Support Forums

Gents,

I have installed a ProDiscover 4.9 trial on a Win2K3 virtual machine and have a Win2K and WinXP VM on the same network.  I am able to ping and deploy a Remote Agent to any host I want, but every attempt to connect to those agents results in a timeout.  I increased the timeout to 20 seconds (from the default 10) with no more success.

If Windows Firewalls are being used, then have the appropriate tcp/6518 and udp/6518 allowed.  The network authentication works for deployment, so that's not the cause of the trouble I'm experiencing.

Please let me know if you have any insight that may help me get through this rough spot.

EXAMPLE:
ProDiscover (2k3) - 192.168.182.136
XP - 192.168.182.132
2K - 192.168.182.134

Connecting to XP

1. Deploy Remote Agent to 192.168.182.132
2. Authenticate to 192.168.182.132 ... Remote Agent successfully deployed
3. Connect to 192.168.182.132 ...
4. "response timedout" -> Retry or Cancel?

-Jed-

JTM, Thanks for taking the time to post. The connection issue is a result of packet filtering/firewalling 99.9% of the time. You may want to try stopping the windows firewall service completely and check anti-virus software. Also, have you confirmed that the remote agent service is started? If it is installed as a service you can verify the service state in Admin Tools, Services.

Again, thanks for using the forums and I look forward to a response.

Thanks,

Alex

Alex, thanks for the response.  I read the Remote Agent Use And Troubleshooting.pdf guide before posting, so I disabled my firewall and AV software before testing.  There is also no indication of a block in the FW logs.  I am including some screenshots to help with troubleshooting. 

The ProDiscover machine is Win2K3. The IP is shown here as 192.168.182.136.


PDServer installation dialog


The PDServer installation reports success.


The target machine is Win2K. The IP is shown here as 192.168.182.134. The PDServer process is shown to be running in Taskmanager and the netstat output shows 6518 is LISTENING


ProDiscover attempts to connect to the target and fails


Pings are successful from ProDiscover machine to target.


Pings are successful from target to ProDiscover machine.


Thanks for any insight,

-Jed-

JTM,

Thanks for the screen shots. They were helpful. Have verified that port 6518 is open on the ProDiscover box? IP 192.168.182.134 ? The connection between ProDiscover and PDServer requires the port to be open both inbound and outbound. So the .134 box needs to have it open as well.

Thanks,

Alex

Alex,

Correct, 6518 is open on the ProDiscover box.  The FW exception and netstat output are shown below:




-Jed-

JTM,

Let's try un-installing the remote agent and then running it in GUI mode. You can burn the remote agent and files to a CD using the ISO found at:

C:\Program Files\Technology Pathways\ProDiscover\Remote Agent\Windows\PDServerWindows.ISO

Put the CD into the target system's drive and it should auto play. If not, you will need to double-click the .exe after browsing to the CD. Once PDServer is running in GUI mode...try connecting.

If you can connect then there's an issue with the service install. If not, then something is stopping the connection.

Alex, 

