CODEWITHSUNDEEP
windowswindows-7perforce
Blankdud
Blankdud

Reputation: 698

Perforce client connecting to server WSAETIMEDOUT

I've been ripping my hair out for a few days over this and need help. I have a perforce server and an external client. Steps I've taken:

1. Opened port 1666 on my router (TCP and UDP) for my servers IP.
2. Allowed port 1666 through windows firewall.
3. I can connect to the perforce server from any system on the LAN by hostname or IP.
4. NETSTAT -a shows port 1666 is LISTENING.
5. External client can ping the server by external IP.
6. Internal client can telnet to the internal IP and port, external cannot.

I can not for the life of me figure out why the hell my external client cannot connect to the server. I am getting my external IP from "WhatsMyIP.org" and it matches my routers WAN address.

I have full on tried to disable windows firewall and still the same issue.

Please god someone help before I lose the rest of my hair.

EDIT1: I forgot to mention the error I am receiving from the external client:

Connect to server failed; check $P4PORT.
TCP connect to 99.252.60.60:1666 failed.
connect: 99.252.60.60:1666: WSAETIMEDOUT

Upvotes: 0

Views: 19414

Answers (2)

Blankdud
Blankdud

Reputation: 698

After working at this for three days, I found the issue with help from this forum post:

http://208.74.204.155/t5/forums/forumtopicpage/board-id/Getting_connected/thread-id/8923/page/1

My router model (Hitron Technologies CGN2-ROG) that I received from my ISP (Rogers up here in Canada) apparently doesn't play nice when it comes to port forwarding. With all of the EXACT same settings, I bridged that router to another spare I had laying around and it worked perfectly.

I literally just plugged in the new router and it worked without making any other changes at all.

Upvotes: 1

P4Jen
P4Jen

Reputation: 1023

You may want to take a look at your router's firewall rules in more detail.

I had a similar problem with my home setup that resulted in me having to modify some firewall settings on the router.

This KB also gives some information about the error:

http://answers.perforce.com/articles/KB/2960/

Upvotes: 1

Related Questions