Dropping network Mapped drives

I have about 5 various clients who sporadically loose their network mapped
drives to 1 NAS. When they try to reconnect they get an error that the
device name allready exists. - they can ping the device. Nothing in
event logs. Has anybody seen this?
looking for any help/suggestions

Thanks
Carl

"CarlN" <> wrote in message
news:...
>I have about 5 various clients who sporadically loose their network mapped
>drives to 1 NAS. When they try to reconnect they get an error that the
>device name allready exists. - they can ping the device. Nothing in
>event logs. Has anybody seen this?
> looking for any help/suggestions
>
> Thanks
> Carl
>
>


Does the NAS have two IPs associated with it or two NICs? Are you using
WINS? If so, look up the name and see if it's in there with more than one
IP.

Also, is the NAS using AD authentication?

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Please reply back to the newsgroup or forum to benefit from collaboration
among responding engineers, and to help others benefit from your resolution.

Ace Fekay, MCT, MCSE, MCSA 2003 & 2000, MCSA Messaging
Microsoft Certified Trainer

http://twitter.com/acefekay

For urgent issues, you may want to contact Microsoft PSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

I checked registery and noticed the following in nullsessionpipes
COMNAP
COMNODE
SQL\QUERY
SPOOLSS
netlogon
lsarpc
samr
browser
and the irpstacksize was only 16.
Could this be causing the issue?
regards

carl

"Ace Fekay [MCT]" <> wrote in message
news:%...
> "CarlN" <> wrote in message
> news:...
>>I have about 5 various clients who sporadically loose their network mapped
>>drives to 1 NAS. When they try to reconnect they get an error that the
>>device name allready exists. - they can ping the device. Nothing in
>>event logs. Has anybody seen this?
>> looking for any help/suggestions
>>
>> Thanks
>> Carl
>>
>>
>
>
> Does the NAS have two IPs associated with it or two NICs? Are you using
> WINS? If so, look up the name and see if it's in there with more than one
> IP.
>
> Also, is the NAS using AD authentication?
>
> --
> Ace
>
> This posting is provided "AS-IS" with no warranties or guarantees and
> confers no rights.
>
> Please reply back to the newsgroup or forum to benefit from collaboration
> among responding engineers, and to help others benefit from your
> resolution.
>
> Ace Fekay, MCT, MCSE, MCSA 2003 & 2000, MCSA Messaging
> Microsoft Certified Trainer
>
> http://twitter.com/acefekay
>
> For urgent issues, you may want to contact Microsoft PSS directly. Please
> check http://support.microsoft.com for regional support phone numbers.

"CarlN" <> wrote in message news:...
>I checked registery and noticed the following in nullsessionpipes
> COMNAP
> COMNODE
> SQL\QUERY
> SPOOLSS
> netlogon
> lsarpc
> samr
> browser
> and the irpstacksize was only 16.
> Could this be causing the issue?
> regards
>
> carl

Carl,

I'm not sure. You didn't respond to my questions, and you said you are using a NAS. I assumed you mean a third party NAS?

If the NAS is using AD authentication, and drives are being dropped, besides the possibility there are multiple names for the one IP, I would also think a possible DNS misconfig, meaning an ISP's or some external DNS address could be being used in the workstations and/or servers, including the NAS if it were a Windows box.

What machine did you get this info from?

Are there any event log errors on the workstations? If the NAS is a Windows machine, how about in its Event logs?

Ace

"CarlN" <> wrote in message news:...
>I checked registery and noticed the following in nullsessionpipes
> COMNAP
> COMNODE
> SQL\QUERY
> SPOOLSS
> netlogon
> lsarpc
> samr
> browser
> and the irpstacksize was only 16.
> Could this be causing the issue?
> regards

As far as the IRPStack, I don't think it is the problem. I've worked in a multitude of scenarios from employers to customers with 5 users to 4500 users, and not once did we have to alter reg settings, especially this one, to fix a mapped drive issue. It was usually basic stuff.

Here's more info on the stack
http://adaptivetechnologies.wordpres...-irpstacksize/
http://www.webopedia.com/TERM/I/IRPStackSize.html

But I wouldn't go changing it yet. I would like to rule out basic configuration FIRST.

If the NAS is a Windows machine, please state the OS version (2000, 2003, etc), as well as unedited ipconfig /all.

