Jump to content


Can only connect to server via localhost, IP times out

connection error server timeout timed out

  • Please log in to reply
19 replies to this topic

#1 mrshmid

mrshmid

    Member

  • Members
  • PipPip
  • 10 posts

Posted 05 March 2017 - 11:10 PM

Anytime someone tries to connect to me, they get the following error:
Connect to server failed; check $P4PORT.
TCP connect to mrshmid.ddns.net:1666 failed.
connect: 73.109.12.154:1666: WSAETIMEDOUT
I have the port forwarded, I've set the P4PORT, I've tried reinstalling the server, I've checked the firewall to make sure it's getting through, I made sure I'm using a static IP (if that matters), and restarting the server(multiple times).  Also, as long as I'm connecting to myself using localhost, I'm fine.  Once I try connecting to my own IP, it times out.
This happens when I try connecting from P4V or P4Admin, or doing anything in the command prompt, including p4 info or just p4.


#2 Sambwise

Sambwise

    Advanced Member

  • Members
  • PipPipPip
  • 764 posts

Posted 06 March 2017 - 03:13 PM

What's your server's P4PORT setting?  (If you're on Windows you can see this with "p4 set -S Perforce P4PORT".)

#3 mrshmid

mrshmid

    Member

  • Members
  • PipPip
  • 10 posts

Posted 07 March 2017 - 03:42 AM

mrshmid.ddns.net:1666 (an alias for my ip).

#4 Sambwise

Sambwise

    Advanced Member

  • Members
  • PipPipPip
  • 764 posts

Posted 07 March 2017 - 05:07 AM

If your server's P4PORT is set that way, you should actually not be able to connect to it via localhost.  What platform are you running the server on and how do you start it?  (Is it a Windows service and if so what is it named, is it being invoked from the command line and if so what are its arguments, etc.)

What does "p4 configure show" when run from a working connection show you?

#5 mrshmid

mrshmid

    Member

  • Members
  • PipPip
  • 10 posts

Posted 09 March 2017 - 09:34 PM

if i do it using my ip it gives me the same error.  If I do it from localhost I get:
P4ROOT=F:\Perforce\Server (set -S)
P4PORT=1666 (set -S)
P4JOURNAL=journal (set -S)
P4NAME=Perforce (services registry)
P4LOG=log (set -S)
monitor=2 (configure)
server: 1 (P4DEBUG)


#6 Sambwise

Sambwise

    Advanced Member

  • Members
  • PipPipPip
  • 764 posts

Posted 09 March 2017 - 11:06 PM

Okay, so your server's P4PORT setting is actually just "1666" -- which is good!   Try running ipconfig -- which IP addresses are listed?

#7 mrshmid

mrshmid

    Member

  • Members
  • PipPip
  • 10 posts

Posted 09 March 2017 - 11:59 PM

Wireless LAN adapter Wi-Fi:

   Connection-specific DNS Suffix  . :
   Link-local IPv6 Address . . . . . : fe80::8bc:d4d6:e902:6bee%9
   IPv4 Address. . . . . . . . . . . : 192.168.1.4
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.1.1

Tunnel adapter Local Area Connection* 12:

   Connection-specific DNS Suffix  . :
   IPv6 Address. . . . . . . . . . . : 2001:0:9d38:1f2b:2455:36b5:b692:f365
   Link-local IPv6 Address . . . . . : fe80::2455:36b5:b692:f365%12
   Default Gateway . . . . . . . . . : ::

#8 Sambwise

Sambwise

    Advanced Member

  • Members
  • PipPipPip
  • 764 posts

Posted 11 March 2017 - 12:12 AM

I don't see 73.109.12.154 (which is theoretically your IP) listed there.  :\  What if you do p4 -p 192.168.1.4:1666 info?

#9 mrshmid

mrshmid

    Member

  • Members
  • PipPip
  • 10 posts

Posted 11 March 2017 - 01:01 AM

User name: mrshmid
Client name: Shmidinator3000
Client host: SHMIDINATOR3000
Client root: c:\Users\[username]
Current directory: c:\Users\[username]
Peer address: 192.168.1.4:51417
Client address: 192.168.1.4
Server address: SHMIDINATOR3000:1666
Server root: F:\Perforce\Server
Server date: 2017/03/10 16:59:53 -0800 Pacific Standard Time
Server uptime: 03:39:58
Server version: P4D/NTX64/2016.2/1487173 (2017/02/14)
Server license: none
Case Handling: insensitive

#10 Sambwise

Sambwise

    Advanced Member

  • Members
  • PipPipPip
  • 764 posts

Posted 12 March 2017 - 08:36 PM

Yup, so clearly you can connect to your server on an interface that's not localhost.  I think the issue is that 73.109.12.154 doesn't route to this machine.

#11 mrshmid

mrshmid

    Member

  • Members
  • PipPip
  • 10 posts

Posted 12 March 2017 - 09:08 PM

I don't understand how that works.  I used this same IP before, and I've been running game servers here as well.  I just tested one of my Minecraft servers and it works ok when I try that IP.  It's just perforce that isn't working.

#12 Sambwise

Sambwise

    Advanced Member

  • Members
  • PipPipPip
  • 764 posts

Posted 13 March 2017 - 04:26 AM

Without knowing more about how your Minecraft server and local network are set up, I'd hazard a guess that you've got port forwarding configured on your router to to forward connections from your external IP (73.109.12.154) to your local IP (192.168.1.4) if they match certain ports (i.e. those Minecraft uses), but you don't have that type of forwarding set up for port 1666.

#13 mrshmid

mrshmid

    Member

  • Members
  • PipPip
  • 10 posts

Posted 13 March 2017 - 05:04 AM

I've definitely got 1666 port forwarded.  I used the same process to port forward perforce as I used for everything else.

#14 Sambwise

Sambwise

    Advanced Member

  • Members
  • PipPipPip
  • 764 posts

Posted 13 March 2017 - 02:37 PM

Shot in the dark -- did you restart your router after adding the port forwarding for 1666?  :)

