WSHNetwork.MapNetworkDrive vbs. script 80070035

Hello,

My college's application server had a severe hardware failure yesterday and we quickly rebuilt a new server giving it the same name and ip address as the old server. However, when I attempt to log in as a student our logon script is throwing a WSHNetwork.MapNetworkDrive Code 80070035 error saying it cannot find the path of the server. I have checked DNS, DHCP and WINS records, flushed DNS, and refreshed WINS registration but it doesn't help. The group policy that is executing the script is functioning up to the point that the script is called. What other reference could this script be looking for? The domain controller has the new server registered. I checked all the group policy entries and they refer to the server like this \\servername\path to scripts.
OteroJCAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

kyleb84Commented:
Can you ping "servername" from any of the workstations?

What happens if your type this in cmd on one of the workstations?:

net use * \\servername\share /User=[Username]

Where [Username] is a user that would utilise this script?
0
OteroJCAuthor Commented:
I can ping the servername but when I try to log in with the net use command it tells me that my username or password is invalid for accessing the machine. I'm going to try a couple of other machine to see if it is the same across the board.
0
OteroJCAuthor Commented:
Okay, I've tried several other machines and none of them recognize the username and password though I've verified that they exist in Active Directory and I can log on to in the individual workstation's with that account. I even tried it directly on the server itself and it didn't recognize it. Is it a bad DNS record?
0
kyleb84Commented:
"Is it a bad DNS record?"

Sounds like a context issue...

If you try:

net use * \\servername\share /User=[DOMAINNAME\Username]

Does it work then?
What about:

net use * \\servername\share /User=[SERVERNAME\Username]
0
OteroJCAuthor Commented:
Okay, finally found the problem. There was an issue with cached 'remembered connection' at the same time that the DHCP was handing out messed up records. Clearing both of those up solved the problem.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Networking

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.