Unable to acess Win2003 network drives from XP machine

[SteveDingle]

Heya All,

My current home set up:

Windows Server 2003 - latest updates installed
Windows XP on 2 PCs (ZoneAlarm as Firewall) - latest updates installed
Lynksys Router
DLINK Modem for internet access.

FWIW, I have rebooted network and all devices multiple times

My problem is that on the PC that login using network user accounts, I can no longer see the shared drives on the Server. I can PING the server from the DOS prompt but can't see the drives. If I try to select an existing mapped drive (using windows explorer), after waiting 10min+ expanding the MY COMPUTER tree and the selecting the drive:

"Microsoft Windows Network : The local device name is already in use"

I found an article on MSFT site about this error and followed the suggestions of removing existing shares and recreating them. I have tried that and what happens is:

- Deleted and re-create the share to the server drive, hit Finish
- See small message saying "Attempting to connecting to ..."
- I am then prompted for user name and password.
- At this point I put in my Login and Password and get the following message immediately:

"The user name you typed is the user name you logged in with. That user name has already been tried. A domain controller cannot be found to verify that user name"

Just to verify that the user name was ok I went to another PC and mapped a drive using MY login/password and it worked fine.

I have also tried the following:

1) Starting in SAFE MODE with Network Access - didn't help

Before restarting I cleared all the event logs and when I try to log in using safe mode with networking - I see the following errors in the various logs:

APPLICATION Log
----------------
UserEnv - Windows cannot obtain the domain controller name for your computer network. (The specified domain either does not exist or could not be contacted. ). Group Policy processing aborted.

SYSTEM LOG
---------
DCOM - DCOM got error "This service cannot be started in Safe Mode " attempting to start the service EventSystem with arguments "" in order to run the server: [unique key was here]

NetLogon - No Domain Controller is available for domain [Domain Name] due to the following:
There are currently no logon servers available to service the logon request.

Service Control Manager - The following boot-start or system-start driver(s) failed to load:
Cinemsup,eeCtrl,Fips,intelppm,mbmiodrvr,SPBBCDrv,SRTSPX,SYMTDI

2) If I log in using LOCAL User Account, I can then access the network drives but of course all my application settings and profiles would have to be setup again so this isn't really a solution.

Sorry for the long post, just wanted to provide as much info as possible


Toodles,
Steve Dingle

http://www.dsbusinesssolutions.co.uk

D&S Business Solutions Ltd

 

[nevets2001uk]

Part of this sounds like a DNS issue to me as those errors are suggesting the PC cannot find a Domain Controller.

You said you can ping the server. Did you do this using the IP? If so try pinging the name to see if the name is resolved to an IP. You could also try clearing the local DNS cache using ipconfig /flushdns in the command line. You could also use the nslookup command line tool to do some tests to see if DNS is working. Sepcifically check you can lookup the server name and also that you can find service records for the domain controller.

Once you've tried that and hopefully verified DNS is working trying connecting to a share using the UNC path \\SERVER\FOLDERNAME and see if the folder opens. If so try again with a drive mapping.

Steve G (MCSE / MCSA:Messaging)

 

[SteveDingle]

Heya Steve,

Thanks for quick response. I should start by saying I'm kinda naive when it comes to network stuff, my friend initially set this up for me but this problem is currently beyond his expertise ;-)

1) Ping {server name} - this worked
2) Cleared DNS cache - wasn't sure if it should work right away or not but didn't. I then rebooted and still no joy
3) I used NSLOOKUP command and got the following.

DNS request timed out.
timeout was 2 seconds.
*** Can't find server name for address [server ip address]: Timed out
Default Server: [this looks like my ISP provider server]
Address: [IP address currently set on server as second DNS server]

The first address for the DNS server is itself - 127.0.0.1

I wasn't sure if I should go further as I'm not familiar with NSLOOKUP (will read up on it now)

Thanks Again

Toodles,
Steve Dingle

http://www.dsbusinesssolutions.co.uk

D&S Business Solutions Ltd

 

[nevets2001uk]

After clearing the DNS cache can you ping the server name still? It seems that your DNS is the problem. NSLOOKUP is a good diagnosis tool and can read about at...

http://support.microsoft.com/kb/200525

You PC should be pointing at your local DNS server in order to query it for the local name resolution and to discover the available domain controllers to contact. I'd suggest opening up the network connection properties and checking the DNS settings point to your DNS server. I presume you have this setup on your 2003 server.

If your clients get their addresses by DHCP you can set that up to pass out the DNS settings instead.

