Esteemed Ladies and Gentlemen of the Samba list, I have a curious problem on one of my windows 2000 machines. As soon as the user connects to a samba share, they are disconnected and the drive appears marked with a red X The samba logs indicate that 10-20 seconds after any user of this machine connects to a network drive, they are disconnected. Oddly enough, you can browse the contents of the drives with no problems. You can also save documents to the network drives, but you get the following error message; "an error occurred while reconnecting W: to \\server\myshare. Microsoft Windows Network: The local device name is already in use. this connection has not been restored <OK>" Users are still able to save, however, but then they ask me what the message means, and I weep and tear out my hair. Seriously though, no big deal, but kind of annoying. Happens to two out of 100 users. I'll look through the M$ knowledge base and if I find anything I'll post it here. Thanks, --- Sam Barasch Computer Systems Support Department of Biostatistics University of Wisconsin Madison
More info would help. Are these drives the users home folders in the [homes] section of the smb.conf file? I ran into a problem similar to this quite often in a windows domain. What caused the problem is the user or someone had manually mapped the drives. In other words someone had either browsed the network and mapped drive or entered path to drive. Anytime a drive that is connected in users profile is also manually mapped you will get device already in use error. To test this just disconnect the drives and have user login again. If this is cause of problem error will go away. Hope this helps. On Monday 19 August 2002 15:37, Sam Barasch wrote:> Esteemed Ladies and Gentlemen of the Samba list, > > I have a curious problem on one of my windows 2000 machines. > > As soon as the user connects to a samba share, they are disconnected and > the drive appears marked with a red X > > The samba logs indicate that 10-20 seconds after any user of this machine > connects to a network drive, they are disconnected. > > > Oddly enough, you can browse the contents of the drives with no > problems. You can also save documents to the network drives, but you get > the following error message; > > "an error occurred while reconnecting W: to \\server\myshare. Microsoft > Windows Network: The local device name is already in use. this connection > has not been restored <OK>" > > Users are still able to save, however, but then they ask me what the > message means, and I weep and tear out my hair. > > Seriously though, no big deal, but kind of annoying. Happens to two out of > 100 users. > > I'll look through the M$ knowledge base and if I find anything I'll post it > here. > > Thanks, > > --- > Sam Barasch > Computer Systems Support > Department of Biostatistics > University of Wisconsin Madison-- Jerry Mercks, MCSE Phone: 256 881 1492 This private communication is intended for the named recipient(s) only. If you have received this message in error please delete at once and notify me at merckspub@comcast.net.
*Getting grey hair by the minute*
Hello All,
I set up a samba pdc for our office a month ago. All machines on the
network are Windows XP with a few Windows 2000 clients.
My Windows 2000 clients have joined the domain with out any problem. And are
having no problems with the PDC or the domain.
My Windows Xp clients have all joined the domain as well. Though, sometimes
after a couple of hours, a day, a week, the windows XP clients cannot logon
seemingly out of the blue. This is not all systems. Maybe half run into this
problem as where the other half have given me no problems what so ever.
The following error I receive is:
"Windows cannot connect to the domain, either because, the domain
controller
is down or otherwise unavailable, or because your computer account was not
found. Please try again later. If this message continues to appear contact
your Sys Admin for help."
I am using Samba Version 2.2.3a (Comes with RH 7.3)
First. Yes I do have the sign or seal patch applied. I also manually
checked the registry. It has been applied to the current control set and all
other controls sets just in case.
I have made sure the following in Local Security Policy is set:
I edited or checked the following entries:
"Domain member: Digitally encrypt or sign secure channel(Disabled)"
"Domain member: Disable machine account password changes(Disabled)."
"Domain member: Require strong (Windows 2000 or later) session
key(Disabled)"
Other questions:
Is the PDC down? NO
Are there other XP and Windows 2000 clients using the PDC at present: Yes
Do the machines have accounts? Yes
Were these machines working before on the domain? Yes
User accounts are located in the passwd and smbpasswd file
Machine accounts are located in the passwd and smbpasswd file as well.
The PDC is working. Machines are using it.
I been digging around quite a bit regarding this, and it seems like I am not
alone. But I have not found any answers or I have missed something very
simple..or maybe complicated.
Appreciate any help given
Cheers and Thanks
Sono