Socket Won't Connect

[Chase Preuninger]

Does anyone have any idea why when I create socket connections like
shown they only really work when I test them on my local machine or
when I test them on 2 computers on my wireless network. Other than
that I can't get a peer to peer connection to work.

Socket s = new Socket(Some InetAddress Object, Some Port);

 

[Knute Johnson]

Does anyone have any idea why when I create socket connections like
shown they only really work when I test them on my local machine or
when I test them on 2 computers on my wireless network. Other than
that I can't get a peer to peer connection to work.

Socket s = new Socket(Some InetAddress Object, Some Port);

Do you have a firewall in the way?

 

[Nigel Wade]

Does anyone have any idea why when I create socket connections like
shown they only really work when I test them on my local machine or
when I test them on 2 computers on my wireless network. Other than
that I can't get a peer to peer connection to work.

Socket s = new Socket(Some InetAddress Object, Some Port);

Given that you haven't told us either the IP address or the port in question,
then no, I don't know. All I can do is guess.

There are 3 things I can think of which might be getting in the way. There is no
route between the two IP addresses. The user running the code doesn't have
sufficient privilege to open the port requested. There is a firewall blocking
the connection.

 

[Mark Space]

Does anyone have any idea why when I create socket connections like
shown they only really work when I test them on my local machine or
when I test them on 2 computers on my wireless network. Other than
that I can't get a peer to peer connection to work.

Socket s = new Socket(Some InetAddress Object, Some Port);

Not enough info. Show us how you are actually calling this when if
fails. SSCCE please.

 

[Chase Preuninger]

If there was a firewall in the way wouldn't there be a messages that
pops up when I try to connect. Also what is a proxy?

 

[RedGrittyBrick]

If there was a firewall in the way wouldn't there be a messages that
pops up when I try to connect.

Not necessarily. Most boundary firewalls don't send messages back to
clients. Your client program could pop-up a message if the connection fails.

Also what is a proxy?

http://en.wikipedia.org/wiki/Proxy_server

 

[Mark Space]

If there was a firewall in the way wouldn't there be a messages that
pops up when I try to connect. Also what is a proxy?

<http://en.wikipedia.org/wiki/Ping>

 

[EJP]

Does anyone have any idea why when I create socket connections like
shown they only really work when I test them on my local machine or
when I test them on 2 computers on my wireless network. Other than
that I can't get a peer to peer connection to work.

As you haven't provided the exception message or the stack trace, no, I
have no idea.

The exception tells you *exactly* why:

ConnectException 'connection refused': somebody issued an RST, either
the target host, in which case nothing is listening at the port, or an
intermediate firewall, in which case you violated the firewall rules.

ConnectException 'connection timeout': most probably an intermediate
firewall is dropping you on the floor.

NoRouteToHostException: self-explanatory.