This problem looks strange to me, but perhaps this is common Windows 7 behaviour... First, let me explain my network hardware setup: Usually I'm connecting to my LAN using a network cable or through WLAN. My ADSL router is a AVM Fritz!BOX machine. When I'm outside my office, I'm connecting to the Internet using my Windows 6.1 mobile phone, connected via USB or Bluetooth. Now here comes the strange part (the one which I don't understand): I have just connected to the Internet using my mobile phone. If I now open a Console window and enter IPCONFIG, this is the result: Windows-IP-Konfiguration Ethernet-Adapter USB_LAN -Verbindung: Verbindungsspezifisches DNS-Suffix: fritz.box Verbindungslokale IPv6-Adresse . : fe80::a1bb:a7e0:c9d1:3117%21 IPv4-Adresse . . . . . . . . . . : 192.168.0.103 Subnetzmaske . . . . . . . . . . : 255.255.255.0 Standardgateway . . . . . . . . . : 192.168.0.1 Ethernet-Adapter Bluetooth-Netzwerkverbindung: Medienstatus. . . . . . . . . . . : Medium getrennt Verbindungsspezifisches DNS-Suffix: Ethernet-Adapter LAN-Verbindung: Medienstatus. . . . . . . . . . . : Medium getrennt Verbindungsspezifisches DNS-Suffix: Drahtlos-LAN-Adapter Drahtlosnetzwerkverbindung: Medienstatus. . . . . . . . . . . : Medium getrennt Verbindungsspezifisches DNS-Suffix: fritz.box Ethernet-Adapter VMware Network Adapter VMnet1: Verbindungsspezifisches DNS-Suffix: Verbindungslokale IPv6-Adresse . : fe80::fc70:5bcb:9a81:998%25 IPv4-Adresse . . . . . . . . . . : 192.168.118.1 Subnetzmaske . . . . . . . . . . : 255.255.255.0 Standardgateway . . . . . . . . . : Ethernet-Adapter VMware Network Adapter VMnet8: Verbindungsspezifisches DNS-Suffix: Verbindungslokale IPv6-Adresse . : fe80::f03e:bb90:8f9f:a504%26 IPv4-Adresse . . . . . . . . . . : 192.168.113.1 Subnetzmaske . . . . . . . . . . : 255.255.255.0 Standardgateway . . . . . . . . . : Tunneladapter isatap.{0ABCC82A-A4E3-4017-9F32-CEF2EAB02DAB}: Medienstatus. . . . . . . . . . . : Medium getrennt Verbindungsspezifisches DNS-Suffix: Tunneladapter isatap.fritz.box: Medienstatus. . . . . . . . . . . : Medium getrennt Verbindungsspezifisches DNS-Suffix: Tunneladapter Teredo Tunneling Pseudo-Interface: Verbindungsspezifisches DNS-Suffix: IPv6-Adresse. . . . . . . . . . . : 2001:0:5ef5:79fd:bb:171f:3f57:ff99 Verbindungslokale IPv6-Adresse . : fe80::bb:171f:3f57:ff99%17 Standardgateway . . . . . . . . . : :: Tunneladapter isatap.{3C0A7E7A-8A55-494C-BE78-D3ADEE7B897D}: Medienstatus. . . . . . . . . . . : Medium getrennt Verbindungsspezifisches DNS-Suffix: Where's that "fritz.box" DNS suffix coming from? It belongs to the LAN connection, not to the USB_LAN connection. Your help is quite appreciated! Regards, Axel Dahmen

That DNS suffix is most likely coming being assigned from the DHCP server that assigned that IP address to your device. Visit: anITKB.com, an IT Knowledge Base.

Impossible... Unless Windows Mobile 6.1 would have a Fritz DHCP implementation ;)

Where is the 192.168.0.103 IP address coming from? Is this a static IP, or Alternate Configuration? Have you run the command IPCONFIG /all to verify this configuration is not coming from a DHCP server? Visit: anITKB.com, an IT Knowledge Base.

Don't nail me down on this but it must be the Windows Mobile phone. I've just connected my laptop to the mobile phone again, run IPCONFIG /ALL on it an this is the result (just showing the first network adapter settings): Windows-IP-Konfiguration Hostname . . . . . . . . . . . . : Loptap Primäres DNS-Suffix . . . . . . . : Knotentyp . . . . . . . . . . . . : Gemischt IP-Routing aktiviert . . . . . . : Nein WINS-Proxy aktiviert . . . . . . : Nein DNS-Suffixsuchliste . . . . . . . : fritz.box Ethernet-Adapter USB_LAN-Verbindung: Verbindungsspezifisches DNS-Suffix: fritz.box Beschreibung. . . . . . . . . . . : Remote NDIS based Internet Sharing Device Physikalische Adresse . . . . . . : 80-00-62-FD-A3-00 DHCP aktiviert. . . . . . . . . . : Ja Autokonfiguration aktiviert . . . : Ja Verbindungslokale IPv6-Adresse . : fe80::a1bb:a7e0:c9de:1471%21(Bevorzugt) IPv4-Adresse . . . . . . . . . . : 192.168.0.103(Bevorzugt) Subnetzmaske . . . . . . . . . . : 255.255.255.0 Lease erhalten. . . . . . . . . . : Mittwoch, 29. September 2010 15:18:28 Lease läuft ab. . . . . . . . . . : Samstag, 2. Oktober 2010 15:18:28 Standardgateway . . . . . . . . . : 192.168.0.1 DHCP-Server . . . . . . . . . . . : 192.168.0.1 DHCPv6-IAID . . . . . . . . . . . : 578742044 DHCPv6-Client-DUID. . . . . . . . : 00-01-00-01-13-99-EC-5F-00-52-C5-7A-28-52 My home network uses a differen sub net. The third octet is not null there.

I assume that the output shown above is German and that "DHCP aktiviert: Ja" means "DHCP Enabled: Yes" by comparing the output with that of an English version. The client (shown above) is pulling a DHCP lease from 192.168.0.1. You can see the leave time information as well. Where that DHCP server service is actually located, you will not be able to determine that from the IPCONFIG /all. In any network situation, the next step would be to start up a network capture so that you can get the source MAC information and follow the bread crumbs...until you reach the source. If you say that this is normally the configuration that you receive while connected via the LAN, but it does not clear when connected to the phone, I have not seen this in the past. Based on the lease information, it leads me to think that this is not a "sticky" configuration that is left behind. You clearly can see that the lease is brand new. Again, a network capture would be my next step in locating the source. Visit: anITKB.com, an IT Knowledge Base.