help please invalid ip


  1. Posts : 2
    Windows 7 Home Premium 64bit
       #1

    help please invalid ip


    Ok so i have an HP touchsmart computer running windows 7 home premium 64bit and im in the army living in the barracks so my only internet source is a hotspot that they have set up for us in the barracks my problem is that when i try to connect to it it says

    "Wireless Network Connection dosnt have a valid ip configuration"
    i have went through the cmd and did the ipconfig/all, ipconfig/release, ipconfig/renew with no luck iv reinstalled my drivers for my wireless card this is what i got with my ipconfig/all



    C:\Windows\system32>ipconfig/all

    Windows IP Configuration

    Host Name . . . . . . . . . . . . : T-PC
    Primary Dns Suffix . . . . . . . :
    Node Type . . . . . . . . . . . . : Hybrid
    IP Routing Enabled. . . . . . . . : No
    WINS Proxy Enabled. . . . . . . . : No

    Ethernet adapter Local Area Connection 3:

    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : PdaNet Broadband Adapter
    Physical Address. . . . . . . . . : 00-26-37-BD-39-42
    DHCP Enabled. . . . . . . . . . . : Yes
    Autoconfiguration Enabled . . . . : Yes
    Link-local IPv6 Address . . . . . : fe80::961:747:4262:5901%22(Preferred)
    IPv4 Address. . . . . . . . . . . : 192.168.9.2(Preferred)
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Lease Obtained. . . . . . . . . . : Saturday, February 26, 2011 2:10:21 PM
    Lease Expires . . . . . . . . . . : Sunday, February 27, 2011 2:10:20 PM
    Default Gateway . . . . . . . . . : 192.168.9.1
    DHCP Server . . . . . . . . . . . : 192.168.9.1
    DHCPv6 IAID . . . . . . . . . . . : 721430071
    DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-14-73-A3-65-00-22-15-82-CD-67

    DNS Servers . . . . . . . . . . . : 8.8.8.8
    NetBIOS over Tcpip. . . . . . . . : Enabled

    Wireless LAN adapter Wireless Network Connection:

    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : 802.11n Wireless LAN Card
    Physical Address. . . . . . . . . : 00-22-5F-04-E9-FF
    DHCP Enabled. . . . . . . . . . . : Yes
    Autoconfiguration Enabled . . . . : Yes
    Link-local IPv6 Address . . . . . : fe80::5492:cb4a:3735:e63%12(Preferred)
    Autoconfiguration IPv4 Address. . : 169.254.14.99(Preferred)
    Subnet Mask . . . . . . . . . . . : 255.255.0.0
    Default Gateway . . . . . . . . . :
    DHCPv6 IAID . . . . . . . . . . . : 201335391
    DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-14-73-A3-65-00-22-15-82-CD-67

    DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
    fec0:0:0:ffff::2%1
    fec0:0:0:ffff::3%1
    NetBIOS over Tcpip. . . . . . . . : Enabled

    Tunnel adapter isatap.{D91B34EC-80FF-42A7-A327-2052F1F48311}:

    Media State . . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Microsoft ISATAP Adapter
    Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter Teredo Tunneling Pseudo-Interface:

    Media State . . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
    Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter isatap.{27E5F2D1-6AAB-4B3D-B10C-D7DCCFA3BB21}:

    Media State . . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3
    Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter 6TO4 Adapter:

    Media State . . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Microsoft 6to4 Adapter
    Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes

    C:\Windows\system32>
    i really dont know what to do i called the people in charge of the hotspot and they couldnt help me so maybe someone here can
      My Computer


  2. Posts : 52
    Windows 7 Pro 64bit
       #2

    travis6969 said:
    Autoconfiguration IPv4 Address. . : 169.254.14.99
    This means the computer is set up to receive an IP address via DHCP, but isn't able to for some reason.....no DHCP server available, cannot contact DHCP server, all DHCP leases used up, etc........

    Are you the only one having problems?

    If someone else can connect, find out their IP info, get the default gateway & subnet mask, and try configuring a static IP in the same subnet. When you choose an IP, before you configure it on your laptop, have your colleague ping it to make sure it is not already being used. Then, set your laptop and see if you connect.

    Please let us know how it goes.
      My Computer


  3. Posts : 2
    Windows 7 Home Premium 64bit
    Thread Starter
       #3

    how do i know what numbers to use when i make a new ip iv never set up a static ip before
      My Computer


  4. Posts : 52
    Windows 7 Pro 64bit
       #4

    Well, you have to understand subnetting, at least a little bit.

    How about, when you find someone who can connect, get their ipconfig, and all we need are the default gateway and the subnet mask. Be sure you are looking at the correct interface. The one they are actually connecting with. Post the info here, and I can tell you a range of IPs you can try.
      My Computer


  5. Posts : 52
    Windows 7 Pro 64bit
       #5

    Are there a lot of people in your area who use computers on the network...wireless and wired?
      My Computer


  6. Posts : 9
    Windows 7 Ultimate (x64)
       #6

    what do you have physically plugged into your network jack? i see what looks to be a (seemingly) successful connect on this interface:

    Ethernet adapter Local Area Connection 3:

    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : PdaNet Broadband Adapter
    Physical Address. . . . . . . . . : 00-26-37-BD-39-42
    DHCP Enabled. . . . . . . . . . . : Yes <--- DHCP is enabled, good
    Autoconfiguration Enabled . . . . : Yes
    Link-local IPv6 Address . . . . . : fe80::961:747:4262:5901%22(Preferred) <-- looks like it has an IPv6 address
    IPv4 Address. . . . . . . . . . . : 192.168.9.2(Preferred) <-- most importantly, here... this is a valid internal IP address
    Subnet Mask . . . . . . . . . . . : 255.255.255.0 <-- same with the subnet mask
    Lease Obtained. . . . . . . . . . : Saturday, February 26, 2011 2:10:21 PM
    Lease Expires . . . . . . . . . . : Sunday, February 27, 2011 2:10:20 PM
    Default Gateway . . . . . . . . . : 192.168.9.1 <-- the gateway would fall again, in line with your IP address on this adapter (gateway is .1, and the first IP address for DHCP to hand out seems to be .2)
    DHCP Server . . . . . . . . . . . : 192.168.9.1 <-- DHCP server is most times the gateway IP as well, so nothing odd here
    DHCPv6 IAID . . . . . . . . . . . : 721430071
    DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-14-73-A3-65-00-22-15-82-CD-67

    DNS Servers . . . . . . . . . . . : 8.8.8.8 <-- this is one of Google's public DNS servers, so it should work fine.
    NetBIOS over Tcpip. . . . . . . . : Enabled
    But in the first line, where it says Ethernet and Local Area Connection -- that typically would mean it's something that is plugged directly into your ethernet/network jack (a physical cable).

    Looking at the other connection, which is likely the one you're wanting to connect with, there are a couple of strange things... they already hit on some of them:

    Wireless LAN adapter Wireless Network Connection:

    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : 802.11n Wireless LAN Card
    Physical Address. . . . . . . . . : 00-22-5F-04-E9-FF
    DHCP Enabled. . . . . . . . . . . : Yes <-- good
    Autoconfiguration Enabled . . . . : Yes
    Link-local IPv6 Address . . . . . : fe80::5492:cb4a:3735:e63%12(Preferred) <-- not really the greatest in this time of technology
    Autoconfiguration IPv4 Address. . : 169.254.14.99(Preferred) <-- as they mentioned, this is an "autoconfiguration" IP, if it starts with 169, it's just a "fake" IP the computer gives to itself, and it's not going to work for your purposes
    Subnet Mask . . . . . . . . . . . : 255.255.0.0
    Default Gateway . . . . . . . . . : <-- obviously it's having trouble finding the Gateway, which is essential.
    DHCPv6 IAID . . . . . . . . . . . : 201335391
    DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-14-73-A3-65-00-22-15-82-CD-67

    DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1 <-- this concerns me, the DNS servers are all listed in IPv6 format, which in all truth, means you probably won't connect and be able to do stuff.
    fec0:0:0:ffff::2%1
    fec0:0:0:ffff::3%1
    NetBIOS over Tcpip. . . . . . . . : Enabled
    We know that's the wireless connection though. Try this -- go into your advanced network settings (type "ncpa.cpl" in your start menu search or your Run... box), and that will take you directly to where you wanna be. You'll see those adapters listed, the ones from the ipconfig. Try to right click on the Wireless one, go to properties, then look at the first page that comes up. You should see several things checked, IPv4 being one... (we want to keep that one checked), and IPv6 being another (try to temporarily uncheck that). Make sure you hit OK to save the changes, then you can go to your dos prompt (command prompt) and type these commands in this order:

    ipconfig /release
    ipconfig /flushdns
    ipconfig /renew

    Once that gets done, all the IPv6 stuff should not be showing. Then do your ipconfig /all

    You should hopefully see something to this effect:

    Description . . . . . . . . . . . : Intel(R) Gigabit Network Connection
    Physical Address. . . . . . . . . : 00-00-00-00-00-00
    DHCP Enabled. . . . . . . . . . . : Yes
    Autoconfiguration Enabled . . . . : Yes
    IPv4 Address. . . . . . . . . . . : 192.168.1.100(Preferred)
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Lease Obtained. . . . . . . . . . : Thursday, April 21, 2011 10:16:16 PM
    Lease Expires . . . . . . . . . . : Monday, May 29, 2147 7:25:53 PM
    Default Gateway . . . . . . . . . : 192.168.1.1
    DHCP Server . . . . . . . . . . . : 192.168.1.1
    DNS Servers . . . . . . . . . . . : 208.67.222.222
    208.67.220.220
    NetBIOS over Tcpip. . . . . . . . : Enabled
    Typically you'll want to make sure you see three or four major things here:
    IPv4 address -- it should start with 192.168.x.x, or 10.x.x.x -- the first IP scheme is used 90% of the time, you'll rarely see 10.x.x.x or 172.x.x.x outside of more complex networks.
    Subnet mask -- this should almost always be 255.255.255.0 on a normal access point/router
    Default gateway -- will often be 192.168.1.1, or 192.168.0.1, maybe 192.168.1.254 -- point is, it's usually going to also be 192.168.x.x, whereas the x's can be anything from 0 or 1 to 254 max.
    DNS servers -- these will be different each time, but if you see the ones I show up there (OpenDNS) or DNS Servers with IP addresses of 8.8.8.8 and/or 8.8.4.4, those are Google's DNS servers, and again, should be fine.

    Good luck, and if that doesn't solve your woes, you know where we're at.

    ... And I think where Ray Finkle may be going is that one a subnet of 255.255.255.0, that means there are only going to be about 250 or so maximum # of people who can connect at a time. This is just due to what they were talking about subnetting.... 192.168.1.x would be a subnet of 255.255.255.0 -- if you can kinda grasp this, it's like an overlay (hence the term "mask") it means people with 192.168.1.x addresses can only talk to people with the same first 3 numbers (octets); for example a 192.168.50.x address would not be able to talk to the 192.168.1.x computers. If we open it up a little to 255.255.0.0, that means basically that anyone with any combination of the last two numbers can talk to each other.

    So with a subnet of 255.255.0.0 -- two computers with these IP addresses: 192.168.10.100 and 192.168.20.200 can see and talk. The big deal about that is that it expands your available people on the same subnetwork from 253 max, to well... a lot more.

    If you really wanna get ballsy with it (I have a feeling you don't, LOL) check out:

    http://en.wikipedia.org/wiki/Network_class
    http://en.wikipedia.org/wiki/IPv4_subnetting_reference
    http://en.wikipedia.org/wiki/Subnetwork

    I remember the concept being pretty intimidating when first approached in college. Turned out I just had really $%#$ teachers/professors who had a hard time translating what almost looks like math theory into something tangible and useful to apply to the real world. I learned nothing in college, BTW. Everything I know, I had to learn myself -- they gave me a very expensive piece of paper and wasted several years of my life... for a Computer Science degree that really nobody even cares about. They want to know how much experience in the field do you have. I think it's because they know the truth about CS degrees -- they teach you all theory and concepts... and total fail at teaching you anything that can actually be applied once you hit the real world. At least my college did that. I suppose it holds merit for simply being able to explain things like subnetting, etc... but the truth is, clients... don't wanna hear that $%#! No more than you do... They just want it fixed!

    Sorry. My little tangent rant. Get back with us....
    Last edited by Chinch; 22 Apr 2011 at 12:28.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 18:40.
Find Us