Windows Forum

Ask something
Discussion Locked

Netuse system error 53 map drive on inet

0 helpful
5 replies

by ngunity

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have a system running on a public IP on the internet, on an ADSL link which I am unable to establish a mapped network drive to.

I have one site on the same Telco providers DSL service I can establish the link to using Net use, however all of myother DSL sites I am unable to establish the link. The net use command errors with:
System Error 53 has occurred. The network Path was not found.

I can ping the public IPs of all the servers I am trying to connect to but cannot map to the shares.
There is no firewalling that is blocking the transit, my packet sniffer shows that I am receiving replies back from the server but then seems to error with a packet that is described with:
Unreachable Port .netbios-nsIP

I have tried setting up the servers in my hosts and LMHOSTS files, and can ping them with their name accordingly, but no shares. I am connecting from a Win2k box to NT Workstations running at the public IPs as servers by the way.

can anyone help?

BTW Iknow this is unsecure as all hell, and I should use VPN but i want it working without ANY VPN solution before I implement the security

5 replies

by nettek

According to Microsoft, system error 53 has two causes:
1. The computer you are trying to connect to does not have File and Print Sharing enabled (or the "Allow others to view my files" checkbox is not checked), or
2. The second reason is the remote client cannot locate the \\computername.

Try using NET USE with the IP address (NET USE \\207.12.34.5\sharename, for example). If you can map a drive that way, you have a name resolution problem. If you still get the error using the IP address, then some security setting is preventing your remote PC from accessing your network share.

by shanghai sam

The share is definetely up, running NT on the remote by the way. I have tried using the Net use to IP command, as well as tried using the netbios name, resolved with the host file

I have been knocking over all security boundaries in the way, and there's just no real boundary left that I can find. Only one hardware firewall is in place, and I have granted full permission in and out for the specific IP, on all ports.

I am looking at setting up a PPTP solution if nothing else

thanks

by joseph moore

Try TELNETing to TCP port 139. If you cannot connect, then something is blocking the port between your machine and the remote machine. If you do connect, then there is something else going on.
Open a Command Prompt on your system that you want to connect FROM and type in:

TELNET ipaddress_of_remote_machine 139

If you connect successfully, then the Telnet screen should go blank and stay connected for 20 seconds. If the connection is blocked, then you will receive an immediate connection refused message.

It is my guess that something is blocking TCP port 139.

You could also get a port scanner to try and scan the remote machine to determine if the NetBIOS port is open, but that is something entirely different.

hope this helps

by shanghai sam

OK
The telnetting on 139 definitely shows something is blocking the connection. I am stumped as to what it could be, and if my PPTP solution works I may never work it out.

The telnet to one of my remote sites that I CAN map the share to succesffully established the conncetion on 139, the sites I can't get to do have a connection failed come up immediately.

Not working but at least you have proven it's being blocked

thank you

This discussion is closed to new replies.