Network Connection Properties have disappeared

I'm in the process of moving all of my Windows XP workstations to a Windows
2003 domain environment, and I'm experiencing the same problem on all of them
after the workstation after joining the new domain.

Before the workstations are joined to the new domain, you can view the
Network Connection properties. You can see all of the network cards and can
edit their properties as well.

After the rebooting (from joining the new domain) the ability to view the
network cards, and the network settings for each of them, disappears through
Network Connections.

You can still see the network cards through the device manager, and they the
network cards still work. You just can't go in and edit any of the
properties. This occurs even when you are logged into the workstation with
full administrative privileges.

There are no global policies set, beyond the default policies that are
created by Windows 2003 Server. Is this by design through Windows 2003
Server? If so, how can I overide this?

Any suggestions?

Hi Harry.

Since it is happening to all computers it does sound like a Group Policy
setting. I would install the Group Policy Management Console on a W2003
domain controller to see if indeed any settings have been defined for any
GPO. Note that if a GPO is created with defined settings and then later that
GPO is deleted [without unlinking or disabling first] that it is possible
that the settings that GPO had defined did not "untake". If nothing obvious
is found it may help to create a new GPO and place it at the top of the list
for the domain container or OU container if the computers are in an OU and
define the settings that will hopeful undo this behavior. The settings you
refer to are under user configuration/administrative
templates/network/network connections. Define settings that would reverse
what is occurring. Also verify that you indeed are logged on as an
administrator by using the "net localgroup administrators" command and try
logging on as the local built in administrator account to see if that makes
a difference. The local administrator account would not be subject to domain
policy user configuration, so you may want to try that first as if it did
not apply to the local administrator it almost certainly is a domain/OU
policy. --- Steve


"Harry Theriot" <(E-Mail Removed)> wrote in message
news:F413D086-4691-4550-A907-(E-Mail Removed)...
> I'm in the process of moving all of my Windows XP workstations to a
> Windows
> 2003 domain environment, and I'm experiencing the same problem on all of
> them
> after the workstation after joining the new domain.
>
> Before the workstations are joined to the new domain, you can view the
> Network Connection properties. You can see all of the network cards and
> can
> edit their properties as well.
>
> After the rebooting (from joining the new domain) the ability to view the
> network cards, and the network settings for each of them, disappears
> through
> Network Connections.
>
> You can still see the network cards through the device manager, and they
> the
> network cards still work. You just can't go in and edit any of the
> properties. This occurs even when you are logged into the workstation
> with
> full administrative privileges.
>
> There are no global policies set, beyond the default policies that are
> created by Windows 2003 Server. Is this by design through Windows 2003
> Server? If so, how can I overide this?
>
> Any suggestions?

I've checked all of the current GPO's that are setup on our AD, and none of
them have anything relating to the Network Connections.

As suggested, I've even created a GPO to "Enable" what appears the correct
policies, and disable the "Prohibits" that seemed appropriate.
Still no changes on any of the Windows XP workstations. I still can't
change/edit the properties of the network connections.

I did notice on the all of the XP workstations, that there are entries in
the Application Event Log that are not normal. The source is Userenv with an
Event ID of 1090. It mentions that there are possible problems connecting to
the WMI.

Are there any configuration settings that need to be done to the WMI?

I'm not sure where to go from here.

Any suggestions?

"Steven L Umbach" wrote:

> Hi Harry.
>
> Since it is happening to all computers it does sound like a Group Policy
> setting. I would install the Group Policy Management Console on a W2003
> domain controller to see if indeed any settings have been defined for any
> GPO. Note that if a GPO is created with defined settings and then later that
> GPO is deleted [without unlinking or disabling first] that it is possible
> that the settings that GPO had defined did not "untake". If nothing obvious
> is found it may help to create a new GPO and place it at the top of the list
> for the domain container or OU container if the computers are in an OU and
> define the settings that will hopeful undo this behavior. The settings you
> refer to are under user configuration/administrative
> templates/network/network connections. Define settings that would reverse
> what is occurring. Also verify that you indeed are logged on as an
> administrator by using the "net localgroup administrators" command and try
> logging on as the local built in administrator account to see if that makes
> a difference. The local administrator account would not be subject to domain
> policy user configuration, so you may want to try that first as if it did
> not apply to the local administrator it almost certainly is a domain/OU
> policy. --- Steve
>
>
> "Harry Theriot" <(E-Mail Removed)> wrote in message
> news:F413D086-4691-4550-A907-(E-Mail Removed)...
> > I'm in the process of moving all of my Windows XP workstations to a
> > Windows
> > 2003 domain environment, and I'm experiencing the same problem on all of
> > them
> > after the workstation after joining the new domain.
> >
> > Before the workstations are joined to the new domain, you can view the
> > Network Connection properties. You can see all of the network cards and
> > can
> > edit their properties as well.
> >
> > After the rebooting (from joining the new domain) the ability to view the
> > network cards, and the network settings for each of them, disappears
> > through
> > Network Connections.
> >
> > You can still see the network cards through the device manager, and they
> > the
> > network cards still work. You just can't go in and edit any of the
> > properties. This occurs even when you are logged into the workstation
> > with
> > full administrative privileges.
> >
> > There are no global policies set, beyond the default policies that are
> > created by Windows 2003 Server. Is this by design through Windows 2003
> > Server? If so, how can I overide this?
> >
> > Any suggestions?
>
>
>

