Can't "net use \\192.168.100.253\Myshare"

[Peter Kaufman]

XP SP2 client. Windows 2000 SP4 Server.

The XP client is not a member of the domain, but on the same subnet. I
can ping other servers/workstations, but cannot connect using "net
use". Firewall is OFF.

The error is always "1231 - The network location cannot be reached."
It does not matter if I supply credentials or not - I am never
prompted for credentials. The share name(s) I try to connect to are
correct.

Assistance tracking down the problem would be really appreciated. This
is driving me batty!

Peter

 

[John]

Don't you need a drive letter?
net use E: \\192.168.100.253\Myshare

 

[Peter Kaufman]

Solved.

Client for Microsoft networks was not checked in local connection
properties.

Isn't it amazing how often putting a problem down in writing will
prompt a solution or at least a new avenue of investigation!

Peter

 

[Chuck]

XP SP2 client. Windows 2000 SP4 Server.

The XP client is not a member of the domain, but on the same subnet. I
can ping other servers/workstations, but cannot connect using "net
use". Firewall is OFF.

The error is always "1231 - The network location cannot be reached."
It does not matter if I supply credentials or not - I am never
prompted for credentials. The share name(s) I try to connect to are
correct.

Assistance tracking down the problem would be really appreciated. This
is driving me batty!

Peter

Peter,

Is this maybe a browser (no not Internet Explorer) problem? Are there other
computers in the same domain / workgroup with this computer?

The Microsoft Browstat program will show us what browsers you have in your
domain / workgroup, at any time.
http://support.microsoft.com/?id=188305

You can download Browstat from either:
<http://www.dynawell.com/reskit/microsoft/win2000/browstat.zip>
<http://rescomp.stanford.edu/staff/manual/rcc/tools/browstat.zip>

Browstat is very small (40K), and needs no install. Just unzip the downloaded
file, copy browstat.exe to any folder in the Path, and run it from a command
window, by "browstat status". Make sure all computers give the same result.

For more information about the browser subsystem (very intricate), see:
http://support.microsoft.com/?id=188001
http://support.microsoft.com/?id=188305
<http://www.microsoft.com/technet/prodtechnol/winntas/deploy/prodspecs/ntbrowse.mspx>

How about you provide browstat information for the problem computer, and for a
couple computers that it can't net view.
Start - Run - "cmd". Type "browstat status >c:\browstat.txt" into the command
window - Open c:\browstat.txt in Notepad, make sure that Format - Word Wrap is
NOT checked!, copy and paste into your next post. Identify each computer by
name and operating system.

 

[Chuck]

Solved.

Client for Microsoft networks was not checked in local connection
properties.

Isn't it amazing how often putting a problem down in writing will
prompt a solution or at least a new avenue of investigation!

Peter

Good job, Peter. Sometimes the simplest settings can make a difference. Thanks
for updating your status.

 

[Peter Kaufman]

Thanks for that and the previous tip.

John - no, you don't need a drive letter but thanks for trying.

Peter

 

[Lucvdv]

Solved.

Client for Microsoft networks was not checked in local connection
properties.

And just when I was beginning to think it doesn't make much difference: as
long as you have one interface with Client checked it seems to be enough to
reach shares through other interfaces too.

I've got two machines, each in a different network, with a third network
connecting them.

10.1.0.5
10.255.255.1
|
10.255.255.2
10.13.1.11

Routing tables are set up so each machine can ping the other on both of its
addresses, that's probably why it works.

I can uncheck Client on the 10.255.255.* interfaces, as long as I leave
Sharing checked I can access shares on the 10.255.255 addresses.

With Client and Sharing both unchecked, I can still access the other side
on its other IP (i.e. from 10.255.255.1 to 10.13.1.11).

Isn't it amazing how often putting a problem down in writing will
prompt a solution or at least a new avenue of investigation!

About half of the usenet cries for help I write never get sent because I
find the solution while writing about the problem