I should have delivered this with my first post, but I didn't think to install Wireshark on the VMs that early in the process.  Here is a traffic dump giving evidence of successful communication between the RemoteAgent and ProDiscover.  This was grabbed while using the GUI (per your last post) but the result of 'timedout response' still remains.

  4 7.951087    192.168.182.134       192.168.182.136       TCP      1316 > 6518 [SYN] Seq=0 Len=0 MSS=1460 WS=2
  5 7.951197    192.168.182.136       192.168.182.134       TCP      6518 > 1316 [SYN, ACK] Seq=0 Ack=1 Win=64240 Len=0 MSS=1460 WS=0
  6 7.957284    192.168.182.134       192.168.182.136       TCP      1316 > 6518 [ACK] Seq=1 Ack=1 Win=256960 Len=0
  7 7.957364    192.168.182.134       192.168.182.136       TCP      1316 > 6518 [FIN, ACK] Seq=1 Ack=1 Win=256960 Len=0
  8 7.957400    192.168.182.134       192.168.182.136       TCP      1317 > 6518 [SYN] Seq=0 Len=0 MSS=1460 WS=2
  9 7.957435    192.168.182.136       192.168.182.134       TCP      6518 > 1317 [SYN, ACK] Seq=0 Ack=1 Win=64240 Len=0 MSS=1460 WS=0
 10 7.957464    192.168.182.136       192.168.182.134       TCP      6518 > 1316 [ACK] Seq=1 Ack=2 Win=64240 Len=0
 11 7.960669    192.168.182.134       192.168.182.136       TCP      1317 > 6518 [ACK] Seq=1 Ack=1 Win=256960 Len=0
 12 7.963496    192.168.182.134       192.168.182.136       TCP      1317 > 6518 [ACK] Seq=1 Ack=1 Win=256960 Len=1460
 13 7.964501    192.168.182.134       192.168.182.136       TCP      1317 > 6518 [PSH, ACK] Seq=1461 Ack=1 Win=256960 Len=573
 14 7.964531    192.168.182.136       192.168.182.134       TCP      6518 > 1317 [ACK] Seq=1 Ack=2034 Win=64240 Len=0
 15 7.964669    192.168.182.136       192.168.182.134       TCP      6518 > 1317 [FIN, ACK] Seq=1 Ack=2034 Win=64240 Len=0
 16 7.966583    192.168.182.136       192.168.182.134       TCP      1052 > 6518 [SYN] Seq=0 Len=0 MSS=1460
 17 7.967269    192.168.182.134       192.168.182.136       TCP      1317 > 6518 [ACK] Seq=2034 Ack=2 Win=256960 Len=0
 18 7.967462    192.168.182.134       192.168.182.136       TCP      6518 > 1052 [SYN, ACK] Seq=0 Ack=1 Win=65535 Len=0 MSS=1460
 19 7.967477    192.168.182.136       192.168.182.134       TCP      1052 > 6518 [ACK] Seq=1 Ack=1 Win=64240 Len=0
 20 7.967672    192.168.182.136       192.168.182.134       TCP      1052 > 6518 [ACK] Seq=1 Ack=1 Win=64240 Len=1460
 21 7.967782    192.168.182.136       192.168.182.134       TCP      1052 > 6518 [PSH, ACK] Seq=1461 Ack=1 Win=64240 Len=568
 22 7.967886    192.168.182.136       192.168.182.134       TCP      1052 > 6518 [FIN, ACK] Seq=2029 Ack=1 Win=64240 Len=0
 23 7.969402    192.168.182.134       192.168.182.136       TCP      6518 > 1052 [ACK] Seq=1 Ack=2030 Win=64240 Len=0
 24 7.969734    192.168.182.134       192.168.182.136       TCP      1317 > 6518 [FIN, ACK] Seq=2034 Ack=2 Win=256960 Len=0
 25 7.969753    192.168.182.136       192.168.182.134       TCP      6518 > 1317 [ACK] Seq=2 Ack=2035 Win=64240 Len=0
 26 7.973356    192.168.182.134       192.168.182.136       TCP      6518 > 1052 [FIN, ACK] Seq=1 Ack=2030 Win=64240 Len=0
 27 7.973384    192.168.182.136       192.168.182.134       TCP      1052 > 6518 [ACK] Seq=2030 Ack=2 Win=64240 Len=0

JTM,

I should have reviewed your screen shots more closely. You have the remote agent and ProDiscover running on the same box and only one app can bind to a port at a time. If you look at the last screen shot you will see both ProDiscover.exe and PDService.exe running. Windows doesn't always inform the user that multiple apps are trying to bind to the port.

The same scenario would be present if two instances of ProDiscover were running.

Thanks for taking the time gather all of this data. It was obviously needed. :)

Alex,

SUCCESS!  I killed the PDServer.exe process on the ProDiscover machine (probably an artifact from attempting to connect to my localhost as a remote host).  Thank you for working through that with me.  I'm glad to have gone through the screenshots etc. since they provide more information (obviously) than mere words.  I now attempt my ProScripts. :-)

-Jed-