A Windows Vista forum. Vista Banter

Welcome to Vista Banter.

You are currently viewing our boards as a guest which gives you limited access to view most discussions, articles and access our other FREE features. By joining our free community you will have access to ask questions and reply to others posts, upload your own photos and access many other special features. Registration is fast, simple and absolutely free so please, join our community today!

If you have any problems with the registration process or your account login, please contact contact support.

Go Back   Home » Vista Banter forum » Microsoft Windows Vista » Networking with Windows Vista
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

Networking with Windows Vista Networking issues and questions with Windows Vista. (microsoft.public.windows.vista.networking_sharing)

Networking "self-destructs" after joining Windows 2003 Domain



 
 
LinkBack Thread Tools Display Modes
  #1 (permalink)  
Old October 16th 06, 06:09 PM posted to microsoft.public.windows.vista.networking_sharing
ZackMan18
external usenet poster
 
Posts: 2
Default Networking "self-destructs" after joining Windows 2003 Domain

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) 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.
  #2 (permalink)  
Old October 18th 06, 08:52 AM posted to microsoft.public.windows.vista.networking_sharing
Nick Payne
external usenet poster
 
Posts: 54
Default Networking "self-destructs" after joining Windows 2003 Domain

I upgraded a WinXP workstation that was already a domain member (2003 native
mode domain) to RC2 and have had no problems such as you describe. The
workstation was still a domain member after the upgrade and networking works
fine. Must have rebooted it six or eight times so far...

Haven't yet tried joining a fresh install to the domain.

Nick

"ZackMan18" wrote in message
...
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) 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.


 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT. The time now is 11:48 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.Search Engine Optimization by vBSEO 3.0.0 RC6
Copyright ©2004-2012 Vista Banter.
The comments are property of their posters.