Can ping, can't map drive 1

[upnorth]

Hi,

My new XP laptop refuses to map to a share an NT 4.0 server in our DMZ, although it can ping this server just fine. Error message is "network path //server/share could not be found."

I can map to another server (Win2k) in the DMZ, so I don't *think* it's a firewall issue. I used this drive mapping on my two previous workstations (NT 3.5 and Win2k, respectively), and nothing has changed on the server since then. I'm re-using the same IP address that my last computer used.

What piece am I missing? Any suggestions would be much appreciated!

 

[mawilson]

Can you map to the ip address\sharename (\\xx.xx.xx.xx\sharename)

 

[upnorth]

Sadly, no -- I've tried both UNC and IP, but no go.

 

[mjbosko]

I belive your username/password for the account on the xp box needs to have a user account, with the same username/password, on the NT box.

This did work for me to get a similar issue resolved.

Mike

 

[upnorth]

Thanks for the reply, Mike. But my username and password are the same on each box, so that's not it either.

It's driving me crazy; I have a software application that needs that map. Everything looks to be in order but *something* is obviously off!

 

[bcastner]

Can you do it with the NET USE command from a CMD session, or does it fail during this as well?

When you say the server is in the DMZ, I am assuming it is on a different subnet. Have you tried making an LMHOSTS entry on the XP workstation first? (Requires a reboot to be effective).

 

[upnorth]

bcastner, good ideas! I did try NET USE yesterday and it failed there, but I haven't double-checked my LMHOSTS file...

(opening window to check)

Crud. It *is* listed already.

 

[emma2002]

How are your DNS settings?

 

[ReddLefty]

If \\xxx.xxx.xxx.xxx\share didn't work, then the LMHOSTS is not the issue.

Is Microsoft File and Print sharing enabled on the server?




"In space, nobody can hear you click..."

 

[upnorth]

emma2002, they're set appropriately.

ReddLefty, forgive my networking ignorance, but is Microsoft File and Print sharing even an option on that NT 4.0 server box? It's not something I remember ever coming upon (although it is enabled on the XP box, FWIW).

 

[bcastner]

It bothers me that the error message you are receiving is a Netbios error, but even the IP form fails. If it was a permissions issue the error returned would be different.

You should check the event log to see if additional messages were returned that could help.

A firewall could block the Netbios traffic to and from the server, but the IP form failure with Net use suggests some other connectivity issue is also at play.

Try this on the problematic workstation:

1. Remove Client for Microsoft Networking, File and Print Sharing, and any protocol besides TCP/IP. Then add them back.

2. Configure TCP/IP again, making certain that Netbios over TCP/IP is enabled on the properties sheet, DNS tab.

3. Use Device Manager to configure the NIC to 10 - Half Duplex, not "Auto".

Reboot and try again.

 

[upnorth]

bcastner, that's exactly what's haunting me about this whole issue -- the error message doesn't jibe.

I did try your excellent suggestions, one at a time, rebooting between each one, but I still can't map the drive. I'm *this far* from tossing the workstation and going back to my Win2k box...

 

[bcastner]

Worth a try, rebuild the Winsock service stacks on the problem machine:

http://members.shaw.ca/techcd/VB_Projects/WinsockFix.zip

This does not cure all ills, but it sure cures a lot of them with mysterious DNS failures.

 

[WTVA]

Try this.
CMD prompt ...
Use net use to delete all shared drive then use the net use to remap them but include user name info.
//comptername\shared persistent:yes /user: username
hope that makes sense.

 

[bcastner]

There are sections missing in this thread, so let me advise Forum members of the important aspects.

upnorth, the starter of this thread used the Winsock service stack repair tool recommended by forum member (me) and it solved the problem he had been experiencing.

upnorth was happy with the cure, but asked how Winsock service stack corruption could occur.

Forum user bcastner suggested that there were several ways, including poorly written registry cleaners, ad removal utilities, and trojan scan utilities; multiple adapters; user or Pilot error in trying to solve connectivity issues with repeated driver installs and/or hardware changes.

In any case, those with similar odd DNS resolution issues are still recommended to use the link I provided above to clean your Winsock service stacks. It cannot hurt, but no promises that Winsock corruption is in fact the problem you are facing with DNS resolution issues. This utility does a much more thorough job than the netsh int ip reset reset.txt suggestion by Microsoft.

Please search for "Slow Logons" on this site for my complete notions of DNS issues under XP.