Networking "self-destructs" after joining Windows 2003 Domain

[Guest]

I realize that this has been posted before, but no solution seems to be
found. This is a HUGE problem and will abosolutely prevent any rollout of
Vista in my organization if there is no solution to this problem. Basically,
the problem is this:

- New Vista setup (new install or upgrade using RC1) works fine until joined
to the Win2K3 domain.
- After joining the Win2K3 domain, Vista still OK after the first reboot,
but after a subsequent shutdown/restart, the following happens:
* DHCP Client service shuts down with a 1004 Access is denied error.
* No IP address is leased from the DHCP server (since no DHCP Client
service)
* Machine is logged in with cached login information but no attempts to
correct the network failures are successful.

So far I have found no solution to this problem other than reinstall the O/S
and all applications. I have tried saving a Restore point before joining the
doimain and that is not sufficient for restoring the system to a working
state.

Additional information:

- In addition to the DHCP Client not starting, the following "automatic"
startup services are failing as well:

* Base Filtering Engine
* Diagnostic Policy Service
* IKE and AuthIP IPsec Keying Modules
* IPsec Policy Agent
* Network List Service
* Network Location Awareness
* Thread Ordering Server
* Windows Audio
* Windows Firewall
* Windows Time
* Windows Media Center Service Launcher

All of these services are set to Log On as "Local Service" except IPsec
Policy Agent and Network Location Awareness - these are set to Network
Service. Incidentally, there are about a dozen services which use the Local
Service account that are starting correctly so I'm not sure what the problem
is.

Please Help.

 

[Guest]

I am having the same symptoms.
Did you get any responses or solutions?

 

[Ben Derr]

Any domain based GPOs that touch these services?

 

[Guest]

I have the exact same problem you described below. After searching endlessly
I'm desparte for an answer.

 

[Guest]

The policies are removed, but there is noo change. I even removed policies
securing files and registry.
I also reinstalled the machine - still, after the domain join the DHCP
client and the Diagnostic Service fail to launch. Other services using the
same user are running, so it doesnt seem to be a user related problem. Only
"access denied".

Are there any debugging possibilities?? Any logging?

 

[Guest]

This
(http://blogs.technet.com/asiasupp/a...ying-vista-client-in-windows-2000-domain.aspx) could be a solution.

My Domain was upgraded from 2000, maybe something got stuck..

 

[Guest]

The Privilege is not my problem.

I've tried using ProcMon to see if anything gets denied but again - nothing!

I'm at the end of the line

 

[joespr]

I have the same problem. And I've seen various posts about this but no solution.

I (and I am sure many others) are giving up on Vista at least until it can work.

Typical M$Soft attitude: crap on the users.

EggHeadCafe.com - .NET Developer Portal of Choice
http://www.eggheadcafe.com

 

[ShaneMD1]

I realize it's not an ideal solution, but to get started you can add
the Everyone group with full control to HKLM\System\CurrentControlSet
\Services. This will get you the ability to create registry subkeys.
Procmon pointed out that the reason the services were failing with
Access Denied is because of missing permissions to create registry
subkeys, specifically in services like the Base Filtering Engine. At
this point I'm not sure what user/group lost its permissions to do
this, but it was after joining a domain.

My only hangup at the moment is the Diagnostic Policy Service. I
still get access denied on that service, but using the above I was
able to start the BFE and the Windows Firewall. I hope this at least
helps someone along enough to provide feedback or a solution to
further services down the line.

 

[Mick Murphy]

Vista Home Premium won't join a Domain.

 

[Steve]

I'm having the same issue. I was troubleshooting my inability to use Vista's
offline file feature. I have four Vista users with very slow performance
both offline and on. I got past some of it by applying all the Vista patches
to the Exchange server, SBS and the Vista clients, but offline files simply
does not work.

So for troubelshooting, I built an SBS lab and now I have the issue you
describe...I joined the system to the domain using the Connect Computer site,
but during the connection attempt, it killed every network connection on the
network.

Further troubleshooting got a single successful offline file synchronization
but only by booting to diagnostic startup. Once that succeeded, I have been
unable to reproduce the success...all attempts at syncing fail now, and often
even the attempt will blow away other network connections.

Twice I've had to reboot my router to reestabilsh connectivity...and yes,
the router's firmware is up to date. It is a SonicWALL 2040 both at the lab
and the production site, and the production site to date has not shown the
network "self-destruction" symptom of the lab, but I'm certainly not going to
try to recreate it there.

I have a ticket open with Microsoft, and to date their alleged escalation
engineers cannot find a solution.

So again...in addition to the network blowing up when the Vista systems try
to join the domain and when GPO runs, I cannot get offline files working.

To make matters worse, these are Dell XPS laptops which cannot run XP
Pro...or believe me I would have stopped beating my head against this issue a
hundred hours ago and "upgraded" back to XP Pro.

Any help would be appreciated, thanks.