tucktech
asked on
Network Drive, Location not available
Hello Experts,
I have a windows 2008 r2 server and windows 7 laptop. I am using active directory and group policies. For a specific computer I login and the home drive (network shared and redirected) gives a message of "location not available".
I am using DFS.
While in explorer I can use the relative path \\domain.ad\home\username path and I can get access for that user to their home folder.
I have tried to remap the with a different drive letter and the same bad results.
It does work ok on other workstations.
I have run virus scans, performed a check disk, un and rejoined the domain.
help.
Any thoughts?
I have a windows 2008 r2 server and windows 7 laptop. I am using active directory and group policies. For a specific computer I login and the home drive (network shared and redirected) gives a message of "location not available".
I am using DFS.
While in explorer I can use the relative path \\domain.ad\home\username path and I can get access for that user to their home folder.
I have tried to remap the with a different drive letter and the same bad results.
It does work ok on other workstations.
I have run virus scans, performed a check disk, un and rejoined the domain.
help.
Any thoughts?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Okay, so it fails whether or not the configuration comes from group policy. That implies a problem on the machine itself.
As [Wilder_Admin] notes, this could very well be a timing issue. The OS could be trying to map the drives before the network stack is fully operational. I'm not sure what you could do about that short of setting up a script to run after you log on. You could try new network card drivers, a new network card, or moving the machine to a new port in your switch....
As [Wilder_Admin] notes, this could very well be a timing issue. The OS could be trying to map the drives before the network stack is fully operational. I'm not sure what you could do about that short of setting up a script to run after you log on. You could try new network card drivers, a new network card, or moving the machine to a new port in your switch....
ASKER
Ok, so I did the following to progress.
I removed the laptop from the domain on the laptop itself. I then removed the computer name from active directory.
I rejoined the domain.
No I cannot get to the share of \\dfs-name\share\username.
I removed the laptop from the domain on the laptop itself. I then removed the computer name from active directory.
I rejoined the domain.
No I cannot get to the share of \\dfs-name\share\username.
ASKER
Ok, it appears to be a DFS problem. I changed the "mapping" from the FQDN to just the domain name. For example the share with DFS was \\domain.ad\sharename and now it is \\domain\sharename. It all works now. Not sure what I "tripped" to make the FQDN not work... any ideas or comments?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I have left the DFS to only contain the base name of the domain. For example, domainname versus domainname.ad. It appears to be working fine so I will leave it at alone.
ASKER
I have setup gp for default gp only, no workstation gp. I also verified to make sure.
Wilder_Admin, I added the net use command in the login script and this did not change aything.
I also just changed network connections to remove IP6.