Laptop as domain member prompts for reboot after trying to change

[Guest]

Here's the problem as best I can describe...

Background:
Fresh XP Pro with SP2 install on Gateway 400 series laptop
Latest drivers for all components
Requirement to change IP config frequently
Logged on with either local admin or domain admin

BEFORE joing system to domain (right after fresh install) I was able to
change IP information without requiring a reboot. Since joining our company's
domain, I am no longer able to change IP without rebooting. I've checked our
domain policies and find nothing enabled that would prevent me from IP
changes. The other VERY STRANGE thing about all this is that after the change
and reboot the network device properties show a different IP config than
doing an ipconfig. It just shows the original config as if it never changed;
even after the reboot. It's as if I'm no longer a local admin.

The problem remains after removing computer from the domain.

So, what kinds of things should I be looking at? What kind of group policy
settings would prevent IP changes?

Thanks for any help offered.

 

[Lanwench [MVP - Exchange]]

Here's the problem as best I can describe...

Background:
Fresh XP Pro with SP2 install on Gateway 400 series laptop
Latest drivers for all components
Requirement to change IP config frequently

Why? Do you not connect to networks with DHCP servers on 'em?

Logged on with either local admin or domain admin

BEFORE joing system to domain (right after fresh install) I was able
to change IP information without requiring a reboot. Since joining
our company's domain, I am no longer able to change IP without
rebooting.

What errors do you get?
Since I'm presuming you're talking about static IPs (yuck), if you go into
the TCP/IP properties,change the IP to what you need, apply/close, and run
ipconfig /all from the command prompt, what do you see?
If you right-click on the Local Area Connection & choose repair, does it
help?
Event log errors?

I've checked our domain policies and find nothing enabled
that would prevent me from IP changes. The other VERY STRANGE thing
about all this is that after the change and reboot the network device
properties show a different IP config than doing an ipconfig. It just
shows the original config as if it never changed; even after the
reboot. It's as if I'm no longer a local admin.

The problem remains after removing computer from the domain.

So, what kinds of things should I be looking at? What kind of group
policy settings would prevent IP changes?

None that I know of - but running rsop.msc from start | run might help you
look.

 

[Guest]

Thanks for the help. I solved the problem but feel like such a dolt. We are
testing McAfee VSE 8.5i and the laptop has that installed. There is a new
"feature" in that which allows you to "protect network settings". I disabled
that and all is back to normal.

Hope this helps someone else with similar problems.

Why? Do you not connect to networks with DHCP servers on 'em?

Yup. I agree; static IPs suck. We're stuck with that due to our mainframe
setup. Thanks again.

 

[Lanwench [MVP - Exchange]]

Thanks for the help. I solved the problem but feel like such a dolt.
We are testing McAfee VSE 8.5i and the laptop has that installed.
There is a new "feature" in that which allows you to "protect network
settings". I disabled that and all is back to normal.

Hope this helps someone else with similar problems.

Ah, glad you found it. Still doesn't explain why you aren't using DHCP,
tho. ;-)

 

[Lanwench [MVP - Exchange]]

Lanwench [MVP - Exchange]

Ah, glad you found it. Still doesn't explain why you aren't using
DHCP, tho. ;-)

Whoops - sorry, didn't scroll down & see your last line. It doesn't really
explain why you can't stick a DHCP server on the network, unless you need
computerX to always have a specific IP address - you could use reservations,
you know.