Machine can not connect to dfs share
Hi ,
I work on a domain environment with active directories and domain controllers in place. i am facing a wierd problem. one of the machine with full network access, firewall off and nothing blocking its access; cannot connect to DFS share. All the user profiles reside on the DFS share so the user can not even load the desktop.
This is not a profile level issue because none of the users can load their profiles on that computer. You can not even browse to DFS Share location with that computer. It has the same settings as other users but I do not know why this computer is having this problem.
One more thing, if I delete the user profile locally from the computer then it SOMETIMES loads fien from the server ONCE or TWICE but then fails on next restart. It is very unstable.
I work on a domain environment with active directories and domain controllers in place. i am facing a wierd problem. one of the machine with full network access, firewall off and nothing blocking its access; cannot connect to DFS share. All the user profiles reside on the DFS share so the user can not even load the desktop.
This is not a profile level issue because none of the users can load their profiles on that computer. You can not even browse to DFS Share location with that computer. It has the same settings as other users but I do not know why this computer is having this problem.
One more thing, if I delete the user profile locally from the computer then it SOMETIMES loads fien from the server ONCE or TWICE but then fails on next restart. It is very unstable.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Actually, I think this machine has some connectivity problem with DFS. Actually DFS used to reside on a differetn server before and that server is off the network for now. There is a new server on place which is hosting DFS.
This machine can communicate wtth the new server very fine and I can browse to all the shares on that machine fine but when it comes to domain address/dfs it fails.
This is so strange. I see a possibility that in it's registry it is remembering the address of the old server for DFS reference or may be I am wrong. But something is wrong at network level for sure.
This machine can communicate wtth the new server very fine and I can browse to all the shares on that machine fine but when it comes to domain address/dfs it fails.
This is so strange. I see a possibility that in it's registry it is remembering the address of the old server for DFS reference or may be I am wrong. But something is wrong at network level for sure.
ASKER
This machine is not clone of any other machine. it has it's own fresh wondows installation.
ASKER
There is actually one more piece to this information: My server's name is X and Domain name is Dname:
Now, if I do \\DName.local\dfs then it does not work BUT if I do \\X.DName.local\DFS then it loads like butter.
I have only one server on network at this moment which hosts DFS. then if I write DName.local then it should directly go to that address but it does not. But when i explicitly say that go to X.local\DFS then it browses to the location fine.
Now, if I do \\DName.local\dfs then it does not work BUT if I do \\X.DName.local\DFS then it loads like butter.
I have only one server on network at this moment which hosts DFS. then if I write DName.local then it should directly go to that address but it does not. But when i explicitly say that go to X.local\DFS then it browses to the location fine.
ASKER