Discussion Locked

Can't access network share after Nimda

0 helpful
2 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have an NT 4.0 (SP6) that caught nimda. I cleaned it up using the Symantec fix and it's clean now, but certain users can no longer connect to the network shares (map a drive) on that computer. I've deleted and re-created the shares, made sure the user policies (usrmgr) allow "access from the network", but no go. I can attach no problem as admin, but user 'BatchPC' can't connect even if I make them a member of the admin group. If using 'net use \\server\share' from command line, I get 'Error 71: the request is not accepted by the network' (win98 client). I can browse to the server in NW Neighborhood on that computer (very slowly) and see the shares, but can't map or explore them. I think it must be a policy or permission issue, but I can't tell what. I do have a Win2000 server in the mix, but I don't know if that's having any effect. Suggestions, clues, or WAGs are solicited and encouraged.

--Steve

2 replies

by beermonster

Hi,
As far as I know there are two things which can cause this. Firstly if the shares themselves have a specific number of connections allowed and that limit is being exceeded, or the server itself has per server licensing and is out of licenses. That's where I'd look anyway. Good luck : )

by jovenpop

Thanks for the suggestion. The problem with the 'out of licenses' theory is that I can immediately log on to the server as a different user.

NEWS FLASH: I just tried deleting and re-adding the 'batch' user that couldn't connect, and whaddyaknow, now it works fine. Screwed up user rights? I'm still interested in your opinions...

--Steve

This discussion is closed to new replies.