Home directorie not mapping

[Ryan]

In our environment, I have created a DFS structure pointing all user Home
Directories to a DFS link in AD. This has been working very well for several
months, but on Monday, July 13, the home directory stopped mapping for some
users. In ADUC, I am pointing home directories to \\domain\home\%username%,
which resolves immediately to \\domain\home\user.name. If I change ADUC to
point to the actual server hosting the home directories, the drive maps fine.
I have verified permissions and can access the home directories by going
Start | Run | \\domain\home\%username% or \\domain\home\user.name.

Does anybody have any ideas as to why this is happening?

[DaveMills]

You are placing the home folder directly in the DFSRoot folder. ADUC will create
a folder %username% in the DFSRoot (i.e. \\domain\home). It will NOT create a
DFS link called %username% and point that to another server.

You should have something like \\Domain\DFSRoot\Home when Home is a DFSFolder
with links to \\Server\Home.

Post by Ryan
In our environment, I have created a DFS structure pointing all user Home
Directories to a DFS link in AD. This has been working very well for several
months, but on Monday, July 13, the home directory stopped mapping for some
users. In ADUC, I am pointing home directories to \\domain\home\%username%,
which resolves immediately to \\domain\home\user.name. If I change ADUC to
point to the actual server hosting the home directories, the drive maps fine.
I have verified permissions and can access the home directories by going
Start | Run | \\domain\home\%username% or \\domain\home\user.name.
Does anybody have any ideas as to why this is happening?

[Ryan]

in our DFS structure, our Home Directories are pointing to
\\domain\DFSRoot\Home. Within the Home folder, we have hundreds of folders
for our users, thus giving the \\domain\DFSRoot\Home\%username% structure.

When I go into ADUC and change the home folder to
\\domain\DFSRoot\Home\%username%, I get a message stating the directory
already exists, which it does, and the security properties will be applied to
give the particular users correct rights. This appears to be working fine.
However, when a user logs on, the drive is not mapped. To make things worse,
this did work until Monday, July 13.

Post by DaveMills
You are placing the home folder directly in the DFSRoot folder. ADUC will create
a folder %username% in the DFSRoot (i.e. \\domain\home). It will NOT create a
DFS link called %username% and point that to another server.
You should have something like \\Domain\DFSRoot\Home when Home is a DFSFolder
with links to \\Server\Home.

Post by Ryan
In our environment, I have created a DFS structure pointing all user Home
Directories to a DFS link in AD. This has been working very well for several
months, but on Monday, July 13, the home directory stopped mapping for some
users. In ADUC, I am pointing home directories to \\domain\home\%username%,
which resolves immediately to \\domain\home\user.name. If I change ADUC to
point to the actual server hosting the home directories, the drive maps fine.
I have verified permissions and can access the home directories by going
Start | Run | \\domain\home\%username% or \\domain\home\user.name.
Does anybody have any ideas as to why this is happening?

--
Dave Mills
There are 10 types of people, those that understand binary and those that don't.

[DaveMills]

OK, that's not what you said at first, so moving on.

