Jump to content


Unable to connect to P4 server from P4V

client p4v port number

  • Please log in to reply
9 replies to this topic

#1 kristo5747

kristo5747

    Newbie

  • Members
  • Pip
  • 5 posts

Posted 07 October 2014 - 04:48 PM

My apologies if this is not the correct forum. I am your typical newbie. You've been warned. :)

I have inherited the role of Perforce admin for my team. Our server was installed by my predecessor on a RedHat server. I am trying to connect to it using the P4V client from my MS Windows workstation so I can create a depot.

To get the client info, I logged in to my P4 server `blahblah33` and typed `p4 info`.

blahblah33:/home/perforce => p4 info
User name: perforce
Client name: perforce
Client host: blahblah33
Client root: /opt/perforce/WORKSPACE/perforce
Current directory: /home/perforce
Peer address: 147.22.111.80:14419
Client address: 147.22.111.80
Server address: blahblah:16666
Server root: /opt/perforce/P4ROOT
Server date: 2014/10/07 10:31:43 -0600 MDT
Server uptime: 15:46:13
Server version: P4D/LINUX26X86_64/2013.2/740201 (2013/11/11)
Server license: MYEMPLOYER 36 users (support ends 2014/10/16)
Server license-ip: 147.22.111.80:16666
Case Handling: sensitive

When I enter ` blahblah33:16666` for my server in P4 client, it fails with the error message "Connect to server failed. Check $P4Port" (see attached screenshot). I have checked my hosts file and the ip address to `blahblah33` is correctly listed. I tried using the ip addresss instead of the host name, same error.

What I noticed is that the documentation reads that the default port is `1666`, not `16666`. Does it matter?

I am not even sure my Perforce server is running. Is there a P4 command I can run to check?

Thanks in advance for your help.

#2 P4Sam

P4Sam

    Advanced Member

  • Members
  • PipPipPip
  • 484 posts
  • LocationSan Francisco, CA

Posted 07 October 2014 - 08:38 PM

The "p4 info" output shows that the server is running.  Possibly it's not listening on the right network interface?  From your server try doing:

 p4 -p blahblah33:16666 info
 p4 -p localhost:16666 info

If one of those works but not the other (even though they both point to the same machine, right?), you should be able to fix it by restarting the server with a P4PORT of just '16666' (rather than say 'localhost:16666').

#3 kristo5747

kristo5747

    Newbie

  • Members
  • Pip
  • 5 posts

Posted 07 October 2014 - 09:39 PM

That's interesting. Why does it fail?


blahblah33:/home/perforce => p4 -p localhost:16666 info
Perforce client error:
Connect to server failed; check $P4PORT.
TCP connect to localhost:16666 failed.
connect: 127.0.0.1:16666: Connection refused

when this works?

blahblah33:/home/perforce => p4 -p blahblah33:16666 info
User name: perforce
Client name: perforce
Client host: blahblah33
Client root: /opt/perforce/WORKSPACE/perforce
Current directory: /home/perforce
Peer address: 147.22.111.80:50249
Client address: 147.22.111.80
Server address: blahblah33:16666
Server root: /opt/perforce/P4ROOT
Server date: 2014/10/07 15:36:25 -0600 MDT
Server uptime: 20:50:55
Server version: P4D/LINUX26X86_64/2013.2/740201 (2013/11/11)
Server license: MYEMPLOYER 36 users (support ends 2014/10/16)
Server license-ip: 147.22.111.80:16666
Case Handling: sensitive

It's the same machine, right? Is it a different network interface?

#4 P4Sam

P4Sam

    Advanced Member

  • Members
  • PipPipPip
  • 484 posts
  • LocationSan Francisco, CA

Posted 07 October 2014 - 09:54 PM

View Postkristo5747, on 07 October 2014 - 09:39 PM, said:

That's interesting. Why does it fail?


blahblah33:/home/perforce => p4 -p localhost:16666 info
Perforce client error:
Connect to server failed; check $P4PORT.
TCP connect to localhost:16666 failed.
connect: 127.0.0.1:16666: Connection refused

