TCP/IP settings can not be saved

  • Thread starter Thread starter Paul
  • Start date Start date
P

Paul

Hi,

I installed a 2nd NIC into my W2Ksp3 server. After booting the server the
2nd NIC had a h/w address conflict with the 1st NIC. After resolving the
conflict I find I can no longer save IP settings. However ipconfig /all at
the DOS prompt shows that the adapters do have IP settings and can be pinged
from other hosts, but workstations are unable to login (i.e. windows
networking has been affected). Each time I open the TCP/IP settings for each
adapter and change from Automatic to manual and enter the IP address
settings, the settings are lost each time I reopen the dialog box.

I have tried pulling the NICs out, uninstall their drivers and redo
everything again but to no avail. It seems that the h/w address conflict
corrupted something.

Does anyone have any ideas?

Thanks a bunch.
 
SP3??? Your server should be at SP4. Have you at least got the ms03-039
patch installed? Are you using the 2nd nic to connect to a router for
internet?
 
The 2nd NIC is intended for a router. Will sp4 solve this issue?

Tks


Marina Roos [SBS-MVP] wrote in message ...
SP3??? Your server should be at SP4. Have you at least got the ms03-039
patch installed? Are you using the 2nd nic to connect to a router for
internet?

--
Regards,

Marina
[SBS-MVP]


Paul said:
Hi,
Click to expand...
Click to expand...
 
You'll need SP4 anyway. Make sure the external nic is in a different
IP-range. If you hadn't the ms03-039 installed yet, you might be blasted
which causes the errors you have.

--
Regards,

Marina
[SBS-MVP]


Paul said:
The 2nd NIC is intended for a router. Will sp4 solve this issue?

Tks


Marina Roos [SBS-MVP] wrote in message ...
SP3??? Your server should be at SP4. Have you at least got the ms03-039
patch installed? Are you using the 2nd nic to connect to a router for
internet?

--
Regards,

Marina
[SBS-MVP]


Paul said:
Hi,
Click to expand...
Click to expand...
Click to expand...
 
Hi,

ms03-039 is interesting but I doubt if it will solve the predicament I am
in. If anyone else can contribute other ideas I would appreciate your help.

Thanks,


Marina Roos [SBS-MVP] wrote in message ...
You'll need SP4 anyway. Make sure the external nic is in a different
IP-range. If you hadn't the ms03-039 installed yet, you might be blasted
which causes the errors you have.

--
Regards,

Marina
[SBS-MVP]


Paul said:
The 2nd NIC is intended for a router. Will sp4 solve this issue?

Tks


Marina Roos [SBS-MVP] wrote in message ...
SP3??? Your server should be at SP4. Have you at least got the ms03-039
patch installed? Are you using the 2nd nic to connect to a router for
internet?

--
Regards,

Marina
[SBS-MVP]


"Paul" <[email protected]> schreef in bericht
Hi,
Click to expand...
Click to expand...
Click to expand...
 
Check it!

--
Regards,

Marina
[SBS-MVP]


Paul said:
Hi,

ms03-039 is interesting but I doubt if it will solve the predicament I am
in. If anyone else can contribute other ideas I would appreciate your help.

Thanks,


Marina Roos [SBS-MVP] wrote in message ...
You'll need SP4 anyway. Make sure the external nic is in a different
IP-range. If you hadn't the ms03-039 installed yet, you might be blasted
which causes the errors you have.

--
Regards,

Marina
[SBS-MVP]


Paul said:
The 2nd NIC is intended for a router. Will sp4 solve this issue?

Tks


Marina Roos [SBS-MVP] wrote in message ...
SP3??? Your server should be at SP4. Have you at least got the ms03-039
patch installed? Are you using the 2nd nic to connect to a router for
internet?

--
Regards,

Marina
[SBS-MVP]


"Paul" <[email protected]> schreef in bericht
Hi,
Click to expand...
Click to expand...
Click to expand...
 
I've seen this happen before - I've generally booted into safe mode and
removed all references to that network config in HKLM \ ....current control
set, controlset001, 002, etc.... then rebooted, re-added the network card,
and the problem has gone away.

Thankfully, I've only ever seen it happen on my own server (W2k SP4, with
ms03-039 definitely applied as well as all other critical patches). This
server has of course taken a lot more abuse than my clients' have, due to my
"playing" with it. If anyone has a better answer, I'd love to hear it!
 
Can you remember which registry entries you deleted

Tks.

----- Lanwench [MVP - Exchange] wrote: ----

I've seen this happen before - I've generally booted into safe mode an
removed all references to that network config in HKLM \ ....current contro
set, controlset001, 002, etc.... then rebooted, re-added the network card
and the problem has gone away

Thankfully, I've only ever seen it happen on my own server (W2k SP4, wit
ms03-039 definitely applied as well as all other critical patches). Thi
server has of course taken a lot more abuse than my clients' have, due to m
"playing" with it. If anyone has a better answer, I'd love to hear it

Paul wrote
 
Hmmm - well, it was late at night, but ...

HKLM | System | Controlset* and CurrentControlSet ...Network.
Found the references to the NIC I was having problems with and deleted
everything. When I booted back up normally, I just added in the hardware
again, and it worked.

I did not enjoy the procedure.

Paul said:
Can you remember which registry entries you deleted?

Tks.

----- Lanwench [MVP - Exchange] wrote: -----

I've seen this happen before - I've generally booted into safe mode and
removed all references to that network config in HKLM \ ....current control
set, controlset001, 002, etc.... then rebooted, re-added the network card,
and the problem has gone away.

Thankfully, I've only ever seen it happen on my own server (W2k SP4, with
ms03-039 definitely applied as well as all other critical patches). This
server has of course taken a lot more abuse than my clients' have, due to my
"playing" with it. If anyone has a better answer, I'd love to hear it!
server
the 2nd NIC had a h/w address conflict with the 1st NIC. After
resolving the conflict I find I can no longer save IP settings.
However ipconfig /all at the DOS prompt shows that the adapters do
have IP settings and can be pinged from other hosts, but workstations
are unable to login (i.e. windows networking has been affected). Each
time I open the TCP/IP settings for each adapter and change from
Automatic to manual and enter the IP address settings, the settings
are lost each time I reopen the dialog box. redo
everything again but to no avail. It seems that the h/w address
conflict corrupted something.
Click to expand...
Click to expand...
 
Thanks, I'll give it a try.

Paul


Lanwench [MVP - Exchange] wrote in message ...
Hmmm - well, it was late at night, but ...

HKLM | System | Controlset* and CurrentControlSet ...Network.
Found the references to the NIC I was having problems with and deleted
everything. When I booted back up normally, I just added in the hardware
again, and it worked.

I did not enjoy the procedure.

Paul said:
Can you remember which registry entries you deleted?

Tks.

----- Lanwench [MVP - Exchange] wrote: -----

I've seen this happen before - I've generally booted into safe mode and
removed all references to that network config in HKLM \ ....current control
set, controlset001, 002, etc.... then rebooted, re-added the
Click to expand...
network
card,
and the problem has gone away.

Thankfully, I've only ever seen it happen on my own server (W2k SP4, with
ms03-039 definitely applied as well as all other critical patches). This
server has of course taken a lot more abuse than my clients' have, due to my
"playing" with it. If anyone has a better answer, I'd love to hear it!
Click to expand...
Click to expand...
 
Back
Top