Hi Folks, A Windows XP machine d

[Virusbaba]

Hi Folks,

A Windows XP machine dials in and connects to a Win 2000 VPN Server using the Microsoft VPN client and gets a virtual IP assigned by the VPN Server. Specified Discovery to this virtual IP does not work.

"netstat -an" results do not indicate that the virtual IP address is listening on port 42508 udp.

Etrust InoculateIT build 96 will not listen on a virtual IP. How do we accomplish the same?

Any help is highly appreciated.

Cheers!
Virus Baba

Baba counting starts now..........

 

[bkonline]

virusbaba
1) My assumption is that your VPN client dials-in and mostly likely not stay on long enough to be picked up by the Inoculate periodic discoveries.
2) port 42508-upd is the default port used by the server for listening and discovery, and the clients MUST be set to use the same.
3) Ensure that the client is on the same subnet as the server. In other words, discoveries works on subnet bases. So if the vPN client happens to have an IP that is outside the server's subnet, then you might need to setup a special discovery of that particular subnet using specific election option. (i.e. assuming there is no Firewall between the subnets). But if there is FW, then a rule modification may be necessary to allow that port, as in my own case. ^^^^^^^^^^^^^^^^
None is Better!
^^^^^^^^^^^^^^^^
bkonline@comcast.net

 

[iowtech]

If the client is not listening on 42508 then chck this out (enterprise version only):

http://support.ca.com/Download/patches/ilitnt/QO28716.html