IP Configurations

[Jason Bridge]

Alright, here goes.
Background info:
1. Dell Lattitude Laptop w/ on-board 3Com NIC
2. Windows 2000 Professional
3. Two seperate Network Connection Locations
a. One is Office LAN w/ DHCP
b. The other is a remote connection from Home via A
redcreek ravlin that is pre-set with IP address to mimic a
connection as if I was in the office
c. The connection from home has a different grouping of
IP addresses pre-assigned and a different subnet.

Problem:
Pretending this connection to the network was a first, the
server would assign me an IP address, subnet, etc. after
communication is established with my NIC via the MAC
address. I then shutdown down, go home, and attempt to
connect via the ravlin device. End result, I can't connect.
I run IPCONFIG at command prompt, and it returns the IP
info as if I was still connected in the office. I execute,
IPCONFIG /RELEASE and IPCONFIG /RENEW and the exact same IP
info is obtained (exempt from that is that I do obtain a
new lease). The same problem occurs in reverse, i.e.
connect the first time at home, shut down, and then
reconnect in the office. The only way I have found to
circumvent this problem is to release IP cofig info, shut
the computer down, and then reboot connected to whichever
network I am working from.

From appearances, the IP info remains in cache somewhere so
when I do a release and renew, the cached info is
re-established. I wrote a little batch file to execute
everytime I shutdown before connecting to the other
network. Is this a bug in WIN2000 or is this normal.

Please help, as I am confused.

Thanks,

\Jason

 

[Michael Johnston [MSFT]]

Please refer to 167014 DHCP Client May Fail to Obtain a DHCP-Assigned IP Address http://support.microsoft.com/?id=167014. This may explain the
behavior you are experiencing.

Thank you,
Mike Johnston
Microsoft Network Support


--

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from which they originated.

 

[Jason Bridge]

Thanks for the info. However, after reading the article I
do see where this makes sense. Still one problem. The
article states to run a release and renew. I can NOT do
this. When I release and renew, I obtain the same IP info
even if I am connected to a different subnet. Therefore, It
appears to me that the IP info is in cache somewhere. The
only I can get a full release is to run a release, then reboot.

Thanks for your advice.

Jason

-----Original Message-----
Please refer to 167014 DHCP Client May Fail to Obtain a

DHCP-Assigned IP Address
http://support.microsoft.com/?id=167014. This may explain the

behavior you are experiencing.

Thank you,
Mike Johnston
Microsoft Network Support

confers no rights. Use of included script samples are
subject to the terms specified at

http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all

responses to this message are best directed to the
newsgroup/thread from which they originated.