1. Computer problem? Tech Support Guy is completely free -- paid for by advertisers and donations. Click here to join today! If you're new to Tech Support Guy, we highly recommend that you visit our Guide for New Members.

Solved: Incorrect IP4 Addr assigned to Wireless Atheros adapter by public hotspot

Discussion in 'Networking' started by TomNice, Jan 4, 2013.

Thread Status:
Not open for further replies.
Advertisement
  1. TomNice

    TomNice Thread Starter

    Joined:
    Jan 4, 2013
    Messages:
    5

    Hi,
    I’ve got a Toshiba Notebookwith Atheros AR9002WB-1NG wireless adapter. Generally it works fine, especiallywhen dhcp with various home based routers assign types of addresses /subnet masksin the range 192.xx with 255.255.255.0.in that case DNS and GWY settings are okand work.

    However, when trying toaccess a free hotspot, even when signal is strong, it wants to assign addressesin the range 78.xx , and then, totally incorrect IP4 Addresses (in the range10.xx with similar prefixes for Gwy and dns servers ) and no IP6 are assigned; obviouslythe gateway is wrong and no DNS resolution can take place. By default the advanced parameter AdHoc 11nis disabled, in that case it doesn’t even come up with the provider’s loginscreen. When I enable it, it does, but produces no further internetconnectivity, due to the above. I try to disable known automatic internet connectivity requests that come up prior to establishing a valid connection, but I doubt whether there's any relevance to my issue.
    What grabs me is that asecond notebook, Dell Latitude with an Intel Pro WL 3945ABG is workingflawlessly in the same location on the same desk with that free public hotspot.

    They differ in the set ofadvanced parameters (see below); I don’t know whether this has to do anythingwith my problem. If it does, the Atheros driver version is 9.2.0.206, thesystem says it needs no update because the “optimal version is alreadyinstalled”, however their website has 10.0.0.52 versions for 64-bit machines,but I cannot force it to install after downloading and unzipping it.
    802.11b preable is set to long and short
    AdHoc 11n
    Network Address unavailable
    Receive and Tx buffers (I toggle between 256 and 512, no effect)
    Roaming policy (I increased to highest value)
    Scan Valid Interval 60

    WhereasIntels set specifies Wireless mode 6.802.11a/b/g
    AdHoc default 0.802.11b/g
    and CTS-to-self active.

    Anysuggestion to help me resolve this issue? Thx a lot in advance, Thomas,Nice, France.
     
  2. Couriant

    Couriant Trusted Advisor

    Joined:
    Mar 26, 2002
    Messages:
    33,063
    First Name:
    James
    The IP address range for 78.x.y.z is a public IP address, as in it came from the internet provider directly. That IP address should have allowed you to connect to the internet, unless there is some kind of security on that hotspot.

    Can you provide the full IP information by posting your IPCONFIG/ALL when you are connected to the wireless connection.
     
  3. TomNice

    TomNice Thread Starter

    Joined:
    Jan 4, 2013
    Messages:
    5
    Hi, thx, ok I'm patient. The public 'free' hotspot allocates the public IP address, but will route any http request to its login screen and won't grant full internet connectivity unless you provide valid ID /PW. Until than the symbol in the taskbar keeps ofcourse the yellow exclamation point. During that state I could see something of 802.11n, and probably nothing about IPV6. Now I'm logged in (with the Dell Laptop / Intel Adapter, which is the device that works). Here's the result of the config: While you look at it, I'm trying to extract some information from the other laptop, which fails, and to post it to you in some way, maybe by a USB memory stick.
    Windows-IP-Konfiguration
    Hostname . . . . . . . . . . . . : NB-MP153-W7
    Primäres DNS-Suffix . . . . . . . : bdi.local
    Knotentyp . . . . . . . . . . . . : Gemischt
    IP-Routing aktiviert . . . . . . : Nein
    WINS-Proxy aktiviert . . . . . . : Nein
    DNS-Suffixsuchliste . . . . . . . : bdi.local
    Ethernet-Adapter Bluetooth-Netzwerkverbindung:
    Medienstatus. . . . . . . . . . . : Medium getrennt
    Verbindungsspezifisches DNS-Suffix:
    Beschreibung. . . . . . . . . . . : Bluetooth-Gerät (PAN)
    Physikalische Adresse . . . . . . : 00-1A-6B-32-20-60
    DHCP aktiviert. . . . . . . . . . : Ja
    Autokonfiguration aktiviert . . . : Ja
    Drahtlos-LAN-Adapter Drahtlosnetzwerkverbindung:
    Verbindungsspezifisches DNS-Suffix:
    Beschreibung. . . . . . . . . . . : Intel(R) PRO/Wireless 3945ABG Network
    nection
    Physikalische Adresse . . . . . . : 00-1B-77-19-50-19
    DHCP aktiviert. . . . . . . . . . : Ja
    Autokonfiguration aktiviert . . . : Ja
    Verbindungslokale IPv6-Adresse . : fe80::6da1:7365:b0ad:c7f0%12(Bevorzug
    IPv4-Adresse . . . . . . . . . . : 78.251.79.163(Bevorzugt)
    Subnetzmaske . . . . . . . . . . : 255.255.128.0
    Lease erhalten. . . . . . . . . . : Freitag, 04. Jänner 2013 22:07:32
    Lease läuft ab. . . . . . . . . . : Freitag, 04. Jänner 2013 22:37:10
    Standardgateway . . . . . . . . . : 78.251.127.254
    DHCP-Server . . . . . . . . . . . : 78.251.127.254
    DHCPv6-IAID . . . . . . . . . . . : 201333623
    DHCPv6-Client-DUID. . . . . . . . : 00-01-00-01-18-33-BB-85-00-18-8B-CD-9
    DNS-Server . . . . . . . . . . . : 212.27.40.240
    212.27.40.241
    NetBIOS über TCP/IP . . . . . . . : Aktiviert
    Ethernet-Adapter LAN-Verbindung:
    Medienstatus. . . . . . . . . . . : Medium getrennt
    Verbindungsspezifisches DNS-Suffix:
    Beschreibung. . . . . . . . . . . : Broadcom NetXtreme 57xx Gigabit Contr
    r
    Physikalische Adresse . . . . . . : 00-18-8B-CD-9F-89
    DHCP aktiviert. . . . . . . . . . : Nein
    Autokonfiguration aktiviert . . . : Ja
    Tunneladapter isatap.{B45E56C3-5F1D-4560-8C20-58B285ADF6EB}:
    Medienstatus. . . . . . . . . . . : Medium getrennt
    Verbindungsspezifisches DNS-Suffix:
    Beschreibung. . . . . . . . . . . : Microsoft-ISATAP-Adapter
    Physikalische Adresse . . . . . . : 00-00-00-00-00-00-00-E0
    DHCP aktiviert. . . . . . . . . . : Nein
    Autokonfiguration aktiviert . . . : Ja
    Tunneladapter isatap.{75D1DAFA-A36C-4372-8A58-295CC5DB8CC7}:
    Medienstatus. . . . . . . . . . . : Medium getrennt
    Verbindungsspezifisches DNS-Suffix:
    Beschreibung. . . . . . . . . . . : Microsoft-ISATAP-Adapter #2
    Physikalische Adresse . . . . . . : 00-00-00-00-00-00-00-E0
    DHCP aktiviert. . . . . . . . . . : Nein
    Autokonfiguration aktiviert . . . : Ja
    Tunneladapter isatap.{5FB56AD5-E110-4613-860C-7AFE58365C62}:
    Medienstatus. . . . . . . . . . . : Medium getrennt
    Verbindungsspezifisches DNS-Suffix:
    Beschreibung. . . . . . . . . . . : Microsoft-ISATAP-Adapter #3
    Physikalische Adresse . . . . . . : 00-00-00-00-00-00-00-E0
    DHCP aktiviert. . . . . . . . . . : Nein
    Autokonfiguration aktiviert . . . : Ja
    Tunneladapter Teredo Tunneling Pseudo-Interface:
    Verbindungsspezifisches DNS-Suffix:
    Beschreibung. . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
    Physikalische Adresse . . . . . . : 00-00-00-00-00-00-00-E0
    DHCP aktiviert. . . . . . . . . . : Nein
    Autokonfiguration aktiviert . . . : Ja
    IPv6-Adresse. . . . . . . . . . . : 2001:0:5ef5:79fb:3cd3:6d:b104:b05c(Be
    ugt)
    Verbindungslokale IPv6-Adresse . : fe80::3cd3:6d:b104:b05c%17(Bevorzugt)
    Standardgateway . . . . . . . . . :
    NetBIOS über TCP/IP . . . . . . . : Deaktiviert
    Tunneladapter 6TO4 Adapter:
    Verbindungsspezifisches DNS-Suffix:
    Beschreibung. . . . . . . . . . . : Microsoft-6zu4-Adapter
    Physikalische Adresse . . . . . . : 00-00-00-00-00-00-00-E0
    DHCP aktiviert. . . . . . . . . . : Nein
    Autokonfiguration aktiviert . . . : Ja
    IPv6-Adresse. . . . . . . . . . . : 2002:4efb:4fa3::4efb:4fa3(Bevorzugt)
    Standardgateway . . . . . . . . . : 2002:c058:6301::c058:6301
    DNS-Server . . . . . . . . . . . : 212.27.40.240
    212.27.40.241
    NetBIOS über TCP/IP . . . . . . . : Deaktiviert
     
  4. TomNice

    TomNice Thread Starter

    Joined:
    Jan 4, 2013
    Messages:
    5
    Surprise, I managed to connect with the laptop that failed until now, however it keeps losing connection and the internet is awfully slow. Here's its IPCONFIG - totally different from the good device:

    Windows-IP-Konfiguration
    Hostname . . . . . . . . . . . . : Tommy-TOSH
    Primäres DNS-Suffix . . . . . . . :
    Knotentyp . . . . . . . . . . . . : Gemischt
    IP-Routing aktiviert . . . . . . : Nein
    WINS-Proxy aktiviert . . . . . . : Nein
    Drahtlos-LAN-Adapter Drahtlosnetzwerkverbindung:
    Verbindungsspezifisches DNS-Suffix:
    Beschreibung. . . . . . . . . . . : Atheros AR9002WB-1NG Wireless Network Ada
    pter
    Physikalische Adresse . . . . . . : D0-DF-9A-F8-D0-95
    DHCP aktiviert. . . . . . . . . . : Ja
    Autokonfiguration aktiviert . . . : Ja
    Verbindungslokale IPv6-Adresse . : fe80::b0e0:f12e:c5e0:bbba%17(Bevorzugt)
    IPv4-Adresse . . . . . . . . . . : 10.1.35.244(Bevorzugt)
    Subnetzmaske . . . . . . . . . . : 255.248.0.0
    Lease erhalten. . . . . . . . . . : Freitag, 04. Jänner 2013 22:58:10
    Lease läuft ab. . . . . . . . . . : Freitag, 04. Jänner 2013 23:58:09
    Standardgateway . . . . . . . . . : 10.7.255.254
    DHCP-Server . . . . . . . . . . . : 10.7.255.254
    DHCPv6-IAID . . . . . . . . . . . : 231792538
    DHCPv6-Client-DUID. . . . . . . . : 00-01-00-01-15-F8-F5-FB-B8-70-F4-D0-E6-0F
    DNS-Server . . . . . . . . . . . : 212.27.40.241
    212.27.40.240
    NetBIOS über TCP/IP . . . . . . . : Aktiviert
    Ethernet-Adapter LAN-Verbindung:
    Medienstatus. . . . . . . . . . . : Medium getrennt
    Verbindungsspezifisches DNS-Suffix: mshome.net
    Beschreibung. . . . . . . . . . . : Realtek PCIe FE Family Controller
    Physikalische Adresse . . . . . . : B8-70-F4-D0-E6-0F
    DHCP aktiviert. . . . . . . . . . : Ja
    Autokonfiguration aktiviert . . . : Ja
    Tunneladapter LAN-Verbindung* 5:
    Verbindungsspezifisches DNS-Suffix:
    Beschreibung. . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
    Physikalische Adresse . . . . . . : 00-00-00-00-00-00-00-E0
    DHCP aktiviert. . . . . . . . . . : Nein
    Autokonfiguration aktiviert . . . : Ja
    IPv6-Adresse. . . . . . . . . . . : 2001:0:5ef5:79fb:38c4:a51:f5fe:dc0b(Bevor
    zugt)
    Verbindungslokale IPv6-Adresse . : fe80::38c4:a51:f5fe:dc0b%11(Bevorzugt)
    Standardgateway . . . . . . . . . : ::
    NetBIOS über TCP/IP . . . . . . . : Deaktiviert
    Tunneladapter isatap.{885C35A3-D091-45C5-AFCB-36554BCE573B}:
    Medienstatus. . . . . . . . . . . : Medium getrennt
    Verbindungsspezifisches DNS-Suffix:
    Beschreibung. . . . . . . . . . . : Microsoft-ISATAP-Adapter
    Physikalische Adresse . . . . . . : 00-00-00-00-00-00-00-E0
    DHCP aktiviert. . . . . . . . . . : Nein
    Autokonfiguration aktiviert . . . : Ja
    :rolleyes:
     
  5. Courtneyc

    Courtneyc

    Joined:
    Dec 6, 2003
    Messages:
    1,936
    All of the IP addresses you listed are valid. The one that starts with 78.x.x.x is a public IP address It is visible and can be routed on the Internet. The 10.x.x.x is a private IP address (the same as 192.168.x.x) and cannot be routed on the Internet (a router uses NAT to allow you to surf).

    Remember that, on most public hotspots, after you connect, you must start your web browser and surf anywhere. You will be redirected to the public hotspot's page to accept an agreement. Only then, can you surf.
     
  6. sniper1132

    sniper1132

    Joined:
    Dec 24, 2012
    Messages:
    5
    Hi. For a wireless connection specially public wi-fi hotspot.. check first there access either WEP/WPAPSK and also your device for compatibility protected access.
     
  7. TomNice

    TomNice Thread Starter

    Joined:
    Jan 4, 2013
    Messages:
    5
    Good morning,
    sorry, but this doesn't really help me. I made no specific settings on the Dell, which picked up the 78.x.x.x address correctly after logging on the sign-on page of this public hotspot provider. Neither did I consciously set parameters on the Toshiba (which won't pick up the dhcp assigned values). Why does it insist keeping these private addresses? How can I force the IP stack to behave in a manner compatible with the requirements of this hotspot? Any modifications previously made were done by the system itself when I hit on Diagnose, sometimes it says "errors have been corrected" and some values are set. What doesn't work with this public offer, is to set the IP DNS-server and GWY manually (because they want you to sign-in first).
    Does it help you to find out what is wrong if I tell you that some time ago I defined a home network on this Toshiba laptop and either connected it by ethernet cable to a router thus letting to share that connection by other devices at home, or vice versae.
    How can the entire TCP stuff be brought back to virgin state? (I tried some Netsh commands I thought appilcable, but no effect).
    Thx in advance! T.
     
  8. TomNice

    TomNice Thread Starter

    Joined:
    Jan 4, 2013
    Messages:
    5
    Hi Couriant and Courtneyc,
    I managed to get my Toshiba with Atheros wifi adapter working now with that plublic hotspot. The two modifications to my definitions that seem to have achieved this were the following:
    In the adapter configuration I set the 802.11n to enable and in the network address I set the value (copied from its MAC address). I've not a clue WHY THIS MAKES THE DIFFERENCE, but I tried it because I read in other threads in France, that the ISP fiddles around with those physical addresses in order to counter misuse due to proliferation of IDs and multiple simultaneous sign-ins.
    Also important to let others know, that all programs that sit there and vye for a connection must be stopped prior to successfull sign-in. I'd like to understand why, but that's fact.
    So my problem is resolved now (apart from skype that reclaims sometimes bad network) but I'd really like to understand why the DELL picks up the ISP distributed IPv4 address whiles the Toshiba insists on keeping the private 10.x.x.x with the submask 255.248.0.0. for itself as well as its gateway and its dhcp service. At least the DNS addresses are the correct ones 212.x.x.x.
    I'd appreciate an explanation when you've got time.
    Cheers, T.
    As a ref: the latest IPCONFIG /all:
    Windows-IP-Konfiguration
    Hostname . . . . . . . . . . . . : Tommy-TOSH
    Primäres DNS-Suffix . . . . . . . :
    Knotentyp . . . . . . . . . . . . : Gemischt
    IP-Routing aktiviert . . . . . . : Nein
    WINS-Proxy aktiviert . . . . . . : Nein
    Drahtlos-LAN-Adapter Drahtlosnetzwerkverbindung:
    Verbindungsspezifisches DNS-Suffix:
    Beschreibung. . . . . . . . . . . : Atheros AR9002WB-1NG Wireless Network Ada
    pter
    Physikalische Adresse . . . . . . : D0-DF-9A-F8-D0-95
    DHCP aktiviert. . . . . . . . . . : Ja
    Autokonfiguration aktiviert . . . : Ja
    Verbindungslokale IPv6-Adresse . : fe80::b0e0:f12e:c5e0:bbba%15(Bevorzugt)
    IPv4-Adresse . . . . . . . . . . : 10.1.119.122(Bevorzugt)
    Subnetzmaske . . . . . . . . . . : 255.248.0.0
    Lease erhalten. . . . . . . . . . : Sonntag, 06. Jänner 2013 10:05:38
    Lease läuft ab. . . . . . . . . . : Sonntag, 06. Jänner 2013 15:18:39
    Standardgateway . . . . . . . . . : 10.7.255.254
    DHCP-Server . . . . . . . . . . . : 10.7.255.254
    DHCPv6-IAID . . . . . . . . . . . : 231792538
    DHCPv6-Client-DUID. . . . . . . . : 00-01-00-01-15-F8-F5-FB-B8-70-F4-D0-E6-0F
    DNS-Server . . . . . . . . . . . : 212.27.40.241
    212.27.40.240
    NetBIOS über TCP/IP . . . . . . . : Aktiviert
    Ethernet-Adapter LAN-Verbindung:
    Medienstatus. . . . . . . . . . . : Medium getrennt
    Verbindungsspezifisches DNS-Suffix: mshome.net
    Beschreibung. . . . . . . . . . . : Realtek PCIe FE Family Controller
    Physikalische Adresse . . . . . . : B8-70-F4-D0-E6-0F
    DHCP aktiviert. . . . . . . . . . : Ja
    Autokonfiguration aktiviert . . . : Ja
    Tunneladapter isatap.{885C35A3-D091-45C5-AFCB-36554BCE573B}:
    Medienstatus. . . . . . . . . . . : Medium getrennt
    Verbindungsspezifisches DNS-Suffix:
    Beschreibung. . . . . . . . . . . : Microsoft-ISATAP-Adapter
    Physikalische Adresse . . . . . . : 00-00-00-00-00-00-00-E0
    DHCP aktiviert. . . . . . . . . . : Nein
    Autokonfiguration aktiviert . . . : Ja
    Tunneladapter LAN-Verbindung* 5:
    Verbindungsspezifisches DNS-Suffix:
    Beschreibung. . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
    Physikalische Adresse . . . . . . : 00-00-00-00-00-00-00-E0
    DHCP aktiviert. . . . . . . . . . : Nein
    Autokonfiguration aktiviert . . . : Ja
    IPv6-Adresse. . . . . . . . . . . : 2001:0:5ef5:79fd:28d2:fb0:f5fe:8885(Bevor
    zugt)
    Verbindungslokale IPv6-Adresse . : fe80::28d2:fb0:f5fe:8885%11(Bevorzugt)
    Standardgateway . . . . . . . . . : ::
    NetBIOS über TCP/IP . . . . . . . : Deaktiviert
    Tunneladapter isatap.mshome.net:
    Medienstatus. . . . . . . . . . . : Medium getrennt
    Verbindungsspezifisches DNS-Suffix:
    Beschreibung. . . . . . . . . . . : Microsoft-ISATAP-Adapter #2
    Physikalische Adresse . . . . . . : 00-00-00-00-00-00-00-E0
    DHCP aktiviert. . . . . . . . . . : Nein
    Autokonfiguration aktiviert . . . : Ja
     
  9. Sponsor

As Seen On
As Seen On...

Welcome to Tech Support Guy!

Are you looking for the solution to your computer problem? Join our site today to ask your question. This site is completely free -- paid for by advertisers and donations.

If you're not already familiar with forums, watch our Welcome Guide to get started.

Join over 733,556 other people just like you!

Thread Status:
Not open for further replies.

Short URL to this thread: https://techguy.org/1083693

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice