NET USE doesn't work under VPN

  • Thread starter Thread starter gorfmeister
  • Start date Start date
G

gorfmeister

I have finally been able to establish a VPN. My ISP is
blocking port 139. When I do a NET USE from the client to
an IP address on the remote connection, I get a "System
error 53 has occurred." message, the same message I get
without a VPN. I thought that the VPN would bypass my ISPs
block, since it communicates on a different port. Is this
true?

I'm not sure that this is related to the problem, but I'm
not sure I understand how the IP address assignments work
with VPN. On the remote computer (WIN 2K Server), I have
the IP addresses set to a static pool of 192.168.16.1 to
192.168.16.255 (private network). The computer has only
one NIC, so during the Routing and Remote Access setup, I
selected "no adapter" (it wouldn't let me choose the
adpater in my machine). I do not have a modem attached, so
I do not dial up capability. I connect via the public IP
address of the system. Also, the NET USE is attempting to
connect to this IP address. On the client, I configured
the VPN connection to access the WINS of the remote
computer. Did I do everything right?
 
The client should be able to see the server using its private LAN IP.

If you are running DNS and/or WINS on the LAN, the client should receive
the DNS and WINS addresses at connection time, and you should be able to see
the server by name in net view \\servername . If you are not running WINS or
DNS, you will need a HOSTS or LMHOSTS file on the client to resolve its name
to an IP address.
 
The problem is not DNS related.

After sending my original question, I noticed that I
cannot even PING from the server to the client using the
private IP assigned to the client. Also, I cannot PING the
server from the client using a private multi-homed IP
address assigned to the server (e.g. 192.168.xx.xx).
Furthermore NET USE x: \\xxx.xxx.xxx.xxx\c$ also has a
problem (no name, just IP address).
 
I'm assuming the connection is going through fine. Doing a tracert to the
client ip address will tell you if the packets are reaching the client at
all through the tunnel.

It could also be some filters configured at the server configured in the
Remote Access Policy. Note that trying to use the public address will go
through the ISP rather than the tunnel.
 
Back
Top