Forum

Notifications
Clear all

winsock error

0 Posts
2 Users
0 Reactions
164 Views
(@vohra82)
Active Member
Joined: 55 years ago
Posts: 3
Topic starter  

i just downloaded abs telnet..i m trying to connect to my http server running on port 10999 on windows xp..there r no firewalls...when i enter my host ip and port number..it gives error as winsock error:connection refused...my telnet server on the host is follwing NTLM. However when i try to conect frm the remote host to the telnet server on port 23, it can connect....
please help me out wid this....
sameer vohra


   
ReplyQuote
(@bpence)
Member Admin
Joined: 10 months ago
Posts: 1374
 

So, you can telnet to the telnet port, but not to the HTTP port? Why are you using telnet to connect to the HTTP port anyway?

Brian


   
ReplyQuote
(@vohra82)
Active Member
Joined: 55 years ago
Posts: 3
Topic starter  

Hi,
i've got this strange n peculier problem,
i have a java server program running on, say mach1, which is listening on port 10991.
when i try to connect client to that server, it just cannot connect.

furthermore, i can telnet the server from client on port 23, but when i telnet the server on port 10991, it fails.

similarly, if the client and the server are runing on same machine and if i specify the destination addres in client as "localhost", it can connect, but when i specify the destn add as ip, it fails.

i havent seen anything like this before,
any help, any clue please


   
ReplyQuote
(@vohra82)
Active Member
Joined: 55 years ago
Posts: 3
Topic starter  

Hi,
i've got this strange n peculier problem,
i have a java server program running on, say mach1, which is listening on port 10991.
when i try to connect client to that server, it just cannot connect.

furthermore, i can telnet the server from client on port 23, but when i telnet the server on port 10991, it fails.

similarly, if the client and the server are runing on same machine and if i specify the destination addres in client as "localhost", it can connect, but when i specify the destn add as ip, it fails.

i havent seen anything like this before,
any help, any clue please


   
ReplyQuote
(@bpence)
Member Admin
Joined: 10 months ago
Posts: 1374
 

Sameer,

There are NO firewalls involved, or you just don't believe that your firewall should be involved with this connection?

If you're getting different results when you use 'localhost' vs. IP address, then the issue could be that the traffic is diverted outside the box, then back in again, making it subject to the rules of the firewall.

using 'localhost' will use the internal loopback address
using '127.0.0.1' should be the same as localhost
using an internal address such as '192.168.0.1' will confine the traffic to your local net.
using 'mymachine.mydomain.net' may resolve to an external address, which is subject to the firewall.

IF telnet can get through but 10991 cannot, that just seems to indicate further that the firewall is in play and that access has been allowed on some ports and not others.

A more precise description of your network topology would help in this discussion.


   
ReplyQuote
Share: