Has anyone seen the following anomaly? When I first connect to the Samba server, I run a logon script that maps 5 shares to drives F,G,H,L,M. Some time later, when I check "My Computer", I find that the share mapped to H: has been mapped to all the remaining drive letters as well! For example, after I mount /users on G: and /programs on H:, I'll notice at some point later that I also have /programs mapped to I,J,K,L,M and so on through Z. I don't know when this actually happens since I notice it through the course of a days work. Has anyone heard of this before?? I'm running NT4WS/SP6. Thanks Dennis
> Has anyone seen the following anomaly? > > When I first connect to the Samba server, I run a logon script that maps > 5 shares to drives F,G,H,L,M. > Some time later, when I check "My Computer", I find that the share > mapped to H: has been mapped to all the remaining drive letters as well! > For example, after I mount /users on G: and /programs on H:, I'll notice > at some point later that I also have /programs mapped to I,J,K,L,M and > so on through Z. I don't know when this actually happens since I notice > it through the course of a days work. Has anyone heard of this before?? > I'm running NT4WS/SP6.Dennis I have had the same problem with Samba 2.0.5a-1 / NT 4 workstation -SP6. The only fix I was able to come up with was to not map drives in a logon script but map normally through Network Neigborhood and select to reconnect at logon. This is definitely a wierd problem and my guess is that it is a SP6 problem. Sincerely, Chuck Smith ------------------------------------------------------- The Bat! - automatic mail servant of Chuck Smith. The BAT! ver. 1.38e Windows NT 4.0 build 1381 Service Pack 6 Website : http://www.online-str.com You may also contact me via ICQ at 12185766. Give your child mental blocks for Christmas.
Hi, I had the same problem, but mine started with an NT installation which was successively patched up through SP4, SP5 and SP6 (with hotfix!). I also don't run a login script but mapped the drives F:, G: and H: by hand with instructions to reconnect at next login. The additional drives connected like I: thru to O: as the share connected to F:, then P: was always the share connected to G:, and then Q: to W: were (again) the share connected to F:. These would map downwards from I: over the course of several hours, so by about lunchtime I had a full set. These drives were not persistent, i.e. would not remap at next login, but would function correctly as normal network drives. I put the problem down to the way in which I installed my system because I have drives C: thru E: as Win 95 and then I installed NT to F: with G: and H: as CD-ROM drives. I then hacked the registry to move the NT partition to X: (and the CD drives to Y: and Z:) (this is why the shares were never connected beyond W:) and I wondered if I had done some damage so that this mapping behaviour could take place. Unfortunately, we'll never know because my NT partition destroyed itself last week and I had to perform a complete NT reinstall and the behaviour no longer occurs (though NT was installed in the same way as before). Are there any other common factors? I only had network drives set as persistent and "automagically" mapped from our primary Samba box, an UltraSparc 1 running Solaris 2.6 and Samba 2.05a. I use other Samba servers on site (2.03, 2.05a and 2.06) and these are mainly Intel-RedHat 5/6 boxes, but no shares from these have ever displayed the same behaviour. Weird? No kidding! Mike Robinson>> Has anyone seen the following anomaly? >> >> When I first connect to the Samba server, I run a logon script that maps >> 5 shares to drives F,G,H,L,M. >> Some time later, when I check "My Computer", I find that the share >> mapped to H: has been mapped to all the remaining drive letters as well! >> For example, after I mount /users on G: and /programs on H:, I'll notice >> at some point later that I also have /programs mapped to I,J,K,L,M and >> so on through Z. I don't know when this actually happens since I notice >> it through the course of a days work. Has anyone heard of this before?? >> I'm running NT4WS/SP6. >> >>Dennis > >I have had the same problem with Samba 2.0.5a-1 / NT 4 workstation >-SP6. The only fix I was able to come up with was to not map drives >in a logon script but map normally through Network Neigborhood and >select to reconnect at logon. This is definitely a wierd problem and >my guess is that it is a SP6 problem. > >Sincerely, >Chuck Smith====================================== This message contains information which may be confidential or privileged. Unless you are the addressee (or authorized to receive for the addressee), you may not use, copy or disclose to anyone the message or any information contained in the message. If you have received this message in error, please advise the sender by reply e-mail @sdli.com, and delete the message. Thank you for your cooperation. SDL, Inc.
Yes, I see these problems, too. We automatically map drives for users when they login. For reasons I cannot explain, they enounter two strange problems on occasion. First, users seem to loose their credentials with samba. When they first connect, they appear to be authenticated by our PDC and are given a vuid (valid uid, right?)..but later, they appear as nobody. A simple remapping of the drive clears things up. Second (this is a strange one), one of our users has problems saving files to the samba drive. NT reports that the drive is full. (The samba drive is on a raid array and there is plenty of space.) I'm not able to repeat these errors and I've never encountered the problems -- which makes it even more frustrating. I'm using the same configuration as the subject line, except I'm running on sol 2.6. Any ideas what to try next? Jean -------------- next part -------------- A non-text attachment was scrubbed... Name: jeannie.vcf Type: text/x-vcard Size: 228 bytes Desc: Card for Jean Henchey Url : http://lists.samba.org/archive/samba/attachments/19991222/ef557fd3/jeannie.vcf
I've just gotten around to reading the mailing list archives from last month and I saw your problem. We had the same problem starting with SP4. It was indirectly a result of using roaming profiles. Here's an example: I would log into one machine and map a drive to say F:. I would log out and go to another machine that would have an F: partition so NT couldn't use F: for that network drive. Starting with SP4, it got "helpful" and would try to map the network drive to another letter. But I guess they forgot to check for success and it just keeps mapping it until it runs out of letters. To fix this, I would have to go to a machine without an F: partition and unmap the network drive from F: and pick a higher letter. So, in summary, for a particular profile, if you have a network drive mapped to a letter that NT thinks belongs to a physical drive somewhere in the bowels of its little registry mind, NT tries to "fix" it by remapping it to another drive and forgets to stop when it succeeds. This is also why that other fellow saw problems when he changed the drive letters for his cdroms. NT still remembered somewhere in its registry the original letters for those drives and thought they were "taken." And to fix it, you resolve the conflict by unmapping the network drive from the letter in conflict. Absolutely not a samba problem. Ronni Dockins dockins@cs.sc.edu University of South Carolina