Also please post an unedited ipconfig /all from a sample workstation that is having the problem, as well as a DC, so we can rule out possible basic AD configuration issues.

Any of your DCs multihomed?
Is the NAS box multihomed?
Using WINS?

Thank you,
Ace

Sorry for not getting the info
It is a dell nas with 2 nics teamed to 1 IP. I checked DNS, Wins and all
ipconfig info. it has correct data.
Nothing in event logs, only happens to about 4 machines-

"Ace Fekay [MCT]" <> wrote in message
news:...
"CarlN" <> wrote in message
news:...
>I checked registery and noticed the following in nullsessionpipes
> COMNAP
> COMNODE
> SQL\QUERY
> SPOOLSS
> netlogon
> lsarpc
> samr
> browser
> and the irpstacksize was only 16.
> Could this be causing the issue?
> regards
>
> carl

Carl,

I'm not sure. You didn't respond to my questions, and you said you are using
a NAS. I assumed you mean a third party NAS?

If the NAS is using AD authentication, and drives are being dropped, besides
the possibility there are multiple names for the one IP, I would also think
a possible DNS misconfig, meaning an ISP's or some external DNS address
could be being used in the workstations and/or servers, including the NAS if
it were a Windows box.

What machine did you get this info from?

Are there any event log errors on the workstations? If the NAS is a Windows
machine, how about in its Event logs?

Ace

"CarlN" <> wrote in message news:...
> Sorry for not getting the info
> It is a dell nas with 2 nics teamed to 1 IP. I checked DNS, Wins and all
> ipconfig info. it has correct data.
> Nothing in event logs, only happens to about 4 machines-

Thank you for the info.

I'm not sure what you mean by "correct data" for the ipconfigs. Some admins believe if they use their ISP's DNS address, it would be a correct configuration. That's why I asked for ipconfig /alls. Many times you will find Microsoft engineers, MVPs, and others, request this info from posters to confirm settings, and if incorrect, make suggestions and recommendations to fix it.

Also, good to hear the NICs are teamed. Multihoming without teaming, can cause this, too. At least we've eliminated this possibility.

Therefore, I assume the 4 machines it's happening to (and all machines internally and using VPNs), are only using your internal DCs as their DNS addresses in their IP properties, and not an external DNS, ISP DNS or the router as a DNS address. You would be surprised at how many tiems we see this in the public forum with non-AD DNS addresses that cause a slew of problems, and finding that removing them, everything simply works.

Are these four machines laptops? If so, do they have multiple connections to the network, i.e., LAN hardwired and wireless? According to the following link, the error you are getting can be caused by the user switching up (inadvertently and unknowningly) between network connections, and will cause the inability to connect, because they were originally connected on the one network connection, then tried to reconnect on the other. This can happen if the users never restart, lock their workstations, and simply unlock their workstations and are connected with a different network connection. Case in point, users at home with their laptops, connected via VPN, then sign off, lock the laptop, then come into the office, and connecto on the wire or wireless, this may occur.

If a workstation, and they have a dialup, a VPN, or some other connectoid object on the machine, then disconnect, they will find this error may pop up as well.

So you see, with the questions I've been asking, it is to help me diagnose the problem for you, and not trying to illicit corporate data for any other means. It eliminates assumptions and additional communications. I mean you can change the internal domain name on the ipconfigd, but for the IPs, I assume they are in a private range, so they are safe.

Ace

Sorry for not being clear. All DNS servers are going thru our AD
integrated DNS. Only our DNS servers resolve names at our ISPs DNS , and
they use recurssion.
The WINS server also points to the correct server and WINS has just 1(the
correct) entry for this server as does DNS.

Thanks for being so thorough !


"Ace Fekay [MCT]" <> wrote in message
news:...
"CarlN" <> wrote in message
news:...
> Sorry for not getting the info
> It is a dell nas with 2 nics teamed to 1 IP. I checked DNS, Wins and all
> ipconfig info. it has correct data.
> Nothing in event logs, only happens to about 4 machines-

Thank you for the info.

I'm not sure what you mean by "correct data" for the ipconfigs. Some admins
believe if they use their ISP's DNS address, it would be a correct
configuration. That's why I asked for ipconfig /alls. Many times you will
find Microsoft engineers, MVPs, and others, request this info from posters
to confirm settings, and if incorrect, make suggestions and recommendations
to fix it.

