[JohnWill]

More information is always good.

[asuh]

Okay, I finally have an update! I couldn't do anything until end of business day and I'm on the left coast so people are finally leaving here.

We are still having the issue of losing connection upon reboot. I tried the net use command with and without the /savecred switch and it still breaks the connection. Using /savecred switch seems to conflict with /persist switch so that wasn't successful.

Either way, I can't seem to have these desktops keep the connection alive after a reboot.

[JohnWill]

Well, you could always put the NET USE command in the startup folder so they're remapped each boot.

[Squashman]

Originally Posted by JohnWill

Well, you could always put the NET USE command in the startup folder so they're remapped each boot.

Agreed. There doesn't seem to be any definitive reason as to why this happens or a definitive fix for it. But making a batch file to execute at startup should work.

Are these computers wired to the network or are they wireless? If they are wireless tt may be they are trying to map the drives before a network connection is present.

[asuh]

Man, I sure hope that startup folder suggestion isn't the main answer because that seems so janky!

All the computers are wired. We now have no wireless connections available.

[JohnWill]

I know that drive mapping works fine for me with wired systems, don't know what's going on there. I have to agree with the previous opinion, for some reason the mapping may be failing because it takes too long to get a connection.

Did you look in the Event Log of one of these systems to see if there's an error related to attempting to map the drive?

[asuh]

Originally Posted by JohnWill

Did you look in the Event Log of one of these systems to see if there's an error related to attempting to map the drive?

See my first post for the error I'm getting. This problem could certainly be related to a DNS error that I'm having but I don't know.

If I write a batch file that includes the net use, will this basically be recreating the mapped drive every time? All I need to happen on reboot is to log into the existing mapped drives, not create new ones.

[Squashman]

Have your batch file delete any existing mappings first and then recreate them.
I know it is kind of hokey but you gotta do what you gotta do to get things done sometimes. Back in the days of Win 9x the only way to get things to launch at startup was to put it in the startup folder. You should thank Bill for at least having that option in your time of need.

[asuh]

Originally Posted by Squashman

Have your batch file delete any existing mappings first and then recreate them.
I know it is kind of hokey but you gotta do what you gotta do to get things done sometimes. Back in the days of Win 9x the only way to get things to launch at startup was to put it in the startup folder. You should thank Bill for at least having that option in your time of need.

Oh no, don't get me wrong, I'll definitely thank Bill if/once I get this working correctly! It's the best solution yet!!

Let's talk hypothetical first: If I write this batch file to delete Q drive, recreate Q drive, and enter credentials, I shouldn't have to do this to every single mapped file on the same server, right? I'm assuming that once I recreate the one mapped drive, the other mapped drives will then be able to log in based on the fact that I logged into the one. Right?

Assuming so, how would I write this net use command? I'm not sure how to do it. Thanks for all your help so far!! You guys are amazing.

[JohnWill]

Actually, if the mappings are getting lost, you'll probably have to have a NET USE for each mapping.

I had overlooked the error you're getting, that appears to be what Squashman mentioned, for some reason the workstation isn't connected when the drive mappings are being attempted.

[asuh]

Originally Posted by JohnWill

Actually, if the mappings are getting lost, you'll probably have to have a NET USE for each mapping.

Upon reboot, all the mapped drives are there and do exist. In fact, I think any mapped drive to another Windows XP Home stays connected (although, I'm not at work and looking at this but I've only had a problem with the server). It's just that the mapped drives to the server need to be logged in after each reboot. Once I log into one, all of them are accessible.

Hmm... I think maybe I was a little unclear about what's going on. It's not that I'm completely losing all sign of a mapped drive after I log into the desktop after a reboot. Every original mapped drive appears but needs to be logged into again after every reboot. That's what causing the most problems since Quickbooks multiuser files are being shared centrally.

[JohnWill]

So, you have a user permissions issue, not a drive mapping issue, right?

Try running this on the server.


Create a file in notepad named FIXANON.REG with the following contents:

You should have 3 boxes on the bottom in NOTEPAD.
1)Filename : FIXANON.REG
2)Save as type: all files
3)Encoding: ANSI
If you do not change it from txt type to All files type, then the file will actually be FIXANON.REG.txt, this won't accomplish the desired result.

------------------- Use text after this line -------------------
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa]
"restrictanonymous"=dword:00000000
------------------- Use text before this line -----------------

Double click on the file and say Yes to the merge into registry question.

Reboot the computer.

[Squashman]

Do your users have the same username and password on server and their PC?

[asuh]

I'm sorry for my delayed response to this. It has been a hectic week and time was running short.

I have done as JohnWill suggested by patching the registry. I saw no change, however. It's possible that the reason is because I didn't reboot the server, but I'm going out of town for a few weeks and won't be able to revisit this problem until I'm back.

To answer Squashman's question, the local user accounts have different usernames and passwords, each unique to its own computer. There are no shared usernames and passwords on the server since it's running in its own domain and I'm not sure there would be any benefit to recreating these usernames and passwords in the domain that we're not using. Is there something I don't know?

Thanks for all your suggestions, guys! I'll report back as soon as I have something to say.

[Squashman]

If you map a drive to another computer and the user has the same credentials (ie: username and password) on both computers there shouldn't ever be a problem mapping the drive as long as they have permissions to access the share.