Can the user map the drive at the command prompt using the DFS path? Can they
browse the DFS tree to get to their folder. Do the NTFS permissions on the
folder DOMAIN\DFRRoot (the physical folder i.e. C:\DFSRoot or wherever it is
shared from allow read access to the users.


Is this connected to a TCP port or USB?

Post by Ryan
in our DFS structure, our Home Directories are pointing to
\\domain\DFSRoot\Home. Within the Home folder, we have hundreds of folders
for our users, thus giving the \\domain\DFSRoot\Home\%username% structure.
When I go into ADUC and change the home folder to
\\domain\DFSRoot\Home\%username%, I get a message stating the directory
already exists, which it does, and the security properties will be applied to
give the particular users correct rights. This appears to be working fine.
However, when a user logs on, the drive is not mapped. To make things worse,
this did work until Monday, July 13.

Post by DaveMills
You are placing the home folder directly in the DFSRoot folder. ADUC will create
a folder %username% in the DFSRoot (i.e. \\domain\home). It will NOT create a
DFS link called %username% and point that to another server.
You should have something like \\Domain\DFSRoot\Home when Home is a DFSFolder
with links to \\Server\Home.

Post by Ryan
In our environment, I have created a DFS structure pointing all user Home
Directories to a DFS link in AD. This has been working very well for several
months, but on Monday, July 13, the home directory stopped mapping for some
users. In ADUC, I am pointing home directories to \\domain\home\%username%,
which resolves immediately to \\domain\home\user.name. If I change ADUC to
point to the actual server hosting the home directories, the drive maps fine.
I have verified permissions and can access the home directories by going
Start | Run | \\domain\home\%username% or \\domain\home\user.name.
Does anybody have any ideas as to why this is happening?

--
Dave Mills
There are 10 types of people, those that understand binary and those that don't.

[Ryan]

Users can map the DFS path after they are logged in either by using Net Use
or mapping via Windows.

The DFSRoot allows read access to the Users group. Folders within the
DFSRoot have NTFS and share permissions applied.

Users are trying to access the shares via a TCP port.

This is only happening on Vista machines. If I log onto a Server 2003 or XP
box, everything works fine.

Post by DaveMills
OK, that's not what you said at first, so moving on.
Can the user map the drive at the command prompt using the DFS path? Can they
browse the DFS tree to get to their folder. Do the NTFS permissions on the
folder DOMAIN\DFRRoot (the physical folder i.e. C:\DFSRoot or wherever it is
shared from allow read access to the users.
Is this connected to a TCP port or USB?

Post by Ryan
in our DFS structure, our Home Directories are pointing to
\\domain\DFSRoot\Home. Within the Home folder, we have hundreds of folders
for our users, thus giving the \\domain\DFSRoot\Home\%username% structure.
When I go into ADUC and change the home folder to
\\domain\DFSRoot\Home\%username%, I get a message stating the directory
already exists, which it does, and the security properties will be applied to
give the particular users correct rights. This appears to be working fine.
However, when a user logs on, the drive is not mapped. To make things worse,
this did work until Monday, July 13.

Post by DaveMills
You are placing the home folder directly in the DFSRoot folder. ADUC will create
a folder %username% in the DFSRoot (i.e. \\domain\home). It will NOT create a
DFS link called %username% and point that to another server.
You should have something like \\Domain\DFSRoot\Home when Home is a DFSFolder
with links to \\Server\Home.

Post by Ryan
In our environment, I have created a DFS structure pointing all user Home
Directories to a DFS link in AD. This has been working very well for several
months, but on Monday, July 13, the home directory stopped mapping for some
users. In ADUC, I am pointing home directories to \\domain\home\%username%,
which resolves immediately to \\domain\home\user.name. If I change ADUC to
point to the actual server hosting the home directories, the drive maps fine.
I have verified permissions and can access the home directories by going
Start | Run | \\domain\home\%username% or \\domain\home\user.name.
Does anybody have any ideas as to why this is happening?

--
Dave Mills
There are 10 types of people, those that understand binary and those that don't.

--
Dave Mills
There are 10 types of people, those that understand binary and those that don't.

[DaveMills]

I'm out of ideas now then.

Post by Ryan
Users can map the DFS path after they are logged in either by using Net Use
or mapping via Windows.
The DFSRoot allows read access to the Users group. Folders within the
DFSRoot have NTFS and share permissions applied.
Users are trying to access the shares via a TCP port.
This is only happening on Vista machines. If I log onto a Server 2003 or XP
box, everything works fine.

Post by DaveMills
OK, that's not what you said at first, so moving on.
Can the user map the drive at the command prompt using the DFS path? Can they
browse the DFS tree to get to their folder. Do the NTFS permissions on the
folder DOMAIN\DFRRoot (the physical folder i.e. C:\DFSRoot or wherever it is
shared from allow read access to the users.
Is this connected to a TCP port or USB?

Post by Ryan
in our DFS structure, our Home Directories are pointing to
\\domain\DFSRoot\Home. Within the Home folder, we have hundreds of folders
for our users, thus giving the \\domain\DFSRoot\Home\%username% structure.
When I go into ADUC and change the home folder to
\\domain\DFSRoot\Home\%username%, I get a message stating the directory
already exists, which it does, and the security properties will be applied to
give the particular users correct rights. This appears to be working fine.
However, when a user logs on, the drive is not mapped. To make things worse,
this did work until Monday, July 13.

Post by DaveMills
You are placing the home folder directly in the DFSRoot folder. ADUC will create
a folder %username% in the DFSRoot (i.e. \\domain\home). It will NOT create a
DFS link called %username% and point that to another server.
You should have something like \\Domain\DFSRoot\Home when Home is a DFSFolder
with links to \\Server\Home.

Post by Ryan
In our environment, I have created a DFS structure pointing all user Home
Directories to a DFS link in AD. This has been working very well for several
months, but on Monday, July 13, the home directory stopped mapping for some
users. In ADUC, I am pointing home directories to \\domain\home\%username%,
which resolves immediately to \\domain\home\user.name. If I change ADUC to
point to the actual server hosting the home directories, the drive maps fine.
I have verified permissions and can access the home directories by going
Start | Run | \\domain\home\%username% or \\domain\home\user.name.
Does anybody have any ideas as to why this is happening?

--
Dave Mills
There are 10 types of people, those that understand binary and those that don't.

--
Dave Mills
There are 10 types of people, those that understand binary and those that don't.