Advertisement

Problem with winsock: connect()

Started by January 06, 2003 05:31 PM
9 comments, last by Evil Bill 22 years, 1 month ago
Anyone know how to fix this: I'm writing a MUD, and it works perfectly within my own network (i have 3 computers networked), but whenever someone tries to connect to me who isn't on my network (across the internet), winsock replies to connect() with WSAETIMEDOUT. I'm using a cable modem, with windows internet connection sharing and MFC's CSocket class if that matters. You can get the client program Here Although thats running off my own pooter, so the link may not always be valid. Cheers for any help [edited by - Evil Bill on January 6, 2003 6:32:08 PM]
Member of the Unban Mindwipe Society (UMWS)
Are you behind a firewall? If so, did you open up a known port for the outside world to connect to? I''m thinking you''ll probably have to do this in order for them to connect to you.

-John
- John
Advertisement
Thanks for the quick reply!

Nope, no firewall.

Member of the Unban Mindwipe Society (UMWS)
Is your server running on the computer that''s hosting the Internet connection sharing?
Yep
Member of the Unban Mindwipe Society (UMWS)
Are you running Windows XP?

RapscallionGL - arriving soon.
________________________________________________"Optimal decisions, once made, do not need to be changed." - Robert Sedgewick, Algorithms in C
Advertisement
Nope, Windows 98SE - Sorry, i should have specified.

I appreciate the replies.

Member of the Unban Mindwipe Society (UMWS)
Is it possible that your ISP might be blocking the port on which you''re trying to host? I''ve heard some of them block certain ports to keep people from running file servers.
I don''t think so. I''ll try port 80 and post agaian...

Member of the Unban Mindwipe Society (UMWS)
Uhhh! It works on port 80! Now to see what other ports work...

Cheers!

Member of the Unban Mindwipe Society (UMWS)

This topic is closed to new replies.

Advertisement