XP user can't access shared drive on Windows 2000 Server

Hello Experts,

XP user can't access shared drive on Windows 2000 Server.

Server W2K
Client XP Pro SP3

Server is in it's own workgroup and on a different VLAN.

Client is on W2K3 AD domain.

Firewall rules allow Client to see Server.

Attached is the error message.

Any help will be appreciated.  Thanks.  

Alicia

error.zip
Alicia PerilloAsked:
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.

johnb6767Commented:
Looks like they already have a mapping to this server .....

From the workstation....

start>run>cmd

then type.....

'net use'

See what connections are being made to this server.

You can then delete them by using the 'net use j: /del' command. (replace j: as needed of course....
0
dlan75Commented:
Hi,
this is typically a rights problem.
make sure your users have the proper rights to access the share (even in the security tab)
reverify your firewall settings
disable or reconfigure windows firewall or any other antivirus on the server and / or on the workstation
0
Alicia PerilloAuthor Commented:

Yes, I disconnected his mapping and then tried again but nothing happens i.e. no window for the share and no error msg.

When I try from a different computer with the same username and password it works.
0
Newly released Acronis True Image 2019

In announcing the release of the 15th Anniversary Edition of Acronis True Image 2019, the company revealed that its artificial intelligence-based anti-ransomware technology – stopped more than 200,000 ransomware attacks on 150,000 customers last year.

dlan75Commented:
look at firewall, antivirus, etc.
to make sure it doesn't come from there, disable everything completely, if then it works, you will know where to look
0
Alicia PerilloAuthor Commented:
Already disabled FW - user won't be able to try again until tomorrow AM.
0
dlan75Commented:
on both machines?
let us know
0
Alicia PerilloAuthor Commented:
no on one machine FW and Vscan are running and I can access the share
0
dlan75Commented:
you can access it from the computer with another user? you said it is ok on another computer with the same user, can you try on the machine with another user?
0
Alicia PerilloAuthor Commented:

can't access the share on the machine with any user
0
dlan75Commented:
even with a domain admin account?
are you sure windows firewall is disabled?
can you access any other shares from that machine?
0
Jeff RodgersNetworks & Communications Systems ManagerCommented:
Can you ping the server by name?  What about FQDN?

Can you ping the server by ip?  If yes, try opening the share via IP address (i.e.  \\192.168.1.1\sharename)

It could be a dns issue from the client machine?  

Can the client machine access other resources on the network?

0
Alicia PerilloAuthor Commented:
even with the local administrator account - the server is not part of AD domain - it's in it's own workgroup.

others shares from the same workgroup as the server are accessible.
0
Alicia PerilloAuthor Commented:
I tried accessing using ip address but no luck.
0
Jeff RodgersNetworks & Communications Systems ManagerCommented:
Can you "see the share" but not access it?

Is the computer a member of the same workgroup?
0
dlan75Commented:
oh ok
well check the rights on the share, I don't see anything else like that, you are probably missing something somewhere (do it again maybe)
0
Alicia PerilloAuthor Commented:

no can't see the share at all

computer is not in the same workgroup - client is a member of the domain.
0
dlan75Commented:
look into share rights and permissions ! 90% sure your problem comes from there
0
Jeff RodgersNetworks & Communications Systems ManagerCommented:
But you can see the server though?

What about pinging the server from a command prompt?  
0
Alicia PerilloAuthor Commented:
everyone has permissions through the share and on the security tab.
0
dlan75Commented:
well sounds weird
you said the server is not on a domain, is the client on a domain?
when you access shares, does it the ask for a username and passord?
0
Alicia PerilloAuthor Commented:

can ping the server but can't access the share for user's computer

can ping the server and CAN access the share from another computer.

don't think it's share permissions.
0
Jeff RodgersNetworks & Communications Systems ManagerCommented:
For testing purposes only, try adding Anonymous to the share and then see if you can see it from the client.

Let us know the results.






0
Alicia PerilloAuthor Commented:
Ok user went home for the evening - will try again tomorrow.
0
asrdiasCommented:
Try the following on the client..

Netsh int ip reset reset.log
netsh int ip delete arpcache
netsh winsock reset
ipconfig /flushdns

Reboot

This will reset your network stack.

Case still the same issue try removing the network client for Microfot networks from you network interface card properties, reboot and add it again.
0
Alicia PerilloAuthor Commented:
All,

I tried Netsh solution above by asrdias and it seemed to help - that is, I was then able to access the share from the users machine with the correct user account. Since the client was a domain workstation and the server was not a domain member, but in a separate workgroup, I needed to connect to the share by computername\username and then enter the password.

However, when I logged off/on I was not able to access the share and the message stated the user was locked out.  

I then unlocked the user account on the server using lusrmgr.msc and tried again.  I received the same message every time I tried to logon to the share, stating that the user was locked out.  Each time, I unlocked the account but wasn't able to connect to the share with that account - it kept locking out.  This got me thinking that this might be a user account issue.  So, I created another user with a different name and tried to connect to the share with the new user account.  This worked and seems to be continuing to work now as a mapped drive.

Thanks to all for your help and input.

Alicia

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
asrdiasCommented:
Check that computer for virus or other unwanted software just in case.
Some virus use the user names and try to guess passwords to access shares. Conficker is known to do this.

Cheers
0
johnb6767Commented:
Need to find the source of the lockouts.....

Go to the Security Log, and look for the lockout event. There will be a Logon Type Code.

Reference it here for the type of login, as it might be a simple solution....

Logon Type Codes Revealed
http://www.windowsecurity.com/articles/Logon-Types.html
0
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 XP

From novice to tech pro — start learning today.