Hmm. That is strange. I can not think of anything else offhand. I would
definitely consider the 1090 errors could be related since they are
appearing on all your XP computers. The link below is about a 1090 error and
worth looking at but I am not familiar with any specific WMI settings that
need to be configured. I have never had a problem with such in a default
installation.

http://www.eventid.net/display.asp?e...serenv&phase=1

I don't know if this will help, but I would run the netdiag support tool on
the domain controllers [at lease a couple] and the XP workstations to see if
any related errors are reported. In particular dns misconfiguration can
cause a lot of problems. Review the link below to make sure your dns is
configured correctly. Also check that your XP workstations are current with
critical updates and try using Service Pack 2 on at least one XP computer if
you have not installed such yet. --- Steve

http://support.microsoft.com/default...en-us%3B291382

"Harry Theriot" <(E-Mail Removed)> wrote in message
news:B1CFF4E8-9740-4375-AF82-(E-Mail Removed)...
> I've checked all of the current GPO's that are setup on our AD, and none
> of
> them have anything relating to the Network Connections.
>
> As suggested, I've even created a GPO to "Enable" what appears the correct
> policies, and disable the "Prohibits" that seemed appropriate.
> Still no changes on any of the Windows XP workstations. I still can't
> change/edit the properties of the network connections.
>
> I did notice on the all of the XP workstations, that there are entries in
> the Application Event Log that are not normal. The source is Userenv with
> an
> Event ID of 1090. It mentions that there are possible problems connecting
> to
> the WMI.
>
> Are there any configuration settings that need to be done to the WMI?
>
> I'm not sure where to go from here.
>
> Any suggestions?
>
> "Steven L Umbach" wrote:
>
>> Hi Harry.
>>
>> Since it is happening to all computers it does sound like a Group Policy
>> setting. I would install the Group Policy Management Console on a W2003
>> domain controller to see if indeed any settings have been defined for any
>> GPO. Note that if a GPO is created with defined settings and then later
>> that
>> GPO is deleted [without unlinking or disabling first] that it is possible
>> that the settings that GPO had defined did not "untake". If nothing
>> obvious
>> is found it may help to create a new GPO and place it at the top of the
>> list
>> for the domain container or OU container if the computers are in an OU
>> and
>> define the settings that will hopeful undo this behavior. The settings
>> you
>> refer to are under user configuration/administrative
>> templates/network/network connections. Define settings that would reverse
>> what is occurring. Also verify that you indeed are logged on as an
>> administrator by using the "net localgroup administrators" command and
>> try
>> logging on as the local built in administrator account to see if that
>> makes
>> a difference. The local administrator account would not be subject to
>> domain
>> policy user configuration, so you may want to try that first as if it did
>> not apply to the local administrator it almost certainly is a domain/OU
>> policy. --- Steve
>>
>>
>> "Harry Theriot" <(E-Mail Removed)> wrote in message
>> news:F413D086-4691-4550-A907-(E-Mail Removed)...
>> > I'm in the process of moving all of my Windows XP workstations to a
>> > Windows
>> > 2003 domain environment, and I'm experiencing the same problem on all
>> > of
>> > them
>> > after the workstation after joining the new domain.
>> >
>> > Before the workstations are joined to the new domain, you can view the
>> > Network Connection properties. You can see all of the network cards
>> > and
>> > can
>> > edit their properties as well.
>> >
>> > After the rebooting (from joining the new domain) the ability to view
>> > the
>> > network cards, and the network settings for each of them, disappears
>> > through
>> > Network Connections.
>> >
>> > You can still see the network cards through the device manager, and
>> > they
>> > the
>> > network cards still work. You just can't go in and edit any of the
>> > properties. This occurs even when you are logged into the workstation
>> > with
>> > full administrative privileges.
>> >
>> > There are no global policies set, beyond the default policies that are
>> > created by Windows 2003 Server. Is this by design through Windows 2003
>> > Server? If so, how can I overide this?
>> >
>> > Any suggestions?
>>
>>
>>