Jump to content

Recommended Posts

Posted (edited)

Wow, I've managed to completey disable all of our Windows 7 machines by simply adding a drive mapping to a DFS share in the login script

ie. net use w: \\domain.org.uk\Share

 

All I get now is a long delay at 'preparing your desktop' and eventually a black screen with the mousepointer - thats it - you can use ctrl+alt+del to logoff but otherwise its stuck

 

What fundamental flaw is there in Win7 that won't allow mapped drives for a DFS share! It works ok on XP?

 

Correction - I've just discovered its doing the same thing on XP machines as well! Argh!

Edited by Sheridan
Posted (edited)

Not sure how I've got the setup wrong? But its bascially killed every login!

 

It looks like they're hanging waiting for credentials to be entered for the DFS share? How can I check/change that? Everyone has read access to the shares?

 

Edit: It works fine for admins but no one else - so it must be a permissions thing. As its mapped to the root namespace I can't see any way of fixing this, but the non admin client are being asked for credentials in a command prompt in the background. Normally this would be hidden on login hence the system appears to be completely hung as it is waiting for a response.

Edited by Sheridan
Posted

Disabling the webclient makes no difference. Oddly mapping the drive to one of the servers that hosts the share works i.e \\domain.org\Share doesn't work but \\server\Share does work.

 

Also, if I take a user and apply no group policies it seems to work, but what group policy setting would causes a login to fail like this?

Posted
How can you check the NTFS permissions for the root DFS share? I've checked the shared folders listed under there and everyone has the correct access (read/execute etc)
Posted

I've done some testing and it seems random - with no policies applied it sometimes fails as well. A command prompt remains open saying 'Enter username and password for :' and thats what it hangs on. Even if you put valid credentials in you get Access Denied.

 

Seems to be unrelated to the login server, group policies or anything else I can think off. Looks like I'm stuffed for using DFS shares! Odd thing is this seemed to work when I had only the one 2008 R2 server with DFS, now I've added a second its all gone wrong.

Posted

This is getting more bizarre. I thought it might be down the login server the user gets, but a Windows 7 PC worked and the same user login failed on the XP! Rebooting both and then both fail - but all the time the user was getting the same login server. The failed on always hangs on the prompt for credentials though. Cancel that prompt and the PC works OK albeit with that drive mapping missing. Once you've cancelled the prompt and got the desktop if you try to access the (failed) mapped drive it asked for credentials with a windows prompt - which always failed with Access Denied. I don't understand this at all as this is on both Win7 and XP machines which otherwise work fine.

 

It seems unlikely to be permissions as it has worked - briefly!

Posted

Just a thought; I was increasing the security for IE and suddenly my installers (on a DFS share) refused to work and I summised it was because Windows was treating it as an external domain i.e. web content and therefore prevented me running.

Doesn't sound like your problem but if you have checked permissions ( including traverse folders I assume) then you have yo look somewhere else...

Posted (edited)

I've deleted and recreated the root namespace several times.

 

All I have is a basic namespace created as Read only for users/Read/write for admins. That appears as \\domain\DFS. Even if I try to map a drive at this stage it fails (even with no folders specified). I also tried just adding a single namespace server (i.e \\server\DFS) but mapping to that failed as well.#

 

Not sure whether its a group policy setting fouling things up as it always works for an Admin user - just not the other 99.9% of users!

 

The exact message I get in the command prompt is:

 

The password is invalid for \\domain\DFS

 

Enter the user name for 'domain\DFS':

 

Cancel that and you're logged in ok!

Edited by Sheridan
Posted
I've deleted and recreated the root namespace several times.

 

All I have is a basic namespace created as Read only for users/Read/write for admins. That appears as \\domain\DFS. Even if I try to map a drive at this stage it fails (even with no folders specified). I also tried just adding a single namespace server (i.e \\server\DFS) but mapping to that failed as well.#

 

Not sure whether its a group policy setting fouling things up as it always works for an Admin user - just not the other 99.9% of users!

 

The exact message I get in the command prompt is:

 

 

 

Cancel that and you're logged in ok!

 

Looking at that message it looks like it's trying to use \\domain\dfs as the username

 

As your admin is working it may be a permissions issue

 

Just an observation...

  • 4 months later...
Posted
I think that this is the problem that I am having on my domain as well. I am not positive that it is the problem, but it seems likely. We get the black screens for some users on some PC's. I never thought of the possibility that it could be a DFS issue. I will temporarily link all users to one server and see if that settles it. Thanks for the idea. I will try to remember to post back whether that fixes it for me. (In a few weeks)
Posted

Well, I looked around and found that the share on our backup file server (2nd target of our DFS) had a problem. I solved it with advice from a website that I will put in my next post. I will see if that helps in the future. The second target was disabled though, so I don't know why it should matter.

 

Wish me luck.

 

Merry Christmas!

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...