Marc Lewert
2016-12-29 16:15:51 UTC
The fact that you made changes to your ISP (internet service provider)
connection is important, and is likely the key to the problem.
I note that you are seeing a timeout, and that is an important
indicator. It likely means the connection from your client to the
perforce server is being blocked (swallowing the packets), or running
into bandwidth issues (and again packets are being dropped). Note: The
packets are not being rejected, that would give you a different error.
All of my comments assume a linux client machine.
I would start by trying to make sure the server is up and running. If
the server hardware is down, you need to start by getting it up and
running. Getting the p4d is also desired.
From the client machine, do a host command using the name: host
project2015.ddns.net
Make sure the name maps to the correct IP address.
I would then do a ping to the name (do not use the port number): ping
project2015.ddns.net
That will check the connectivity and basic routing to your perforce
server. If that fails, then your problem is likely routing to the
server machine, however, some companies block the port used for pings.
From there try traceroute to the server machine: traceroute
project2015.ddns.net
That should tell you how far it is making it towards the server
machine. The information will be useful when talking to your ISP (the
same comments made about the blocking of pings also applies here).
From here, you would like to have p4d up and running (even if it was
not earlier).
Next, try a traceroute with the perforce port: traceroute -p 1666
project2015.ddns.net
See how far it makes it toward the server machine. This is a different
test than the previous one, because it tests the routing of the specific
port.
If this traceroute fails, go a normal traceroute and see if there is a
difference. A difference is likely to mean a router (or firewall)
somewhere along the line is blocking port 1666.
Assuming all if the rest of the tests work, then you are making it to
the server.
From here, I normally try a telenet to the server machine on the
appropriate port: telnet project2015.ddns.net 1666
If you get a connection refused, the port is likely not being monitored
by the p4d, or the port is being blocked on the server machine
This is unlikely, since it should work if you made no configurations to
the server machine.
What you hope for is the message: "Connected to project2015.ddns.net
(IP_address)"
The connected message means you are making it all the way through to the
p4d process (or something monitoring that port on the server).
If you get a timeout, you might be making it as far as p4d, but it is
not responding to you.
I am sure I have made some mistakes, and someone else will correct my
approach.
marc
Marc Lewert Going Postal: TiVo Inc.
Senior Software Production Engineer 2160 Gold St.
Email: marc.lewert at tivo.com San Jose, CA 95002
Phone: 408-519-9486 Main Phone: 408-519-9100
________________________________
This email and any attachments may contain confidential and privileged material for the sole use of the intended recipient. Any review, copying, or distribution of this email (or any attachments) by others is prohibited. If you are not the intended recipient, please contact the sender immediately and permanently delete this email and any attachments. No employee or agent of TiVo Inc. is authorized to conclude any binding agreement on behalf of TiVo Inc. by email. Binding agreements with TiVo Inc. may only be made by a signed written agreement.
_______________________________________________
perforce-user mailing list - perforce-***@perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user
connection is important, and is likely the key to the problem.
I note that you are seeing a timeout, and that is an important
indicator. It likely means the connection from your client to the
perforce server is being blocked (swallowing the packets), or running
into bandwidth issues (and again packets are being dropped). Note: The
packets are not being rejected, that would give you a different error.
All of my comments assume a linux client machine.
I would start by trying to make sure the server is up and running. If
the server hardware is down, you need to start by getting it up and
running. Getting the p4d is also desired.
From the client machine, do a host command using the name: host
project2015.ddns.net
Make sure the name maps to the correct IP address.
I would then do a ping to the name (do not use the port number): ping
project2015.ddns.net
That will check the connectivity and basic routing to your perforce
server. If that fails, then your problem is likely routing to the
server machine, however, some companies block the port used for pings.
From there try traceroute to the server machine: traceroute
project2015.ddns.net
That should tell you how far it is making it towards the server
machine. The information will be useful when talking to your ISP (the
same comments made about the blocking of pings also applies here).
From here, you would like to have p4d up and running (even if it was
not earlier).
Next, try a traceroute with the perforce port: traceroute -p 1666
project2015.ddns.net
See how far it makes it toward the server machine. This is a different
test than the previous one, because it tests the routing of the specific
port.
If this traceroute fails, go a normal traceroute and see if there is a
difference. A difference is likely to mean a router (or firewall)
somewhere along the line is blocking port 1666.
Assuming all if the rest of the tests work, then you are making it to
the server.
From here, I normally try a telenet to the server machine on the
appropriate port: telnet project2015.ddns.net 1666
If you get a connection refused, the port is likely not being monitored
by the p4d, or the port is being blocked on the server machine
This is unlikely, since it should work if you made no configurations to
the server machine.
What you hope for is the message: "Connected to project2015.ddns.net
(IP_address)"
The connected message means you are making it all the way through to the
p4d process (or something monitoring that port on the server).
If you get a timeout, you might be making it as far as p4d, but it is
not responding to you.
I am sure I have made some mistakes, and someone else will correct my
approach.
marc
Posted on behalf of forum user 'AllanA'.
Recently I upgraded our internet access (same provider) to gain better
speed. In
doing so a new modem was required. The IP address has not changed and
24 hours
has now passed to ensure DNS propagation. Still, no one, myself or
anyone else
using the web can access P4 any longer.
A whois does resolve to the appropriate IP address. We use DDNS and
for the last
year have never had an issue connecting, the settings on the DDNS
service have
not changed. I can connect to P4 locally using our internal IP scheme.
These are the messages I and others are getting.
Connect to server failed; check $P4PORT.
TCP connect to project2015.ddns.net:1666 failed
connect: 68,231,124,132:1666 WSAETIMEOUT
Spending quite a bit of time talking to the provider and discovering
how little
Tier two support actually knows I'm hoping to get a few ideas here to
help
me resolve this before everyone here gets frustrated.
thanks in advance
--
http://forums.perforce.com/index.php?/topic/5108-assist-unable-to-connect-to-server
_______________________________________________
http://maillist.perforce.com/mailman/listinfo/perforce-user
--Recently I upgraded our internet access (same provider) to gain better
speed. In
doing so a new modem was required. The IP address has not changed and
24 hours
has now passed to ensure DNS propagation. Still, no one, myself or
anyone else
using the web can access P4 any longer.
A whois does resolve to the appropriate IP address. We use DDNS and
for the last
year have never had an issue connecting, the settings on the DDNS
service have
not changed. I can connect to P4 locally using our internal IP scheme.
These are the messages I and others are getting.
Connect to server failed; check $P4PORT.
TCP connect to project2015.ddns.net:1666 failed
connect: 68,231,124,132:1666 WSAETIMEOUT
Spending quite a bit of time talking to the provider and discovering
how little
Tier two support actually knows I'm hoping to get a few ideas here to
help
me resolve this before everyone here gets frustrated.
thanks in advance
--
http://forums.perforce.com/index.php?/topic/5108-assist-unable-to-connect-to-server
_______________________________________________
http://maillist.perforce.com/mailman/listinfo/perforce-user
Marc Lewert Going Postal: TiVo Inc.
Senior Software Production Engineer 2160 Gold St.
Email: marc.lewert at tivo.com San Jose, CA 95002
Phone: 408-519-9486 Main Phone: 408-519-9100
________________________________
This email and any attachments may contain confidential and privileged material for the sole use of the intended recipient. Any review, copying, or distribution of this email (or any attachments) by others is prohibited. If you are not the intended recipient, please contact the sender immediately and permanently delete this email and any attachments. No employee or agent of TiVo Inc. is authorized to conclude any binding agreement on behalf of TiVo Inc. by email. Binding agreements with TiVo Inc. may only be made by a signed written agreement.
_______________________________________________
perforce-user mailing list - perforce-***@perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user