Jump to content


partner is not a perforce client/server

Error

  • Please log in to reply
12 replies to this topic

#1 Metalphantom

Metalphantom

    Newbie

  • Members
  • Pip
  • 9 posts

Posted 01 March 2018 - 12:42 AM

I am a new perforce user and set up a server on my computer for me and my friend to work on our senior project for school. When i first set it up, my friend was able to connect to it and the version control worked great. We took a break from using it for about 3 weeks or so because of other obligations but when we picked the project back up my friend only got this error message shown whenever he tried to connect to my server through the p4v visual client : "RpcTransport: partner is not a Perforce client/server" We tried updating to the latest versions of the server and the visual client, same error. We tried getting an older version of the client and server, same problem. I was wondering if anyone came into this error message before as when i tried to find answers, there were no other topics about this error. I have used port forwarding on my router, I made an exception on the firewall. When i check on port checking websites to see if my port is open, they always come back with a green saying its open, even when i turn the server off, maybe that is a problem? If anyone has any suggestions or needs more information I would be glad to accommodate.

#2 Sambwise

Sambwise

    Advanced Member

  • Members
  • PipPipPip
  • 1155 posts

Posted 01 March 2018 - 02:12 AM

What the error means is that the server the client is talking to isn't a Perforce server -- you'll get this error if, for example, you try to use P4V to connect to a web server.  Last time I tried, the server will also log this error if you try to point a web browser at it.  :)

So this comes down to checking the usual suspects:
1) Are you sure the server is running?
2) Are you sure it's running on the port you think it's running on?
3) Are you sure your friend is connecting to that port?
4) Are you sure the port forwarding is set up correctly?
5) Have you recently angered Nyarlathotep?

#3 Metalphantom

Metalphantom

    Newbie

  • Members
  • Pip
  • 9 posts

Posted 01 March 2018 - 03:16 AM

1) yes, I checked the services running on my machine and found it running

2) yes, the file attached p4server.PNG proves I'm using port 1666 which is the default

3) yes, I've done a skype chat with him where he shared his screen and I watched him put in the correct information

4) as far as I understand I am as the port forwarding is set up the same way when it originally worked. I have xfinity and set up the port forwarding through their website which was relatively easy

5) I hope not :(

I recently got on my laptop to check to see if I could connect to my server on the same network, and I was able to connect to my server on my laptop using the local IP address rather than my global IP.
If you need information on my friends end I should be able to get it from him.

Thank you for responding :)

#4 Sambwise

Sambwise

    Advanced Member

  • Members
  • PipPipPip
  • 1155 posts

Posted 01 March 2018 - 03:23 PM

My guess is that it's the xfinity port forwarding that's somehow busted.  What if you try to connect to your server via the global IP, do you get the same results?  Can you do a packet dump of what the server sends back, or maybe try the "-vnet=5" debugging flag to see more about why the Perforce networking layer thinks what it's talking to isn't a Perforce server?

#5 Metalphantom

Metalphantom

    Newbie

  • Members
  • Pip
  • 9 posts

Posted 01 March 2018 - 08:02 PM

I wanted to test that if I could connect to the server using the global IP even if my friend could not, I should have the results from that as soon as I get out of work. Could you explain how I would get the packets from what the server sends back? what commands would I use? and how would I use the -vnet=5 ? My apologies for my lack of understanding on this topic.

#6 Sambwise

Sambwise

    Advanced Member

  • Members
  • PipPipPip
  • 1155 posts

Posted 01 March 2018 - 09:15 PM

If you run a command like p4 -vnet=5 -p my_global_ip:1666 info you'll get some debugging output from the client that might provide a clue as to what's going wrong.  Another option would be using a tool like Wireshark to inspect the packets directly -- you might find out that you're getting an HTTP error from Xfinity rather than the Perforce server response that the client is expecting.

#7 Metalphantom

Metalphantom

    Newbie

  • Members
  • Pip
  • 9 posts

Posted 02 March 2018 - 04:14 AM

Thank you, I'll try that tomorrow and let you know the results.

#8 Metalphantom

Metalphantom

    Newbie

  • Members
  • Pip
  • 9 posts

Posted 02 March 2018 - 10:07 PM

So I used my laptop on a different network to try and connect to my server at my house. I got a different error message than my friend got: "Perforce Client error: Connect to server failed; check $P4PORT. TCP connect to seniorproject.ddns.net:1666 failed. connect: (global IP):1666: WSAETIMEDOUT." Since there are two different error messages, does that mean there are two issues or is there one that is causes both errors to be thrown?

#9 Metalphantom

Metalphantom

    Newbie

  • Members
  • Pip
  • 9 posts

Posted 03 March 2018 - 05:30 PM

I Used wire shark to check where the package is being sent and the destination of my friends packet is to my local IP address and not my global IP address, is that right? also the port number it is being sent to is not 1666 but a larger port number even though he it trying to connect to: (my global IP):1666.  I'm not sure which information from the wireshark packets are needed so if there's something specific I need to look at or something specific you would like to look at let me know. I also ran the flag command on my machine with the global IP address and got this:

