Hi Everyone,
We have a Hyper-V virtual file server running Win2008 Standard 64bit.
It has one share, that is in dfs (no repl partners) and published to the domain.
When accessing the share through namespace "\\domainname.com\share", several users would freeze.
Explorer would just completely freeze and eventually come up after 2 or 3 mins.
This was affecting about 75% of our users and was random.
When accessing the share directly from the server "\\servername\share" it worked just fine.
The share is being used for folder redirection for My Documents.
So we tested by having the folder redirect to the namespace,
and then mapping a drive to the same folder driectly on the server, not the namespace.
Trying to access by double-clicking the My Docs folder cause the freeze,
but accessing from the mapped drive works fine.
We want to set up DFS to replicate, so we can have redundant file servers.
That is why we need to use the published shares.
This is a brand new Dell PowerEdge 2950-III with 16GB RAM and 2 Quad-Core Xeon 2.33 cpus.
The parent server is running Win2008 Standard 64bit,
and is only running the Hyper-V roll, nothing else.
Any help would be appreciated.
Thanks,
Chris
Chris
We have a Hyper-V virtual file server running Win2008 Standard 64bit.
It has one share, that is in dfs (no repl partners) and published to the domain.
When accessing the share through namespace "\\domainname.com\share", several users would freeze.
Explorer would just completely freeze and eventually come up after 2 or 3 mins.
This was affecting about 75% of our users and was random.
When accessing the share directly from the server "\\servername\share" it worked just fine.
The share is being used for folder redirection for My Documents.
So we tested by having the folder redirect to the namespace,
and then mapping a drive to the same folder driectly on the server, not the namespace.
Trying to access by double-clicking the My Docs folder cause the freeze,
but accessing from the mapped drive works fine.
We want to set up DFS to replicate, so we can have redundant file servers.
That is why we need to use the published shares.
This is a brand new Dell PowerEdge 2950-III with 16GB RAM and 2 Quad-Core Xeon 2.33 cpus.
The parent server is running Win2008 Standard 64bit,
and is only running the Hyper-V roll, nothing else.
Any help would be appreciated.
Thanks,
Chris
Chris