Topic: Windows netlogon should depend on tcpip

[Brave Dave]

Just wondering if anyone else has seen this

I kept getting an errors logon onto my WinXP computer which was subservient to my SME Server as a domain computer, ultimately it would tell me that it could not log me onto my profile and log me onto a temporary profile, telling me my changes would be lost. I did have the event id's but have lost them.

The errors were various including

• No Domain Controller Available
• Cannot access a file (path to a file in my profile)

Solution for me was to modify:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\DependOnService

By Default it is dependent on : LanmanWorkstation
I added Tcpip (on separate lines)

i.e

LanmanWorkstation
Tcpip

I've come across the error a couple of times, always with embedded Gigabit Network Adapters  (on the M/Board), this has fixed it every time

[cactus]

Solution for me was to modify:
By Default it is dependent on : LanmanWorkstation
I added Tcpip (on separate lines)

I am not sure why this works for you, as the key you have modified only affects the start and stop order of windows services as this specified which should be running before the service for which this key is set is started.
You are now only enforcing another service to be started (Tcpip) in addition to an already existing (LanmanWorkstation). This does not change the service requirements, it only enforces your service to start after the other two are running successfully.

See also: http://technet.microsoft.com/en-us/library/cc963243.aspx

[Brave Dave]

affects the start and stop order of windows services

This is what I was trying to do, I tried others - Netman was one that had been suggested - in the end I tried Tcpip - because I wanted to ensure that DHCP had settled before the netlogon option was presented to the user. I had noted that if I left the machine to stabilise a bit before I control-alt-deleted I was able to logon without issue, so I figured something wasn't started fully.

This has fixed the problem, before that I had had to turn roaming profiles off once I found the issue - which had disappointed me.

[cactus]

I had noted that if I left the machine to stabilise a bit before I control-alt-deleted I was able to logon without issue, so I figured something wasn't started fully.

Is your computer that fast? Are you sure there is not something else causing this, like bad cabling a bad switch port or even a bad NIC?

This has fixed the problem, before that I had had to turn roaming profiles off once I found the issue - which had disappointed me.

That is nice, but it still seems a work around to me. It is a pity that M$ does not have a (public) bug tracker.

[mdo]

I had noted that if I left the machine to stabilise a bit before I control-alt-deleted I was able to logon without issue, so I figured something wasn't started fully.

Another workaround for this (which we often use) is to enable "Run logon scripts synchronously" via registry editor.

[CharlieBrady]

Another workaround for this (which we often use) is to enable "Run logon scripts synchronously" via registry editor.

Is there any reason that shouldn't be a standard recommended setting?

[Brave Dave]

Another workaround for this (which we often use) is to enable "Run logon scripts synchronously" via registry editor.

Thanks - I've seen this in the policy editor, will be worth looking at

[Brave Dave]

Is your computer that fast? Are you sure there is not something else causing this, like bad cabling a bad switch port or even a bad NIC?
That is nice, but it still seems a work around to me. It is a pity that M$ does not have a (public) bug tracker.

I think that all computers are fast - for XP, well maybe not Celerons, but WinXP on a standard new PC is very fast in light of what we used to have... post the BIOS boots, a Core2 is ready to Ctrl-Alt-Delete in about 15seconds - but the network may not have completed it's negotiation ...

I don't know that is a case of a MS Bug, I'm just thinking that it's more like a relay race - the Network Card passes the baton to the Network Card Driver, the Driver negotiates Speed with an upstream switch and hands the baton to the DHCP, the DHCP negotiates with the Server to get an IP and the Tcpip says I'm ready ! - Netlogon needs to wait it's turn .... at least a roaming profile can't load without Tcpip when it's talking with an SME server ..

[mdo]

Is there any reason that shouldn't be a standard recommended setting?

I believe it to be safe to make it a recommended setting (to use it everywhere). Many times it is NOT needed but we have never found out, under what circumstances it is actually needed - but it has solved problems for us quite a few times.