Net view produces error 53 on Win2K3 servers but W2K servers

  • Thread starter Thread starter Vince C.
  • Start date Start date
V

Vince C.

Hi.

We have a private network in 10.10.x.y with a W2K Active Directory domain
controller. We also have a remote site that accesses the private LAN with a
VPN tunnel. The remote site is 192.168.100.x.

When we run "net view \\server" on a W2K server on the private LAN, the
command succeeds and returns the shares defined on the remote machine -
server - that is inside the remote site. If we run the same command on a
W2K3 server, the command fails with an error 53 (network path not found). If
we run "ping server" right before running "net view \\server" the latter
succeeds!

I have put "192.168.100.x server" in both LMHOSTS and HOSTS on the W2K3
server but it doesn't help. The "net view" command always fails when run on
W2K3 servers. It always succeeds on W2K servers.

The VPN tunnel is fine for we can to pings to and from both sides of the
tunnel. We can see each side of the tunnel with, say, MSTSC (Terminal
Services Client), for instance. Hence the connectivity is guaranteed.

Does anybody have an idea?

Thanks in advance,
Vince C.
 
Assuming it works if you net view 2003 IP, you may just need to enable WINS server.

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
Hi.

We have a private network in 10.10.x.y with a W2K Active Directory domain
controller. We also have a remote site that accesses the private LAN with a
VPN tunnel. The remote site is 192.168.100.x.

When we run "net view \\server" on a W2K server on the private LAN, the
command succeeds and returns the shares defined on the remote machine -
server - that is inside the remote site. If we run the same command on a
W2K3 server, the command fails with an error 53 (network path not found). If
we run "ping server" right before running "net view \\server" the latter
succeeds!

I have put "192.168.100.x server" in both LMHOSTS and HOSTS on the W2K3
server but it doesn't help. The "net view" command always fails when run on
W2K3 servers. It always succeeds on W2K servers.

The VPN tunnel is fine for we can to pings to and from both sides of the
tunnel. We can see each side of the tunnel with, say, MSTSC (Terminal
Services Client), for instance. Hence the connectivity is guaranteed.

Does anybody have an idea?

Thanks in advance,
Vince C.
 
Thanks, Robert. WINS is already enabled in the WINS tab of TCP/IP advanced properties for the connection. The right WINS server is indicated there. It doesn't work anyway.

Note also that "net view local_subnet_server" works if local_subnet_server is in the same subnet as the W2K3 server we run the command on.

Vince C.
"Robert L [MS-MVP]" <[email protected]> a écrit dans le message de %[email protected]...
Assuming it works if you net view 2003 IP, you may just need to enable WINS server.

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
 
it is better to have WINS in both sites.

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
Should I have a WINS server on both sides?

Vince C.
"Robert L [MS-MVP]" <[email protected]> a écrit dans le message de %[email protected]...
Assuming it works if you net view 2003 IP, you may just need to enable WINS server.

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
 
Back
Top