cant connect to win2k over vpn

  • Thread starter Thread starter clive hammond
  • Start date Start date
C

clive hammond

Hi,

i have 1 win2k pro machine that cant connect to win2k server over vpn,
all other pc's with win2k pro and XP pro can.

setup as follows;
win2k pro SP3
vpn client - checkpoint secure client
user connects over internet to company WAN with secure client
hosts file has correct entries to connect to server via name

typical scenario;
user connects to company LAN with secure client - no problem
can ping server by name and ip address - no problem
can telnet to smtp server - no problem
CANT connect to remote server share, have tried map network drive from
explorer and mapping drive by net use.
get various error messages ie network location cannot be reached,
network name cannot be found, the remote computer is not available
error 51 .

the odd thing is its only happening to this pc, i have checked network
settings and they are no different than a pc that can connect (apart
from IP address of course).

Any ideas?

Cheers

Clive
 
Could be your system is trying to use SMB instead of
CIFS. SMB connections need a local LMHOSTS file or access
to a WINS server or lastly, the optional check-off box
selected to use DNS lookup, which also allows Host file
lookup for SMB which you could select under NT (I don't
remember where it's located under W2k.)

Unless this system needs SMB I would disable NetBIOS
services over TCP/IP that way CIFS will be used instead.

If you have a proxy or firewall you may also be blocking
SMB services(NetBIOS over TCP/IP). Which is something I
often see as it is a chatty protocol and tells remote
systems to much about the network Vs CIFS.
 
Back
Top