Support Forums

I recently purchased ProDiscover IR and I appear to have an issue similar to the one described in the post made by JTM on Sept 20 '07.

I have installed ProDiscover IR on a virtual machine.

The virtual machine is using a NAT'ted connection to the network using the host machine's IP address of X.X.X.201.

Neither the virtual machine nor the host have the XP firewall enabled (nor any other firewall).

ProDiscover successfully connects to the target on IP address X.X.X.168 and installs the PDServer.

There are no firewalls between the ProDiscover machine and the target.

The ProDiscover machine and the target are part of the same domain (probably irrelevant at this point).

The target does not have the XP firewall enabled.

On the target, CurrPorts identifies the PDServer service as running with port 6518 in a Listening state.

Each time the ProDiscover machine attempts to connect to the target, CurrPorts reports that a new connection exists between the two devices in a CloseWait state.  The more connection attempts, the more embryonic connection threads.  The thread which is in a Listening state is also always there.

The ProDiscover machine reports that the "Request Timedout". 

There are no ProDiscover (including PDServer) processes running on either the ProDiscover host or virtual machine (except for a single ProDiscoverIR.exe running on the virtual machine).

I can successfully uninstall the agent from the target, which stops the PDServer.exe process on the target and deletes all the connections logged by CurrPorts.

I would appreciate any advice...

Thanks,

Seth

Seth,

Thanks for the post. 6518 needs to be open both inbound and outbound on both systems. Meaning the initial connection is made on TCP port 6518....but repsponse from PDServer will be made on many ports back to ProDiscover to port 6518.

Regards,

Alex

SUCCESS!

I switched to a bridged connection and it works!  I don't think there's a way to open up the host to forward port 6518 connection attempts to the virtual machine so I don't think there's a way to make the NAT'd environment work...but at least at this point I can work backwords and see how much I can tighten things back up...

So now I get to play around with PDIR for the first time...thanks for your help!

Seth

Seth,

Good news! So the NAT connection in VMWare server would not allow/direct the inbound packets to ProDiscover. I hope the bridge connection is sufficent for your needs.

Again, thanks for using the forums.