when this works?

blahblah33:/home/perforce => p4 -p blahblah33:16666 info
User name: perforce
Client name: perforce
Client host: blahblah33
Client root: /opt/perforce/WORKSPACE/perforce
Current directory: /home/perforce
Peer address: 147.22.111.80:50249
Client address: 147.22.111.80
Server address: blahblah33:16666
Server root: /opt/perforce/P4ROOT
Server date: 2014/10/07 15:36:25 -0600 MDT
Server uptime: 20:50:55
Server version: P4D/LINUX26X86_64/2013.2/740201 (2013/11/11)
Server license: MYEMPLOYER 36 users (support ends 2014/10/16)
Server license-ip: 147.22.111.80:16666
Case Handling: sensitive

It's the same machine, right? Is it a different network interface?

Yep.  Restart p4d with P4PORT=16666 (I don't know what starts your Perforce server so I can't be more specific than that, but it's probably a script somewhere on your server machine that invokes "p4d -p blahblah33:16666"; remove the "blahblah33:" from that) and that should fix it.

There may be more debugging to do given that "p4 -p blahblah33:16666 info" DOESN'T work on your Windows workstation; that suggests that "blahblah33" doesn't resolve to the same thing from everywhere, which is problematic.  You mentioned that you were specifying the IP manually in the client's hosts file; you might double-check what "blahblah33" resolves to on the server machine and make sure that's the same IP you were using on the client machine.

#5 Thandesha

Thandesha

    Advanced Member

  • Members
  • PipPipPip
  • 164 posts
  • LocationSunnyvale, CA, USA

Posted 28 October 2014 - 07:50 AM

I had similar issue today after upgrading from 12.2 to 14.2

Command used to start:

$p4d  -d  -r  <root> -p server:1666 -L server.log -J server.journal

With above command, I am unable to connect to server from any other machine
than the local host.
$ p4 -p server:1666 info
Perforce client error:
        Connect to server failed; check $P4PORT.
        TCP connect to server:1666 failed.
        connect: server:1666: Connection refused

Immediately tried "telnet server 1666" from the server which gave me the
clue that when hostname is passed to p4d start command, it is converting it
into 127.0.0.1/localhost.

$ netstat -an | grep 1666
tcp        0     127.0.0.1:1666                0.0.0.0:*
LISTEN

So immediately restarted my p4d without hostname entry  and netstat showed
it can accept connections.

$p4d  -d  -r  <root> -p 1666 -L server.log -J server.journal

$ netstat -an | grep 1666
tcp        0      0 0.0.0.0:1666                0.0.0.0:*
LISTEN

So finally restarted p4d with IP:PORT that works best.

$p4d  -d  -r  <root> -p IP:1666 -L server.log -J server.journal

$ netstat -an | grep 1666
tcp        0      0 IP:1666              0.0.0.0:*                   LISTEN


So guessing something changed in recent releases compared to 12.2?

On Wed, Oct 8, 2014 at 3:25 AM, P4Sam <
perforce-user-forum@forums.perforce.com> wrote:

Quote


Posted on behalf of forum user 'P4Sam'.



[http://forums.perfor...=forums&module=
forums&section=findpost&pid=15477]
kristo5747, on 2014/10/07 21:39:25 UTC, said:

Quote

   That's interesting. Why does it fail?
        blahblah33:/home/perforce => p4 -p localhost:16666 info Perforce
client error: Connect to server failed; check $P4PORT. TCP connect to
localhost:16666 failed. connect: 127.0.0.1:16666: Connection refused
when this works?
     blahblah33:/home/perforce => p4 -p blahblah33:16666 info User name:
perforce Client name: perforce Client host: blahblah33 Client root:
/opt/perforce/WORKSPACE/perforce Current directory: /home/perforce Peer
address: 147.22.111.80:50249 Client address: 147.22.111.80 Server
address: blahblah33:16666 Server root: /opt/perforce/P4ROOT Server date:
2014/10/07 15:36:25 -0600 MDT Server uptime: 20:50:55 Server version:
P4D/LINUX26X86_64/2013.2/740201 (2013/11/11) Server license: MYEMPLOYER
36 users (support ends 2014/10/16) Server license-ip: 147.22.111.80:16666
Case Handling: sensitive    It's the same machine, right? Is it a different
network interface?


Yep.  Restart p4d with P4PORT=16666 (I don't know what starts your
Perforce server so I can't be more specific than that, but it's probably
a script somewhere on your server machine that invokes "p4d -p
blahblah33:16666"; remove the "blahblah33:" from that) and that
should fix it.

There may be more debugging to do given that "p4 -p blahblah33:16666
info" DOESN'T work on your Windows workstation; that suggests that
"blahblah33" doesn't resolve to the same thing from everywhere,
which is problematic.  You mentioned that you were specifying the IP
manually in the client's hosts file; you might double-check what
"blahblah33" resolves to on the server machine and make sure
that's the same IP you were using on the client machine.




--
Please click here to see the post in its original format:
http://forums.perfor...ic/3622-unable-
to-connect-to-p4-server-from-p4v

_______________________________________________
perforce-user mailing list  -  perforce-user@perforce.com
http://maillist.perf...o/perforce-user




--
------------------------------------------------------------------------------------
"The only thing worse than losing is quitting"

Your Non-Quitting Friend
Thandesha VK
------------------------------------------------------------------------------------
_______________________________________________
perforce-user mailing list  -  perforce-user@perforce.com
http://maillist.perf...o/perforce-user




#6 Thandesha

Thandesha

    Advanced Member

  • Members
  • PipPipPip
  • 164 posts
  • LocationSunnyvale, CA, USA

Posted 28 October 2014 - 09:25 AM

Interesting. Now since we started p4d with IP:1666, from localhost, it
can't accept connections from localhost without IP:1666 format

$ netstat -an | grep 1666
tcp        0      0 10.0.0.55:1666              0.0.0.0:*
LISTEN

$ p4 -p 1666 info
Perforce client error:
        TCP connect to 1666 failed.
        connect: 127.0.0.1:1666: Connection refused

$ p4 -p server:1666 info
Perforce client error:
        TCP connect to server:1666 failed.
        connect: 127.0.0.1:1666: Connection refused

p4 -p IP:1666 info works though.


On Tue, Oct 28, 2014 at 1:17 PM, Thandesha VK <thanvk@gmail.com> wrote:

Quote

I had similar issue today after upgrading from 12.2 to 14.2

Command used to start:

$p4d  -d  -r  <root> -p server:1666 -L server.log -J server.journal

With above command, I am unable to connect to server from any other
machine than the local host.
$ p4 -p server:1666 info
Perforce client error:
        Connect to server failed; check $P4PORT.
        TCP connect to server:1666 failed.
        connect: server:1666: Connection refused

Immediately tried "telnet server 1666" from the server which gave me the
clue that when hostname is passed to p4d start command, it is converting it
into 127.0.0.1/localhost.

$ netstat -an | grep 1666
tcp        0     127.0.0.1:1666                0.0.0.0:*
  LISTEN

So immediately restarted my p4d without hostname entry  and netstat showed
it can accept connections.

$p4d  -d  -r  <root> -p 1666 -L server.log -J server.journal

$ netstat -an | grep 1666
tcp        0      0 0.0.0.0:1666                0.0.0.0:*
  LISTEN

So finally restarted p4d with IP:PORT that works best.

$p4d  -d  -r  <root> -p IP:1666 -L server.log -J server.journal

$ netstat -an | grep 1666
tcp        0      0 IP:1666              0.0.0.0:*
LISTEN


So guessing something changed in recent releases compared to 12.2?

On Wed, Oct 8, 2014 at 3:25 AM, P4Sam <
perforce-user-forum@forums.perforce.com> wrote:

Quote


Posted on behalf of forum user 'P4Sam'.



[http://forums.perfor...=forums&module=
forums&section=findpost&pid=15477]
kristo5747, on 2014/10/07 21:39:25 UTC, said:

Quote

   That's interesting. Why does it fail?
        blahblah33:/home/perforce => p4 -p localhost:16666 info Perforce
client error: Connect to server failed; check $P4PORT. TCP connect to
localhost:16666 failed. connect: 127.0.0.1:16666: Connection refused
when this works?
     blahblah33:/home/perforce => p4 -p blahblah33:16666 info User name:
perforce Client name: perforce Client host: blahblah33 Client root:
/opt/perforce/WORKSPACE/perforce Current directory: /home/perforce Peer
address: 147.22.111.80:50249 Client address: 147.22.111.80 Server
address: blahblah33:16666 Server root: /opt/perforce/P4ROOT Server date:
2014/10/07 15:36:25 -0600 MDT Server uptime: 20:50:55 Server version:
P4D/LINUX26X86_64/2013.2/740201 (2013/11/11) Server license: MYEMPLOYER
36 users (support ends 2014/10/16) Server license-ip:
147.22.111.80:16666 Case Handling: sensitive    It's the same machine,
right? Is it a different network interface?


Yep.  Restart p4d with P4PORT=16666 (I don't know what starts your
Perforce server so I can't be more specific than that, but it's probably
a script somewhere on your server machine that invokes "p4d -p
blahblah33:16666"; remove the "blahblah33:" from that) and that
should fix it.

There may be more debugging to do given that "p4 -p blahblah33:16666
info" DOESN'T work on your Windows workstation; that suggests that
"blahblah33" doesn't resolve to the same thing from everywhere,
which is problematic.  You mentioned that you were specifying the IP
manually in the client's hosts file; you might double-check what
"blahblah33" resolves to on the server machine and make sure
that's the same IP you were using on the client machine.




--
Please click here to see the post in its original format:
http://forums.perfor...ic/3622-unable-
to-connect-to-p4-server-from-p4v

_______________________________________________
perforce-user mailing list  -  perforce-user@perforce.com
http://maillist.perf...o/perforce-user




--

------------------------------------------------------------------------------------
"The only thing worse than losing is quitting"

Your Non-Quitting Friend
Thandesha VK

------------------------------------------------------------------------------------




--
------------------------------------------------------------------------------------
"The only thing worse than losing is quitting"

Your Non-Quitting Friend
Thandesha VK
------------------------------------------------------------------------------------
_______________________________________________
perforce-user mailing list  -  perforce-user@perforce.com
http://maillist.perf...o/perforce-user





#7 Mailman Sync

Mailman Sync

    Advanced Member

  • Maillist Aggregator
  • 2495 posts

Posted 28 October 2014 - 01:10 PM

Originally posted to the perforce-user mailing list by: Michael Mirman


Hi Thandesha -

I thought the notation "1666" as well as "localhost:1666" were specifically to allow only local connections.
We never used this method, but it was recommended by some (maybe even Perforce?) to use that for maintenance.
That's my vague recollection.

--
Michael Mirman
MathWorks, Inc.
508-647-7555


-----Original Message-----
From: perforce-user-bounces@perforce.com [mailto:perforce-user-bounces@perforce.com] On Behalf Of Thandesha VK
Sent: Tuesday, October 28, 2014 5:21 AM
To: perforce-user@perforce.com
Subject: Re: [p4] Unable to connect to P4 server from P4V

Interesting. Now since we started p4d with IP:1666, from localhost, it
can't accept connections from localhost without IP:1666 format

$ netstat -an | grep 1666
tcp        0      0 10.0.0.55:1666              0.0.0.0:*
LISTEN

$ p4 -p 1666 info
Perforce client error:
        TCP connect to 1666 failed.
        connect: 127.0.0.1:1666: Connection refused

$ p4 -p server:1666 info
Perforce client error:
        TCP connect to server:1666 failed.
        connect: 127.0.0.1:1666: Connection refused

p4 -p IP:1666 info works though.


On Tue, Oct 28, 2014 at 1:17 PM, Thandesha VK <thanvk@gmail.com> wrote:

Quote

I had similar issue today after upgrading from 12.2 to 14.2

Command used to start:

$p4d  -d  -r  <root> -p server:1666 -L server.log -J server.journal

With above command, I am unable to connect to server from any other
machine than the local host.
$ p4 -p server:1666 info
Perforce client error:
        Connect to server failed; check $P4PORT.
        TCP connect to server:1666 failed.
        connect: server:1666: Connection refused

Immediately tried "telnet server 1666" from the server which gave me the
clue that when hostname is passed to p4d start command, it is converting it
into 127.0.0.1/localhost.

$ netstat -an | grep 1666
tcp        0     127.0.0.1:1666                0.0.0.0:*
  LISTEN

So immediately restarted my p4d without hostname entry  and netstat showed
it can accept connections.

$p4d  -d  -r  <root> -p 1666 -L server.log -J server.journal

$ netstat -an | grep 1666
tcp        0      0 0.0.0.0:1666                0.0.0.0:*
  LISTEN

So finally restarted p4d with IP:PORT that works best.

$p4d  -d  -r  <root> -p IP:1666 -L server.log -J server.journal

$ netstat -an | grep 1666
tcp        0      0 IP:1666              0.0.0.0:*
LISTEN


So guessing something changed in recent releases compared to 12.2?

On Wed, Oct 8, 2014 at 3:25 AM, P4Sam <
perforce-user-forum@forums.perforce.com> wrote:

Quote


Posted on behalf of forum user 'P4Sam'.



[http://forums.perfor...=forums&module=
forums&section=findpost&pid=15477]
kristo5747, on 2014/10/07 21:39:25 UTC, said:

Quote

   That's interesting. Why does it fail?
        blahblah33:/home/perforce => p4 -p localhost:16666 info Perforce
client error: Connect to server failed; check $P4PORT. TCP connect to
localhost:16666 failed. connect: 127.0.0.1:16666: Connection refused
when this works?
     blahblah33:/home/perforce => p4 -p blahblah33:16666 info User name:
perforce Client name: perforce Client host: blahblah33 Client root:
/opt/perforce/WORKSPACE/perforce Current directory: /home/perforce Peer
address: 147.22.111.80:50249 Client address: 147.22.111.80 Server
address: blahblah33:16666 Server root: /opt/perforce/P4ROOT Server date:
2014/10/07 15:36:25 -0600 MDT Server uptime: 20:50:55 Server version:
P4D/LINUX26X86_64/2013.2/740201 (2013/11/11) Server license: MYEMPLOYER
36 users (support ends 2014/10/16) Server license-ip:
147.22.111.80:16666 Case Handling: sensitive    It's the same machine,
right? Is it a different network interface?


Yep.  Restart p4d with P4PORT=16666 (I don't know what starts your
Perforce server so I can't be more specific than that, but it's probably
a script somewhere on your server machine that invokes "p4d -p
blahblah33:16666"; remove the "blahblah33:" from that) and that
should fix it.

There may be more debugging to do given that "p4 -p blahblah33:16666
info" DOESN'T work on your Windows workstation; that suggests that
"blahblah33" doesn't resolve to the same thing from everywhere,
which is problematic.  You mentioned that you were specifying the IP
manually in the client's hosts file; you might double-check what
"blahblah33" resolves to on the server machine and make sure
that's the same IP you were using on the client machine.




--
Please click here to see the post in its original format:
http://forums.perfor...ic/3622-unable-
to-connect-to-p4-server-from-p4v

_______________________________________________
perforce-user mailing list  -  perforce-user@perforce.com
http://maillist.perf...o/perforce-user




--

------------------------------------------------------------------------------------
"The only thing worse than losing is quitting"

Your Non-Quitting Friend
Thandesha VK

------------------------------------------------------------------------------------




--
------------------------------------------------------------------------------------
"The only thing worse than losing is quitting"

Your Non-Quitting Friend
Thandesha VK
------------------------------------------------------------------------------------
_______________________________________________
perforce-user mailing list  -  perforce-user@perforce.com
http://maillist.perf...o/perforce-user
_______________________________________________
perforce-user mailing list  -  perforce-user@perforce.com
http://maillist.perf...o/perforce-user





#8 Thandesha

Thandesha

    Advanced Member

  • Members
  • PipPipPip
  • 164 posts
  • LocationSunnyvale, CA, USA

Posted 29 October 2014 - 05:20 AM

Hello Michael,

Behavior is not the same in older version (12.2)

Regards,
Thandesha

On Tue, Oct 28, 2014 at 6:37 PM, Michael Mirman <
Michael.Mirman@mathworks.com> wrote:

Quote

Hi Thandesha -

I thought the notation "1666" as well as "localhost:1666" were
specifically to allow only local connections.
We never used this method, but it was recommended by some (maybe even
Perforce?) to use that for maintenance.
That's my vague recollection.

--
Michael Mirman
MathWorks, Inc.
508-647-7555


-----Original Message-----
From: perforce-user-bounces@perforce.com [mailto:
perforce-user-bounces@perforce.com] On Behalf Of Thandesha VK
Sent: Tuesday, October 28, 2014 5:21 AM
To: perforce-user@perforce.com
Subject: Re: [p4] Unable to connect to P4 server from P4V

Interesting. Now since we started p4d with IP:1666, from localhost, it
can't accept connections from localhost without IP:1666 format

$ netstat -an | grep 1666
tcp        0      0 10.0.0.55:1666              0.0.0.0:*
LISTEN

$ p4 -p 1666 info
Perforce client error:
        TCP connect to 1666 failed.
        connect: 127.0.0.1:1666: Connection refused

$ p4 -p server:1666 info
Perforce client error:
        TCP connect to server:1666 failed.
        connect: 127.0.0.1:1666: Connection refused

p4 -p IP:1666 info works though.


On Tue, Oct 28, 2014 at 1:17 PM, Thandesha VK <thanvk@gmail.com> wrote:

Quote

I had similar issue today after upgrading from 12.2 to 14.2

Command used to start:

$p4d  -d  -r  <root> -p server:1666 -L server.log -J server.journal

With above command, I am unable to connect to server from any other
machine than the local host.
$ p4 -p server:1666 info
Perforce client error:
        Connect to server failed; check $P4PORT.
        TCP connect to server:1666 failed.
        connect: server:1666: Connection refused

Immediately tried "telnet server 1666" from the server which gave me the
clue that when hostname is passed to p4d start command, it is converting
it

Quote

into 127.0.0.1/localhost.

$ netstat -an | grep 1666
tcp        0     127.0.0.1:1666                0.0.0.0:*
  LISTEN

So immediately restarted my p4d without hostname entry  and netstat
showed

Quote

it can accept connections.

$p4d  -d  -r  <root> -p 1666 -L server.log -J server.journal

$ netstat -an | grep 1666
tcp        0      0 0.0.0.0:1666                0.0.0.0:*
  LISTEN

So finally restarted p4d with IP:PORT that works best.

$p4d  -d  -r  <root> -p IP:1666 -L server.log -J server.journal

$ netstat -an | grep 1666
tcp        0      0 IP:1666              0.0.0.0:*
LISTEN


So guessing something changed in recent releases compared to 12.2?

On Wed, Oct 8, 2014 at 3:25 AM, P4Sam <
perforce-user-forum@forums.perforce.com> wrote:

Quote


Posted on behalf of forum user 'P4Sam'.



[http://forums.perfor...=forums&module=
forums&section=findpost&pid=15477]
kristo5747, on 2014/10/07 21:39:25 UTC, said:

Quote

   That's interesting. Why does it fail?
        blahblah33:/home/perforce => p4 -p localhost:16666 info
Perforce

Quote

Quote

Quote

client error: Connect to server failed; check $P4PORT. TCP connect to
localhost:16666 failed. connect: 127.0.0.1:16666: Connection refused
when this works?
     blahblah33:/home/perforce => p4 -p blahblah33:16666 info User
name:

Quote

Quote

Quote

perforce Client name: perforce Client host: blahblah33 Client root:
/opt/perforce/WORKSPACE/perforce Current directory: /home/perforce Peer
address: 147.22.111.80:50249 Client address: 147.22.111.80 Server
address: blahblah33:16666 Server root: /opt/perforce/P4ROOT Server
date:

Quote

Quote

Quote

2014/10/07 15:36:25 -0600 MDT Server uptime: 20:50:55 Server version:
P4D/LINUX26X86_64/2013.2/740201 (2013/11/11) Server license: MYEMPLOYER
36 users (support ends 2014/10/16) Server license-ip:
147.22.111.80:16666 Case Handling: sensitive    It's the same machine,
right? Is it a different network interface?


Yep.  Restart p4d with P4PORT=16666 (I don't know what starts your
Perforce server so I can't be more specific than that, but it's probably
a script somewhere on your server machine that invokes "p4d -p
blahblah33:16666"; remove the "blahblah33:" from that) and that
should fix it.

There may be more debugging to do given that "p4 -p blahblah33:16666
info" DOESN'T work on your Windows workstation; that suggests that
"blahblah33" doesn't resolve to the same thing from everywhere,
which is problematic.  You mentioned that you were specifying the IP
manually in the client's hosts file; you might double-check what
"blahblah33" resolves to on the server machine and make sure
that's the same IP you were using on the client machine.




--
Please click here to see the post in its original format:
http://forums.perfor...ic/3622-unable-
to-connect-to-p4-server-from-p4v

_______________________________________________
perforce-user mailing list  -  perforce-user@perforce.com
http://maillist.perf...o/perforce-user




--


------------------------------------------------------------------------------------

Quote

"The only thing worse than losing is quitting"

Your Non-Quitting Friend
Thandesha VK


------------------------------------------------------------------------------------

Quote





--

------------------------------------------------------------------------------------
"The only thing worse than losing is quitting"

Your Non-Quitting Friend
Thandesha VK

------------------------------------------------------------------------------------
_______________________________________________
perforce-user mailing list  -  perforce-user@perforce.com
http://maillist.perf...o/perforce-user




--
------------------------------------------------------------------------------------
"The only thing worse than losing is quitting"

Your Non-Quitting Friend
Thandesha VK
------------------------------------------------------------------------------------
_______________________________________________
perforce-user mailing list  -  perforce-user@perforce.com
http://maillist.perf...o/perforce-user






#9 austin_wardy

austin_wardy

    Newbie

  • Members
  • Pip
  • 3 posts

Posted 01 July 2018 - 12:52 PM

i work in online store and have same problem with p4 and ıt made me sick....first i use this command:I originally tried my public IP which is forwarded to my server, but when that didn't work I tried targetting my server locally as Server: "192.168.1.105:1666" In either case I get a similar error of:Connect to server failed; check $P4PORT.TCP connect to 192.168.1.105:1666 failed.connect: 192.168.1.105:1666: WSAETIMEDOUTOn my server "p4 set" shows:C:\Users\Hephaestus>p4 setP4EDITOR=C:\Windows\SysWOW64\notepad.exe (set)P4PASSWD=13C72FC3B6AE5DF224D835D7A26332A0 (set)P4PORT=1666P4ROOT=D:\p4P4USER=Hephaestus (set)P4_1666_CHARSET=none (set)On my desktop "p4 set" shows:P4EDITOR=C:\Windows\SysWOW64\notepad.exe (set)P4PORT=50.137.244.199:1666 (set)P4USER=jelamb (set)but it didn't work

#10 p4rfong

p4rfong

    Advanced Member

  • Staff Moderators
  • 299 posts

Posted 06 July 2018 - 05:35 PM

The WSAETIMEDOUT is usually a firewall issue.  To check this, log on directly to the server and see if Perforce is running (Control Panel, Adminstrative Tools, Services) and if it is running, you need to check the environmental variables that apply to the service.  From a "Run as Administrator" command prompt, run

p4 set -S Perforce

and check that P4PORT=1666

If Perforce is not running, check the file named "log" in the P4ROOT directory.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users