Once your PC DNS settings are correct try some NSlookup tests and also try to connect to the UNC path or re-map the drive.

Assuming this works you may need to make some changes to ensure you can access external sources such as the Internet.

Steve G (MCSE / MCSA:Messaging)

 

[MarkDym]

Hi

Have you recently added the PC to the network? I would check that the computer has been added to the domain (Right-click My Computer, select Properties, then click the Computer name tab, and click the Change button, then type the name of your domain and follow the prompts). Once it is a member of the domain, it/you will be authorised to use the network.

If the problem persists and the domain controller is still not available, remove the PC from the domain by joining it to a workgroup (following the same procedure), then rejoin it to the domain.

Also, is the PC running WinXP Pro - WinXP Home cannot be joined to a domain... If it is running XP Home, then you will need to enable the Guest account on the Domain Controller (the server), before you will be able to access accounts.

Hope this helps.

 

[SteveDingle]

Hello MaryDym,
Thanks for your reponse. I am using XP Pro (should have said), also the PC's have been conected to the server for over a year.

The change that seems to have triggered this probem is that initially my Server was not able to access the Internet. My friend came in a made a few changes (sorry no log of what) which allowed the Server to access the internet, but seems to have caused this problem. However, because the server wasn't connected I had never run any updates for it. So as soon as I got access I applied all updates so at this point I don't know if it was the updates that caused the problem or the changes to the server to allow it access to the internet.

I am currently working thru Steve G's suggestion to see what I can find out

thx

 

[nevets2001uk]

Since settings were changed on the server, also check the DNS settings there. Make sure your DNS service is running and configured.

Your last post confirms my suspicion that DNS may be the likely cause. If you previously had the server and PC's using local DNS, out of the box you potentially wouldn't have been able to access the internet. Your friend may have pointed the server and PC's to use your ISP's DNS which would have fixed the Internet but broken internal DNS, which is required for AD to function correctly.

Does your friend remember the change(s) he/she made?

Steve G (MCSE / MCSA:Messaging)

 

[SteveDingle]

Heya Steve G.

A coupla things:

>> your PC should be pointing at your local DNS server

Pleading ignorance here. Here are the settings from Local area network connection - I have 2, Local Area and 1394

- Obtaining IP addr auto
- Use following DNS - [my server IP], [my ISP provider IP] (same as the server).

Advanced:
* IP Settings
IP - DHCP Enabled
For Default gateway - nothing
* DSN
2 setting from above, Append primary conn, Append parent suffix
* WIN
Win Address - {server ip], Enabe LMHOSTS Lookup,Enable Netbios over TCP/IP

Does this seem right?

Thanks

 

[SteveDingle]

Steve G

>> Does your friend remember the change(s) he/she made?

He doesn't :-( My bad too should have made notes and unfortunately he's on holiday and this is really getting to be a pain

Thanks for the help

 

[nevets2001uk]

Those settings sound OK for the client. Just to confirm, if you open TCP/IP settings and Advanced, under DNS "DNS Server addresses, in order of use" is the top IP address that of your Server?

If you type \\SERVERNAME in an explorer Window does it display a list of available shares?

Steve G (MCSE / MCSA:Messaging)

 

[SteveDingle]

>> is the top IP address that of your Server?
Yes

>> If you type \\SERVERNAME in an explorer Window

By explore I 1st tried Windows Explorer. If I do that, basically nothing happens. I then did it in Internet Explorer and after about 2 min I get an error saying windows can't find the server named ....

In Windows Explorer I expanded "my network places" and clicked on "Msft Windows Network" and after about 5 min I can see my network listed but am asked for a login and then I get the same message as before about that was same user etc...

I tried entering a different user name/pw and after about 10 min of churning it did give me access but PAINFULLY slow.

So just to mention again. On PC1, User1 - can't access network. If on PC 1, when prompted enter User 2 name/pw - I get access to drives. On PC 2 User 2 - can't access drives. But using User 1 name/pw when prompted I get access. Obviously this make no sense to me.

I tried playing around with NSLOOKUP but I hate to admit I just don't know what to look for (i.e. values to check etc...)

If its too complicated to walk me through settings I understand. My friend would know more about nslookup and the values to check and I could wait for him to get back from holiday if necessary



Toodles,
Steve Dingle

http://www.dsbusinesssolutions.co.uk

D&S Business Solutions Ltd

 

[nevets2001uk]

Did you try Mark suggestion of removing the computer from the domain and reconnecting it?

Steve G (MCSE / MCSA:Messaging)

 

[SteveDingle]

Yes I did, no luck. I recreated with PC off and then again with PC on.

