Static IP does not "stick" on TCP/IP Properties

This is by far the weirdest thing I've seen.

I have a Windows 2000 server setup as file server and domain controller.
All PCs seem to communicate fine with each other as well as with the server.

However, what drives me nuts is that no matter how many times I have
assigned the server a static IP address through the "Internet Protocol
(TCP/IP) Properties" window, every time I go back to check, it tell me that
it's set to obtain an IP address automatically.

Even weirder is the fact that through ipconfig on the command prompt, I can
see that the static IP address I gave it (192.168.0.50), is indeed assigned
to the server and in use. I can even see that the server (according to
ipconfig) is NOT setup to obtain an IP address automatically. But for some
reason the TCP/IP Properties screen doesn't seem to know that.

Any ideas??

i would check to make sure you have the latest driver for the nic. and maybe
run the command: "netsh int ip reset c:\resetlog.txt" and examine the log
for anything that might have been removed or added to the registry.


"Jose" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> This is by far the weirdest thing I've seen.
>
> I have a Windows 2000 server setup as file server and domain controller.
> All PCs seem to communicate fine with each other as well as with the
server.
>
> However, what drives me nuts is that no matter how many times I have
> assigned the server a static IP address through the "Internet Protocol
> (TCP/IP) Properties" window, every time I go back to check, it tell me
that
> it's set to obtain an IP address automatically.
>
> Even weirder is the fact that through ipconfig on the command prompt, I
can
> see that the static IP address I gave it (192.168.0.50), is indeed
assigned
> to the server and in use. I can even see that the server (according to
> ipconfig) is NOT setup to obtain an IP address automatically. But for
some
> reason the TCP/IP Properties screen doesn't seem to know that.
>
> Any ideas??
>
>
>
>

I tried to run that just for "kicks" to see what I'd get. It would not run
it as a command line like that, so I did it a piece at a time:
C:\> netsh
netsh> interface
interface>
interface> ip
interface ip>

Then I hit "?" and "Reset" was not an option. Do only certain "Netsh"
versions have it?


--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


<(E-Mail Removed)> wrote in message
news:sbjbc.25495$(E-Mail Removed) et...
> i would check to make sure you have the latest driver for the nic. and
maybe
> run the command: "netsh int ip reset c:\resetlog.txt" and examine the log
> for anything that might have been removed or added to the registry.
>
>
> "Jose" <(E-Mail Removed)> wrote in message
> news:%(E-Mail Removed)...
> > This is by far the weirdest thing I've seen.
> >
> > I have a Windows 2000 server setup as file server and domain controller.
> > All PCs seem to communicate fine with each other as well as with the
> server.
> >
> > However, what drives me nuts is that no matter how many times I have
> > assigned the server a static IP address through the "Internet Protocol
> > (TCP/IP) Properties" window, every time I go back to check, it tell me
> that
> > it's set to obtain an IP address automatically.
> >
> > Even weirder is the fact that through ipconfig on the command prompt, I
> can
> > see that the static IP address I gave it (192.168.0.50), is indeed
> assigned
> > to the server and in use. I can even see that the server (according to
> > ipconfig) is NOT setup to obtain an IP address automatically. But for
> some
> > reason the TCP/IP Properties screen doesn't seem to know that.
> >
> > Any ideas??
> >
> >
> >
> >
>
>

odd. im using XP pro sp1a and its there.



"Phillip Windell" <@.> wrote in message
news:(E-Mail Removed)...
> I tried to run that just for "kicks" to see what I'd get. It would not run
> it as a command line like that, so I did it a piece at a time:
> C:\> netsh
> netsh> interface
> interface>
> interface> ip
> interface ip>
>
> Then I hit "?" and "Reset" was not an option. Do only certain "Netsh"
> versions have it?
>
>
> --
>
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
>
>
> <(E-Mail Removed)> wrote in message
> news:sbjbc.25495$(E-Mail Removed) et...
> > i would check to make sure you have the latest driver for the nic. and
> maybe
> > run the command: "netsh int ip reset c:\resetlog.txt" and examine the
log
> > for anything that might have been removed or added to the registry.
> >
> >
> > "Jose" <(E-Mail Removed)> wrote in message
> > news:%(E-Mail Removed)...
> > > This is by far the weirdest thing I've seen.
> > >
> > > I have a Windows 2000 server setup as file server and domain
controller.
> > > All PCs seem to communicate fine with each other as well as with the
> > server.
> > >
> > > However, what drives me nuts is that no matter how many times I have
> > > assigned the server a static IP address through the "Internet Protocol
> > > (TCP/IP) Properties" window, every time I go back to check, it tell me
> > that
> > > it's set to obtain an IP address automatically.
> > >
> > > Even weirder is the fact that through ipconfig on the command prompt,
I
> > can
> > > see that the static IP address I gave it (192.168.0.50), is indeed
> > assigned
> > > to the server and in use. I can even see that the server (according
to
> > > ipconfig) is NOT setup to obtain an IP address automatically. But for
> > some
> > > reason the TCP/IP Properties screen doesn't seem to know that.
> > >
> > > Any ideas??
> > >
> > >
> > >
> > >
> >
> >
>
>

The reset is actually only a function on Windows XP and 2003.

Here is an article that lists issues with Network properties -
http://support.microsoft.com/default...B;EN-US;825826. (This
written for XP and Win2003, but should work for 2K)