Also, good to hear the NICs are teamed. Multihoming without teaming, can
cause this, too. At least we've eliminated this possibility.

Therefore, I assume the 4 machines it's happening to (and all machines
internally and using VPNs), are only using your internal DCs as their DNS
addresses in their IP properties, and not an external DNS, ISP DNS or the
router as a DNS address. You would be surprised at how many tiems we see
this in the public forum with non-AD DNS addresses that cause a slew of
problems, and finding that removing them, everything simply works.

Are these four machines laptops? If so, do they have multiple connections to
the network, i.e., LAN hardwired and wireless? According to the following
link, the error you are getting can be caused by the user switching up
(inadvertently and unknowningly) between network connections, and will cause
the inability to connect, because they were originally connected on the one
network connection, then tried to reconnect on the other. This can happen if
the users never restart, lock their workstations, and simply unlock their
workstations and are connected with a different network connection. Case in
point, users at home with their laptops, connected via VPN, then sign off,
lock the laptop, then come into the office, and connecto on the wire or
wireless, this may occur.

If a workstation, and they have a dialup, a VPN, or some other connectoid
object on the machine, then disconnect, they will find this error may pop up
as well.

So you see, with the questions I've been asking, it is to help me diagnose
the problem for you, and not trying to illicit corporate data for any other
means. It eliminates assumptions and additional communications. I mean you
can change the internal domain name on the ipconfigd, but for the IPs, I
assume they are in a private range, so they are safe.

Ace

"CarlN" <> wrote in message news:...
> Sorry for not being clear. All DNS servers are going thru our AD
> integrated DNS. Only our DNS servers resolve names at our ISPs DNS , and
> they use recurssion.
> The WINS server also points to the correct server and WINS has just 1(the
> correct) entry for this server as does DNS.
>
> Thanks for being so thorough !

You are welcome.

Thanks for responding to some of the questions. Still didn't answer anytihng about the workstations or laptops (still don't know which). This is getting a bit challenging to help without knowing more.

Therefore, I am going to ASSUME that the workstations or laptops have more than one connection and the users are toggling back and forth between them (such as wireless, LAN, etc). If you do the following, does it work for them?

net use \\server1\share /D
or
Assuming "T:" drive:
net use t: /d

net use t: \\servername\sharename

Does it reconnect? If not, read the following articles to see if they help.

You may receive the "The local device name is already in use" error message when you try to restore a network mapping connection to a shared network folder on a Windows XP-based client
http://support.microsoft.com/kb/890413

"Local Device Name Is Already In Use" Error Message
http://support.microsoft.com/kb/317021

Mapped Drive Connection to Network Share May Be Lost
http://support.microsoft.com/kb/297684

How to connect and disconnect a network drive in Windows XP
http://support.microsoft.com/kb/308582

Ace

Thaanks again. The affected users do have 2 nics, cable and 802.11 . The
802.11 turns off on cable ethernet connnections. Other commonalities, They
connect thru a fortinet vpn and use RDP.

Carl
"Ace Fekay [MCT]" <> wrote in message
news:...
"CarlN" <> wrote in message
news:...
> Sorry for not being clear. All DNS servers are going thru our AD
> integrated DNS. Only our DNS servers resolve names at our ISPs DNS , and
> they use recurssion.
> The WINS server also points to the correct server and WINS has just 1(the
> correct) entry for this server as does DNS.
>
> Thanks for being so thorough !

You are welcome.

Thanks for responding to some of the questions. Still didn't answer anytihng
about the workstations or laptops (still don't know which). This is getting
a bit challenging to help without knowing more.

Therefore, I am going to ASSUME that the workstations or laptops have more
than one connection and the users are toggling back and forth between them
(such as wireless, LAN, etc). If you do the following, does it work for
them?

net use \\server1\share /D
or
Assuming "T:" drive:
net use t: /d

net use t: \\servername\sharename

Does it reconnect? If not, read the following articles to see if they help.

You may receive the "The local device name is already in use" error message
when you try to restore a network mapping connection to a shared network
folder on a Windows XP-based client
http://support.microsoft.com/kb/890413

"Local Device Name Is Already In Use" Error Message
http://support.microsoft.com/kb/317021

Mapped Drive Connection to Network Share May Be Lost
http://support.microsoft.com/kb/297684

How to connect and disconnect a network drive in Windows XP
http://support.microsoft.com/kb/308582

Ace