Dunno if this helps any but I notice that when checking the properties of the computer object it contains a 'DSN name' which is [pc name].[network].local

I don't know how that information gets populated, as for me the fields are read-only

BTW, Mark sorry for Mary typo in my response :-0

 

[nevets2001uk]

Steve,

I'm going to go back to your original message as DNS sounds to be configured OK and maybe I jumped on that possibilty too fast. From experience it tends to be behind a lot of problems! It still sounds odd that you can't access the server

Your initial error was... "Microsoft Windows Network : The local device name is already in use"

This suggests an in use drive letter when trying to access the share. Have you added any local USB devices that might be trying to use a drive letter required for the mapping?

Since your friend made some change on your server perhaps check that they didn't add any login scripts etc that might also be using a drive letter required by the mapping.

When deleting the mapping and recreating did you try creating the mapping using a new drive letter? This could be worth a try as well.

Also check the client firewall and ensure file and printer sharing isn't being blocked. Long shot but worth a quick check.

On the server you could go to Computer Management, Shared Folders, Sessions and see if your clients are showing up in there. Perhaps even turn them off and check to ensure the connections are clearing. If not you can right click and disconnect them.

For an NSLOOKUP test (ok so I haven't completely dropped my theory that this isn't DNS) on the client type...NSLOOKUP
At the > Prompt type SET TYPE=SRV
Then type _ldap._tcp.yourdomainname (ie. _ldap._tcp.mycompany.local

If DNS is configured correctly and your AD service records registered it should return your domain controller information.

You could also look into running DCDIAG from the support tools on your server as it might highlight any problems that exist with your configuration.

Have you tried rebooting your domain controller if at all possible?

Steve G (MCSE / MCSA:Messaging)

 

[SteveDingle]

Heya Steve G.

Can't thank you enough for taking the time to help me out. Have tried to answer each question separately

>> Have you added any local USB devices
No

>> check ...login scripts
No scripts for sure, just changes to assorted DNS/IP stuff in both the server and the PC

>> did you try creating the mapping using a new drive letter?

Yep tried that

>> Also check the client firewall
Checked, all fine

>>> Computer Management, Shared Folders, Sessions

They was nothing showing up at all with both PC's 'logged in'... however, for grins and giggles on my other PC (PC 2) I mapped a network drive with login for PC 1. Then refreshed and now I can see that session.

To be honest it just doesn't seem like I'm actually logging into the network. Is there anything I can check from client PC which says you are connected to 'X' network.

>> For an NSLOOKUP test
>> type...NSLOOKUP

C:\NSLOOKUP
DNS request timed out.
timeout was 2 seconds.
*** Can't find server name for address [server ip]: Timed out
Default Server: [isp server address].net
Address: [isp ip] ( this is flagged as my second DNS Server)

>> At the > Prompt type SET TYPE=SRV

( At this point I get the following )

> SET TYPE=SRV
*** Can't find address for server TYPE=SRV: Non-existent domain

So I guess this does confirm the DNS isn't confirgured properly :-(

>> You could also look into running DCDIAG

I'll need to find the disk and install the support tools but figured would send the rest along

>> Have you tried rebooting your domain controller
Multiple Time. Basically this is home setup - I work outa my house so no one else to worry about

Thanks again

 

[nevets2001uk]

You're welcome. I just wish some of my ideas were working for you.

I find it odd that the ISP address is appearing for the NSLOOKUP. The error itself isn't an issue as you probably don't have a reverse lookup zone.

On the client on which you ran the NSLOOKUP can you verify once again that for the TCP/IP properties for the local area connection that the preferred DNS server is listed as the IP of your local DNS server? Remove any other secondary DNS settings (although take a note incase you need to put them back in).

On your server can you check the DNS event log and see if there are any errors there?

Steve G (MCSE / MCSA:Messaging)

 

[SteveDingle]

Heya Steve

>> Remove any other secondary DNS settings

Yes can confirm preferred is the IP for the server. When removing the second one I lost internet access and also I could not PING the server. Put it back all was well

>> On your server can you check the DNS event
>> log and see if there are any errors there?

Nothing in the DNS but I did check System - on my server - and saw this error.

"The computer [my pc] tried to connect to the server \\servername using the trust relationship by the [network] domain. However the computer lost the correct security identifier (SID)when the domain was reconfigured. Re-establish the trust relationship."

Is that asking me to drop/recreate the user? If I did that will I loose all me "setting" for desktop and applications :-(



Toodles,
Steve Dingle

http://www.dsbusinesssolutions.co.uk

D&S Business Solutions Ltd