#15 mrshmid

mrshmid

    Member

  • Members
  • PipPip
  • 10 posts

Posted 13 March 2017 - 03:13 PM

Yup.  I've been having internet problems the past few days, have reset it a couple times.  I just tried port forwarding again, it still didn't work.

#16 p4rfong

p4rfong

    Advanced Member

  • Staff Moderators
  • 299 posts

Posted 14 March 2017 - 07:12 PM

I also cannot get to your server:

$ ping 73.109.12.154
PING 73.109.12.154 (73.109.12.154) 56(84) bytes of data.
^C
--- 73.109.12.154 ping statistics ---
7 packets transmitted, 0 received, 100% packet loss, time 6041ms

$ p4 -p 73.109.12.154:1666 info
Perforce client error:
    Connect to server failed; check $P4PORT.
    TCP connect to 73.109.12.154:1666 failed.
    connect: 73.109.12.154:1666: Connection timed out

Check your IP address using http://www.whatismyip.com
as seen in http://answers.perfo...ticles/KB/13219

Also open up ping to at least check that there is connectivity.

#17 mrshmid

mrshmid

    Member

  • Members
  • PipPip
  • 10 posts

Posted 15 March 2017 - 03:43 AM

what is my ip gives my that same ip: 73.109.12.154.  I opened up the ping, but the server still times out

#18 p4rfong

p4rfong

    Advanced Member

  • Staff Moderators
  • 299 posts

Posted 17 March 2017 - 02:08 AM

I still do not see 73.109.12.154 opened up.
$ ping 73.109.12.154
PING 73.109.12.154 (73.109.12.154) 56(84) bytes of data.

Can you ping from a machine that is on another network?

#19 mrshmid

mrshmid

    Member

  • Members
  • PipPip
  • 10 posts

Posted 17 March 2017 - 03:12 AM

My friend tried pinging and also timed out.

#20 p4rfong

p4rfong

    Advanced Member

  • Staff Moderators
  • 299 posts

Posted 05 April 2017 - 07:15 PM

Try turning off the firewall on your Perforce server temporarily and see if you can ping 73.109.12.154.  If so, then try

p4 -p 73.109.12.154:1666 info





Also tagged with one or more of these keywords: connection error, server, timeout, timed out

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users