I have a windows 2003 R2 SP2 server that I'm using as a file server to store user home drives. The files are all stored on a LUN on an equallogic PS400E array. The server is using a QLOGIC QLE4060C iSCSI hba with SANsurfer iSCSI HBA Manager software V 5.00.32 to connect to the LUN.
I have a handfull of clients that will randomly lose their mapped home drives, and when I say lose i mean they disappear completely. The funny thing is that none of the other mapped drives seem to be affected, nor does e-mail, internet connectivity, etc. The mapped drives that are unaffected are on other servers which leads me to think that the problem is server-side, however i'm confused as to why this would only be affecting 6-10 users out of 1100.
All workstations are running windows XP SP2
All network drives are being mapped via a KIX logon script
Here are the steps I have taken thus far:
Originally I thought the problem was due to the server running low on nonpaged pool memory (There were a few errors stating this in the event log) so I followed this microsoft KB to disable the SNP Features. http://support.microsoft.c
I found that the power management option that allows windows to turn off the NIC card was enabled on some of the clients; I disabled it, but don't know if this has helped or not. I'm skeptical that it will do anything because no other network reliant applications and no other network drives are being affected.
I checked the GPO to see if the "Hide and Disable all items on the Desktop" option is configured, it isn't
I've looked through event logs on the server and the clients and can't find anything that looks to be related.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
ThorSG1: There is no disconnected network drive, the drive actually disappears, there is no trace of it.
fm250: Yes they have domain accounts, permissions are set properly; the network drive maps properly, but will randomly disappear at some point during the day after they have already been using it. it could happen after 20 minutes, or after 5 hours. I have tried mapping them normally, but can't tell if this has made a difference or not, just because of how random these problems are (I haven't had any re-occurence of the issue on the clients that I have manually mapped for, but there again, i have had the issue just go away on clients that I haven't touched.)
Let's see if they gonna disappear after manually connected!!
One other thing to check is the scripts; so check carefully for any disccounnect command within them. or if any script that could have been set to run at some pointing time as this is wiered problem that doesn't seem to be a network one. if it was a network, you would see the drives but with no connection. I think there is something that trigger the discounnection.
Is there anything common about the 6-10 users? Are they on the same VLAN? Same PC hardware?
It should not have anything to do with the disk array if you are not seeing any errors in the event log. Nor the power management on you network card. If it were you would be seeing a lot more issues with all your users. It would not be a bad idea to leave the power management off though.
It also sounds like something native to the local computer or as fm250 said possibly a script issue.
Is your KIX script mapping via user groups? Are the groups common between these 6-10 users? Do they have a common group that others do not. I have not worked with KIX for a few years so bear with me on that one. Does your KIX script do any checking to see if the drive is attached already? Are there any disconnect statements in the script?
Is there anything running in the users startup folder?
Are there any scheduled tasks on the client computers?
There is a disconnect statement in the script, but it comes before the line to map the drive; Is it even possible that this would cause the disconnect? The other mapped drives are all mapped in the identical way and we aren't having any issues with any of them.
There's nothing running in the startup folders, and no scheduled tasks.
Ok. It shouldn't be that script then. Do you only have one script that you are using for everyone or are you using different scripts? Have you checked group policy to see if there is another script defined somewhere?
This is a very strange thing. I've never heard of anything like this before. I will keep looking though. I appologize if I'm being redundant but just trying to troubleshoot out the possible causes.
So are there any common groups or anything common about there network settings?
Are the computers running XP and what service pack are they running. I saw a couple of posts about pre SP2 having an issue like this.
I also saw this post. I'm not sure about this on though.
http://techrepublic
I also saw some post about GP should not have this set: "Hide and disable all items on the desktop"
This is the portion of the kix script that maps the most common drives for all users. There are a couple of other statments that say if in group x map drive y, but i'm not having any problems with those drive mappings and they are using different drive letters than the drive i'm having problems with, which is H:
USE P: /DELETE /PERSISTENT
USE R: /DELETE /PERSISTENT
USE S: /DELETE /PERSISTENT
USE H: /DELETE /PERSISTENT
USE H: "\\CRP-FILESRV-P02\user_ho
USE P: "\\FILESRV01\Public"
USE R: "\\FILESRV01\Apps"
USE S: "\\FILESRV01\Data"
Everything looks good in the script.
See if anything in this post helps you.
http://www.kixtart.org
I also wanted to make sure you do not have the following in your script.
USE "*" /delete /persistent
You may want to try to open a cmd shell from kix and try mapping via net use for that drive. Making sure not to map it with the persistent switch. This would show weather it is an issue with kix or not.
I've seen a lot of post about this problem but none of them seem to have found an answer to the problem.
I would like to see you try mapping H in your kix script by opening a cmd shell and then using the windows net use command. That may shed some light on wheather it is something with kixtart or something else. I know I saw a post on how to do that somewhere. If you want to explorer that I can look for how to do that. Let me know this has definitely been an interesting one.
Business Accounts
Answer for Membership
by: ThorSG1Posted on 2008-10-24 at 19:54:46ID: 22801443
Check under disconnect network drive. Is there an orphaned connection there?