P.S.  seniorproject.ddns.net is the free dynamic dns from noip.com

"C:\Users\mchar>p4 -vnet=5 -p seniorproject.ddns.net:1666 info
NetTcpEndPoint::GetAddrInfo(port=[seniorproject.ddns.net]:1666, family=2, flags=0x500)
<-  NetTcpEndPoint try socket(2, 1, 0, (MY GLOBAL IP):1666)
Perforce client error:
Connect to server failed; check $P4PORT.
TCP connect to seniorproject.ddns.net:1666 failed.
connect: (MY GLOBAL IP):1666: WSAETIMEDOUT"

I had my friend run that command and he got this:  vnet=5friendCommand.PNG

I ran the command again but with just port 1666 and got this :

C:\Users\mchar>p4 -vnet=5 -p 1666 info
NetTcpEndPoint::GetAddrInfo(port=[]:1666, family=2, flags=0x500)
<-  NetTcpEndPoint try socket(2, 1, 0, 127.0.0.1:1666)
<-  NetTcpEndpoint connect on 436
<-  NetTcpTransport: enabling TCP keepalives
<-  NetTcpTransport 127.0.0.1:49680 connected to 127.0.0.1:1666
NetBuffer snd 5: <b9><b9><00><00><00>
NetBuffer snd 185: cmpfile<00><00><00><00><00><00>client<00><02><00><00><00>83<00>api<00><05><00><00><00>99999<00>enableStreams<00><00><00><00><00><00>enableGraph<00><00><00><00><00><00>expandAndmaps
<00><00><00><00><00><00>host<00><0b><00><00><00>Constantine<00>port<00><04><00><00><00>1666<00>sndbuf<00><06><00><00><00>524288<00>rcvbuf<00><06><00><00><00>524288<00>func<00><08><00><00><00>protocol<00>

NetBuffer snd 5: <ca><ca><00><00><00>
NetBuffer snd 202: version<00><14><00><00><00>2017.2/NTX64/1611521<00>autoLogin<00><00><00><00><00><00>prog<00><02><00><00><00>p4<00>client<00><0b><00><00><00>Constantine<00>cwd<00><0e><00><00><00>c:\Users\mchar
<00>host<00><0b><00><00><00>Constantine<00>os<00><02><00><00><00>NT<00>user<00><05><00><00><00>mchar<00>charset<00><01><00><00><00>7<00>clientCase<00><01><00><00><00>1<00>func<00><09><00><00><00>user-info<00>

<-  NetTcpTransport send 397 bytes
<-  NetTcpTransport recv 1810 bytes

NetBuffer rcv 5: <9a><9a><00><00><00>
NetBuffer rcv 154: xfiles<00><01><00><00><00>7<00>server<00><01><00><00><00>3<00>server2<00><02><00><00><00>44<00>serverID<00><00><00><00><00><00>revver<00><01><00><00><00>9<00>nocase<00><00><00><00><00><00>tzoffset
<00><06><00><00><00>-18000<00>sndbuf<00><06><00><00><00>524288<00>rcvbuf<00><06><00><00><00>524288<00>func<00><08><00><00><00>protocol<00>

NetBuffer rcv 5: VV<00><00><00>
NetBuffer rcv 86: code0<00><09><00><00><00>285219949<00>fmt0<00><11><00><00><00>User name: %user%<00>user<00><05><00><00><00>mchar<00>func<00><0e><00><00><00>client-Message<00>
User name: mchar
NetBuffer rcv 5: bb<00><00><00>
NetBuffer rcv 98: code0<00><09><00><00><00>285219951<00>fmt0<00><15><00><00><00>Client name: %client%<00>client<00><0b><00><00><00>Constantine<00>func<00><0e><00><00><00>client-Message<00>
Client name: Constantine
NetBuffer rcv 5: ^^<00><00><00>
NetBuffer rcv 94: code0<00><09><00><00><00>285219953<00>fmt0<00><13><00><00><00>Client host: %host%<00>host<00><0b><00><00><00>Constantine<00>func<00><0e><00><00><00>client-Message<00>
Client host: Constantine
NetBuffer rcv 5: aa<00><00><00>
NetBuffer rcv 97: code0<00><09><00><00><00>285219978<00>fmt0<00><13><00><00><00>Client root: %root%<00>root<00><0e><00><00><00>c:\Users\mchar<00>func<00><0e><00><00><00>client-Message<00>
Client root: c:\Users\mchar
NetBuffer rcv 5: mm<00><00><00>
NetBuffer rcv 109: code0<00><09><00><00><00>285219954<00>fmt0<00><1c><00><00><00>Current directory: %dirName%<00>dirName<00><0e><00><00><00>c:\Users\mchar<00>func<00><0e><00><00><00>client-Message<00>
Current directory: c:\Users\mchar
NetBuffer rcv 5: kk<00><00><00>
NetBuffer rcv 107: code0<00><09><00><00><00>285220424<00>fmt0<00><18><00><00><00>Peer address: %peerAddr%<00>peerAddr<00><0f><00><00><00>127.0.0.1:49680<00>func<00><0e><00><00><00>client-Message<00>
Peer address: 127.0.0.1:49680
NetBuffer rcv 5: kk<00><00><00>
NetBuffer rcv 107: code0<00><09><00><00><00>285219955<00>fmt0<00><1c><00><00><00>Client address: %clientAddr%<00>clientAddr<00><09><00><00><00>127.0.0.1<00>func<00><0e><00><00><00>client-Message<00>
Client address: 127.0.0.1
NetBuffer rcv 5: rr<00><00><00>
NetBuffer rcv 114: code0<00><09><00><00><00>285219956<00>fmt0<00><1c><00><00><00>Server address: %serverAddr%<00>serverAddr<00><10><00><00><00>Constantine:1666<00>func<00><0e><00><00><00>client-Message<00>
Server address: Constantine:1666
NetBuffer rcv 5: }}<00><00><00>
NetBuffer rcv 125: code0<00><09><00><00><00>285219957<00>fmt0<00><19><00><00><00>Server root: %serverRoot%<00>serverRoot<00><1e><00><00><00>E:\PerforveVisualClient\Server<00>func<00><0e><00><00><00>client-Message<00>
Server root: E:\PerforveVisualClient\Server
NetBuffer rcv 5: <b2><b2><00><00><00>
NetBuffer rcv 178: code0<00><09><00><00><00>301997174<00>fmt0<00>*<00><00><00>Server date: %serverDate% %serverTimeZone%<00>serverDate<00><13><00><00><00>2018/03/03 12:19:54<00>
serverTimeZone<00><1b><00><00><00>-0500 Eastern Standard Time<00>func<00><0e><00><00><00>client-Message<00>

