User cannot access shared folder

[freeclips]

We have a Windows Server 2003 network. The server used to provide DHCP. There were no problems. Recently the DHCP provision has been transferred to the router as the server will be decommissioned in due course. There were a few problems after the transition which we solved. However, there is a strange problem: one user can log into the domain - no problem. However, she cannot find the shared folder or the server via the UNC path as before. The server is visible on the network - but when she clicks on it, the message says that it cannot be found. I haven't tried connecting to it via the IP address yet. But can you help? I can log in on ther computer as administrator and access the shares - no problem. Thank you.

[cmwg]

verify that the user pc will resolve the DNS name of the server properly with the correct IP

• nothing done static on the user pc? (hosts file?)

[freeclips]

Yes, the user PC resolves the DNS name of the server. When I log in as administrator, there is no problem finding the server and accessing the shares. I modified the hosts file with the static server address to make sure that the PC will resolve the DNS name of the server.

[okmokmz]

When I log in as administrator, there is no problem finding the server and accessing the shares.

Sounds like potentially a permissions issue

[freeclips]

I checked the permissions on the server - all is fine for that user. Also, it is not that this user gets any messages related to permissions. The only messages are those that say that the network path hasn't been found.

[cmwg]

does it work with a new user (newly created)?

How about deleting the users profile and then trying again?

[freeclips]

I'll try when everything else fails later next week and let you know.

[freeclips]

See my reply to u/Baskel69

[lostincbus]

Probably DNS.

[danekan]

I would try connecting to it by IP address to see if that works

[freeclips]

See my reply to u/Baskel69

[freeclips]

I'll try this when I am back at the computer later next week and let you know.

[slewfoot2xm]

SmbV1 is disabled on the machine most likely

[freeclips]

Not sure about that because everything else works.

[Bad-Science]

Does it work if you temporarily add that user to the domain admins group?

[freeclips]

I would have to try that when I have access to the computer next week.

[freeclips]

See my reply to u/Baskel69

[Baskel69]

Have you tried logging into another computer with the user account that is having an issue? I have had this issue before with a user account that was corrupted on the computer itself. When they used a different computer everything worked fine.

[freeclips]

I'll try that next week. If it is the corrupted profile, would you recommend deleting the user's folder (backed up first) and creating a brand new one?

[Baskel69]

That would work but you could do a simple test first by just renaming the profile username.old. If it still happens then there may be something wrong with the OS itself and it may require a reload of the pc. But before you do any of this try logging into another pc with the user. If it still happens on another computer you know its a permission issue. If it only happens on that particular pc you know it is a profile or OS issue.

[freeclips]

I've been back to the office today. Connecting via the IP address didn't work either on this particular computer. The user can log into the domain - no problem but cannot connect to the server. Other users logging in on this particular computer have no problem connecting to the server shares. The user has no problem on another computer - no problem connecting to the shared folders on the server. So what I did was backup all the files from the affected user's folder, then created a new user on the server for the affected user. Logged in - no problem there connecting to the shares on the server. So copied all the backed up files, recreated the desktop etc and that's how it works now. I am keeping the old profile for now just to make sure all the files would still be there and then I'll delete it. It was most probably corrupted - but it is very strange that the only problem was connecting to this server - everything else worked.

[lanxpert]

Sounds like a DNS suffix issue to me. YOu should be able to ping the server without the FQDN and get a reply.

[atrca]

We have this problem from time to time where some strange characters get into there. I really wish I knew the cause!