Changing File Access Permissions - Problems Accessing
I have changed file access permissions on a workstation file folder. This isn't the first time I've done it and everything is working fine - well, almost.
I have it set up so that files are accessed using saved Credentials that match a user profile on the file "server".
Some computers can access the files right away.
Other computers get the familiar message: "Windows cannot access \\server\folder"
I have run these commands, because it was recommended:
arp -d *
nbtstat -R
ipconfig /flushdns
ipconfig /registerdns
(then reboot)
Again, sometimes this works and sometimes it doesn't.
I have found if I do this:
Run: \\servername then the shared folders are displayed but they can't be opened. Same message as above.
The same thing happens if I double click on the "server" in the Network list.
But, if I do this:
Run: \\[ipaddress] then the shared folders are displayed AND they CAN be opened.
There must be some simple thing that one can do to fix this... ???
(So far, all the computers involved are Windows 7 - including the "server". And, they aren't going to change any time soon.)
I have it set up so that files are accessed using saved Credentials that match a user profile on the file "server".
Some computers can access the files right away.
Other computers get the familiar message: "Windows cannot access \\server\folder"
I have run these commands, because it was recommended:
arp -d *
nbtstat -R
ipconfig /flushdns
ipconfig /registerdns
(then reboot)
Again, sometimes this works and sometimes it doesn't.
I have found if I do this:
Run: \\servername then the shared folders are displayed but they can't be opened. Same message as above.
The same thing happens if I double click on the "server" in the Network list.
But, if I do this:
Run: \\[ipaddress] then the shared folders are displayed AND they CAN be opened.
There must be some simple thing that one can do to fix this... ???
(So far, all the computers involved are Windows 7 - including the "server". And, they aren't going to change any time soon.)
Sounds like a DNS issue. Are the workstations in question pointing to the correct DNS server in your environment. If you can hit the server by ip and not by name check your dns settings on the workstations. Do an ipconfig /all and verify if they are in fact pointing to the correct dns server(s). You can also go in to your dns servers and verify if the server they are trying to hit has the correct ip in dns in forward and reverse lookup.
ASKER
I should mention that this is a peer-to-peer network.
That the folders are displayed in either case really goes beyond DNS doesn't it?
But, I rather wondered the same thing. So pinging by name seemed a reasonable test. When this is happening, ping by hostname works with no problem.
It looks like a permissions mismatch of some kind.
That the folders are displayed in either case really goes beyond DNS doesn't it?
But, I rather wondered the same thing. So pinging by name seemed a reasonable test. When this is happening, ping by hostname works with no problem.
It looks like a permissions mismatch of some kind.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Not requiring passwords on the server side might be a reason for file access to break.
ASKER