Server date: 2018/03/03 12:19:54 -0500 Eastern Standard Time
NetBuffer rcv 5: aa<00><00><00>
NetBuffer rcv 97: code0<00><09><00><00><00>285220207<00>fmt0<00><17><00><00><00>Server uptime: %uptime%<00>uptime<00><08><00><00><00>74:29:04<00>func<00><0e><00><00><00>client-Message<00>
Server uptime: 74:29:04
NetBuffer rcv 5: <8b><8b><00><00><00>
NetBuffer rcv 139: code0<00><09><00><00><00>301997175<00>fmt0<00><1f><00><00><00>Server version: %id% (%idDate%)<00>id<00><18><00><00><00>P4D/NTX64/2017.2/1611521<00>idDate<00><0a><00><00><00>2018/01/21<00>
func<00><0e><00><00><00>client-Message<00>

Server version: P4D/NTX64/2017.2/1611521 (2018/01/21)
NetBuffer rcv 5: ``<00><00><00>
NetBuffer rcv 96: code0<00><09><00><00><00>285219960<00>fmt0<00><19><00><00><00>Server license: %license%<00>license<00><04><00><00><00>none<00>func<00><0e><00><00><00>client-Message<00>
Server license: none
NetBuffer rcv 5: pp<00><00><00>
NetBuffer rcv 112: code0<00><09><00><00><00>285220266<00>fmt0<00><1d><00><00><00>Case Handling: %caseHandling%<00>caseHandling<00><0b><00><00><00>insensitive<00>func<00><0e><00><00><00>client-Message<00>
Case Handling: insensitive
NetBuffer rcv 5: <11><11><00><00><00>
NetBuffer rcv 17: func<00><07><00><00><00>release<00>
NetBuffer snd 5: <12><12><00><00><00>
NetBuffer snd 18: func<00><08><00><00><00>release2<00>
NetBuffer flush
<-  NetTcpTransport send 23 bytes
<-  NetTcpTransport 127.0.0.1:49680 closing 127.0.0.1:1666
<-  NetTcpTransport lastRead=0

#10 Metalphantom

Metalphantom

    Newbie

  • Members
  • Pip
  • 9 posts

Posted 03 March 2018 - 07:20 PM

Just check to see if my 1666 port is open for my perforce server using "http://canyouseeme.org/" and it says its open. I then turned my perforce server off and check again and "http://canyouseeme.org/" still says its open

#11 Sambwise

Sambwise

    Advanced Member

  • Members
  • PipPipPip
  • 1155 posts

Posted 03 March 2018 - 09:02 PM

So, about all I can get from that is that whatever is picking up the phone when your friend tries to connect to that port, it's not the Perforce server.  The fault could be with xfinity, or with your Windows firewall, or maybe neither.  And you aren't able to connect via that local IP either.  I'd probably try setting up another way for the machines to connect to each other, like a VPN (one I've used in the past for sharing minecraft servers and stuff is Hamachi; I imagine it'd work fine for Perforce too).

#12 Metalphantom

Metalphantom

    Newbie

  • Members
  • Pip
  • 9 posts

Posted 04 March 2018 - 04:05 PM

OK i'll look into that, thank you.

#13 Metalphantom

Metalphantom

    Newbie

  • Members
  • Pip
  • 9 posts

Posted 04 March 2018 - 08:02 PM

using hamachi seems to be working. Thank you for suggesting it.





Also tagged with one or more of these keywords: Error

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users