Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[OT] Interesting Windows IP issue



I agree. While I am kind of the IT guy in the office, that is not my
job. If we need Windows expertise, there is an IT guy in New York.

On 01/22/2011 11:08 AM, ninurta2005 wrote:
> That is really odd. Usually, when a network card is unable to obtain a
> DHCP address, it defaults to a 169.xxx.xxx.xxx, which is Microsoft's
> default.
>
> I have seen similar behavior with DHCP at work, where the host has a
> IP address issued by DHCP, but it is conflicting with another node on
> the network with the same address. And the host refuses to release the
> address.
>
> One place to search is for the Assigned IP is under
> HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\..\Parameters\TCPIP.
> Hit F3 again. There is another Registry Entry storing it under the=20
> HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\TCPIP\Parameters\Inter=
faces\......
> Hit F3 again and repeat above.  You may be able to remove the key
> under Services where the IP address is stored and attempt to do a
> IPCONFIG/Release and Renew. Microsoft tends to store stuff under
> multiple locations.
>
> Good luck.
> Paul
>
>
>
> -----------------------------------------------------------------------=
-
> *From:* Jerry Feldman <gaf-mNDKBlG2WHs at public.gmane.org>
> *To:* Boston Linux and Unix <discuss-mNDKBlG2WHs at public.gmane.org>
> *Sent:* Sat, January 22, 2011 10:30:00 AM
> *Subject:* [OT] Interesting Windows IP issue
>
> Yesterday at work, one of my coworkers wanted to make a presentation
> from his company laptop (Windows XP). For some reason his IP address wa=
s
> showing 192.168.x.x, not the internal company 10. address. I used my
> Ubuntu netbook to make sure the CAT5E cable was ok, and I certainly got=

> a valid 10. address. We moved to another office because the lighting wa=
s
> better, and the same thing. We even rebooted his computer. Somehow it
> wanted to remain at 192.168. Our cables are plugged directly into a
> switch that plugs into our firewall. After a while we finally got the
> thing up and running on the corporate network. Note that I had even don=
e
> a IPCONFIG /release and IPCONFIG /renew. I've seen this before on his
> previous laptop. Apparently he does something at home, but when I look
> at properties it shows DHCP.
>
> --=20
> Jerry Feldman <gaf-mNDKBlG2WHs at public.gmane.org <mailto:gaf-mNDKBlG2WHs at public.gmane.org>>
> Boston Linux and Unix
> PGP key id: 537C5846
> PGP Key fingerprint: 3D1B 8377 A3C0 A5F2 ECBB  CA3B 4607 4319 537C 5846=

>
>
>


--=20
Jerry Feldman <gaf-mNDKBlG2WHs at public.gmane.org>
Boston Linux and Unix
PGP key id: 537C5846
PGP Key fingerprint: 3D1B 8377 A3C0 A5F2 ECBB  CA3B 4607 4319 537C 5846



_______________________________________________
Discuss mailing list
Discuss-mNDKBlG2WHs at public.gmane.org
http://lists.blu.org/mailman/listinfo/discuss






BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org