The last section discusses deleting a registry value under
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Network . This may work
to resolve your issue. As with anything configuration change, make sure you
have a good backup.

-Matt
--
[This posting is provided AS IS
with no warranties, and confers
no rights.]


<(E-Mail Removed)> wrote in message
news:SRjbc.25891$(E-Mail Removed) et...
> odd. im using XP pro sp1a and its there.
>
>
>
> "Phillip Windell" <@.> wrote in message
> news:(E-Mail Removed)...
> > I tried to run that just for "kicks" to see what I'd get. It would not
run
> > it as a command line like that, so I did it a piece at a time:
> > C:\> netsh
> > netsh> interface
> > interface>
> > interface> ip
> > interface ip>
> >
> > Then I hit "?" and "Reset" was not an option. Do only certain "Netsh"
> > versions have it?
> >
> >
> > --
> >
> > Phillip Windell [MCP, MVP, CCNA]
> > www.wandtv.com
> >
> >
> > <(E-Mail Removed)> wrote in message
> > news:sbjbc.25495$(E-Mail Removed) et...
> > > i would check to make sure you have the latest driver for the nic. and
> > maybe
> > > run the command: "netsh int ip reset c:\resetlog.txt" and examine the
> log
> > > for anything that might have been removed or added to the registry.
> > >
> > >
> > > "Jose" <(E-Mail Removed)> wrote in message
> > > news:%(E-Mail Removed)...
> > > > This is by far the weirdest thing I've seen.
> > > >
> > > > I have a Windows 2000 server setup as file server and domain
> controller.
> > > > All PCs seem to communicate fine with each other as well as with the
> > > server.
> > > >
> > > > However, what drives me nuts is that no matter how many times I have
> > > > assigned the server a static IP address through the "Internet
Protocol
> > > > (TCP/IP) Properties" window, every time I go back to check, it tell
me
> > > that
> > > > it's set to obtain an IP address automatically.
> > > >
> > > > Even weirder is the fact that through ipconfig on the command
prompt,
> I
> > > can
> > > > see that the static IP address I gave it (192.168.0.50), is indeed
> > > assigned
> > > > to the server and in use. I can even see that the server (according
> to
> > > > ipconfig) is NOT setup to obtain an IP address automatically. But
for
> > > some
> > > > reason the TCP/IP Properties screen doesn't seem to know that.
> > > >
> > > > Any ideas??
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>

Ok,..yea I was running it on 2000.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

"Matthew [MSFT]" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> The reset is actually only a function on Windows XP and 2003.
>
> Here is an article that lists issues with Network properties -
> http://support.microsoft.com/default...B;EN-US;825826. (This
> written for XP and Win2003, but should work for 2K)
>
> The last section discusses deleting a registry value under
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Network . This may
work
> to resolve your issue. As with anything configuration change, make sure
you
> have a good backup.
>
> -Matt
> --
> [This posting is provided AS IS
> with no warranties, and confers
> no rights.]
>
>
> <(E-Mail Removed)> wrote in message
> news:SRjbc.25891$(E-Mail Removed) et...
> > odd. im using XP pro sp1a and its there.
> >
> >
> >
> > "Phillip Windell" <@.> wrote in message
> > news:(E-Mail Removed)...
> > > I tried to run that just for "kicks" to see what I'd get. It would not
> run
> > > it as a command line like that, so I did it a piece at a time:
> > > C:\> netsh
> > > netsh> interface
> > > interface>
> > > interface> ip
> > > interface ip>
> > >
> > > Then I hit "?" and "Reset" was not an option. Do only certain "Netsh"
> > > versions have it?
> > >
> > >
> > > --
> > >
> > > Phillip Windell [MCP, MVP, CCNA]
> > > www.wandtv.com
> > >
> > >
> > > <(E-Mail Removed)> wrote in message
> > > news:sbjbc.25495$(E-Mail Removed) et...
> > > > i would check to make sure you have the latest driver for the nic.
and
> > > maybe
> > > > run the command: "netsh int ip reset c:\resetlog.txt" and examine
the
> > log
> > > > for anything that might have been removed or added to the registry.
> > > >
> > > >
> > > > "Jose" <(E-Mail Removed)> wrote in message
> > > > news:%(E-Mail Removed)...
> > > > > This is by far the weirdest thing I've seen.
> > > > >
> > > > > I have a Windows 2000 server setup as file server and domain
> > controller.
> > > > > All PCs seem to communicate fine with each other as well as with
the
> > > > server.
> > > > >
> > > > > However, what drives me nuts is that no matter how many times I
have
> > > > > assigned the server a static IP address through the "Internet
> Protocol
> > > > > (TCP/IP) Properties" window, every time I go back to check, it
tell
> me
> > > > that
> > > > > it's set to obtain an IP address automatically.
> > > > >
> > > > > Even weirder is the fact that through ipconfig on the command
> prompt,
> > I
> > > > can
> > > > > see that the static IP address I gave it (192.168.0.50), is indeed
> > > > assigned
> > > > > to the server and in use. I can even see that the server
(according
> > to
> > > > > ipconfig) is NOT setup to obtain an IP address automatically. But
> for
> > > > some
> > > > > reason the TCP/IP Properties screen doesn't seem to know that.
> > > > >
> > > > > Any ideas??
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>