Local device name is already in use 'error'

[yanky]

For the past 3-4 months, several of my users workstations are
getting the error/warning stating - "Local device name is already in
use. Error occurred while reconnection x: to \\server\share". They
just click - ok. The x: drive is mapped currently. It is like the
machine wants to connect it twice. This only occurs the first time
they login in the morning.
We do not use login scripts. We map that drive via Windows
Explorer. I have tried disconnecting, rebooting and reconnecting, but
the next morning same error. The AD server is a Window 2000 Pro. We
also have 2 WIN NT 4 file servers. We are using mixed mode. They do
map one other drive to the same 2000 share with no problem and they map
a drive to one of the NT 4 servers with no problem.
I thought it was the FW, but disable for testing and it is still
happening. I checked and there are no sessions left open on the 2000
server for those users?

Any ideas?

Thanks
yanky

 

[Ace Fekay [MVP]]

In

For the past 3-4 months, several of my users workstations are
getting the error/warning stating - "Local device name is already in
use. Error occurred while reconnection x: to \\server\share". They
just click - ok. The x: drive is mapped currently. It is like the
machine wants to connect it twice. This only occurs the first time
they login in the morning.
We do not use login scripts. We map that drive via Windows
Explorer. I have tried disconnecting, rebooting and reconnecting, but
the next morning same error. The AD server is a Window 2000 Pro. We
also have 2 WIN NT 4 file servers. We are using mixed mode. They do
map one other drive to the same 2000 share with no problem and they
map a drive to one of the NT 4 servers with no problem.
I thought it was the FW, but disable for testing and it is still
happening. I checked and there are no sessions left open on the 2000
server for those users?

Any ideas?

Thanks
yanky

Is there a Home folder specified in their AD properties?

--
Ace

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

If you are having difficulty in reading or finding responses to your post,
instead of the website you are using, if I may suggest to use OEx (Outlook
Express or any other newsreader of your choosing), and configure a newsgroup
account, pointing to news.microsoft.com. This is a direct link into the
Microsoft Public Newsgroups, and it is FREE and DOES NOT require a Usenet
account with your ISP. With OEx, you can easily find your post, track
threads, cross-post, and sort by date, poster's name, watched threads or
subject.

Not sure how? It's easy:
How to Configure OEx for Internet News
http://support.microsoft.com/?id=171164

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft MVP - Windows Server Directory Services
Microsoft Certified Trainer
Assimilation Imminent. Resistance is Futile.
Infinite Diversities in Infinite Combinations.
=================================

 

[yanky]

We have 'Not Configured' anything on the Group Policies.

 

[yanky]

We have 'Not Configured' anything on the Group Policies.

 

[Ace Fekay [MVP]]

In

We have 'Not Configured' anything on the Group Policies.

I didn't say Group Policy.

What I said was to check the user's account properties in AD.

Just in case if you're not sure how to, but you probably know what I mean by
now, In Active Directory Users and Computers, rt-click the user's account
name, choose properties, click on the Profile tab, see if there is a home
folder mapped in the bottom of that property page.

Ace

 

[yanky]

Ace,

Sorry for the confusion....

I did check several User's Accounts, and none have a Home Folder
mapped.
Thanks,
yanky

 

[Ace Fekay [MVP]]

In

Ace,

Sorry for the confusion....

I did check several User's Accounts, and none have a Home Folder
mapped.
Thanks,
yanky

Is there a batch file under the same property page?

Ace

 

[Ace Fekay [MVP]]

In

Ace,

Sorry for the confusion....

I did check several User's Accounts, and none have a Home Folder
mapped.
Thanks,
yanky

Or to add, did an admin possibly connect to an admin share (C$, etc) and
didn't disconnect or did disconnect? That will cause that error as well.

Ace

 

[yanky]

Ace,
Thanks again for the reply...

There is not batch file in that same properties page.

Regarding the admin share: these workstations would not have a need
to connect to any admin share, just the file server shares.
(\\servername\sharename) In thinking it was a share issue, I thought
it may be the Anti-Virus software in which the def get pushed out every
morning. But then it would happen to all workstations.
I tried to review the registry for other possible differences. I
found one POSSIBLE difference with the MOUNTPOINTS? I haven't checked
every machine, but would this cause? But then why would it only happen
only at 'first logon' in the morning? I am stumped?

Thanks,
Fred

 

[Ace Fekay [MVP]]

In

Ace,
Thanks again for the reply...

There is not batch file in that same properties page.

Regarding the admin share: these workstations would not have a need
to connect to any admin share, just the file server shares.
(\\servername\sharename) In thinking it was a share issue, I thought
it may be the Anti-Virus software in which the def get pushed out
every morning. But then it would happen to all workstations.
I tried to review the registry for other possible differences. I
found one POSSIBLE difference with the MOUNTPOINTS? I haven't checked
every machine, but would this cause? But then why would it only
happen only at 'first logon' in the morning? I am stumped?

Thanks,
Fred

MOUNTPOINTS? I can't see how they will interfere, unless it's the next
logical letter or something? I've never heard of this happening, sorry.

Ace

 

[yanky]

Sorry Ace, I had compared 2 'ok' machines and 2 'not ok' machines and I
found that T(the drive that is trying to set a 2nd time to
\\servername\share) was in the registry MOUNTPOINTS. It was a shot.

I found it is machine specific. I had to get a user(who was getting
the error/warning) a new workstation 2 days ago. With his new machine,
he is not getting that error/warning. This morning, I tested his old
machine, and got the error. I checked the settings on the AD computers
and there was nothing different.

Any more thoughts?
BTW, thanks for your help

Fred

 

[Ace Fekay [MVP]]

In

Sorry Ace, I had compared 2 'ok' machines and 2 'not ok' machines and
I found that T(the drive that is trying to set a 2nd time to
\\servername\share) was in the registry MOUNTPOINTS. It was a shot.

I found it is machine specific. I had to get a user(who was getting
the error/warning) a new workstation 2 days ago. With his new
machine, he is not getting that error/warning. This morning, I
tested his old machine, and got the error. I checked the settings on
the AD computers and there was nothing different.

Any more thoughts?
BTW, thanks for your help

Fred

It might be that mountpoint. Does his new machine have that mount pointin
the reg? Since you are testing the old one, first backup that key in the
reg, or if XP, make sure you have a system restore point, then delete that
mountpoint entry, restart and see if it works.

Ace

 

[yanky]

I tried the above and found it is not the mountpoints.

Back to the 'drawing board'
thanks

 

[Ace Fekay [MVP]]

In

I tried the above and found it is not the mountpoints.

Back to the 'drawing board'
thanks

Sorry about that. As mentioned, this is usually due to a current connection,
whether it is a mapping or an IPC$ connection.

Hope you can find a resolve for this.

Ace