ChatterBank0 min ago
ip address
10 Answers
Help. im going demented, whilst i was working away my mrs had probs with logging on via our modem, she finaly got it sorted with help from aol and everything is hunky dory for her, but now im home i cannot log on with my lap top, it seems she changed the name of our net work, and now when i try to log on it comes up saying im connected with 54.0Mbps strength excellent, acquiring network address, i have tried the trouble shooter and it says i have an invalid IP address 0.0.0.0 subnet mask 0.0.0.0. when i click on repair wireless network connection it says windows is renewing my IP address, this has been on for over an hour now. any suggestions people?
Answers
1 to 10 of 10
Best Answer
No best answer has yet been selected by schiehallion. Once a best answer has been selected, it will be shown here.
For more on marking an answer as the "Best Answer", please visit our FAQ.
wired or wireless?
open a command prompt
type ipconfig
will show something like this
Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 192.168.2.168
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.2.254
then type
ping 127.0.0.1
should say
Pinging 127.0.0.1 with 32 bytes of data:
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
come back with your results
gateway is your router .... so that's important
open a command prompt
type ipconfig
will show something like this
Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 192.168.2.168
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.2.254
then type
ping 127.0.0.1
should say
Pinging 127.0.0.1 with 32 bytes of data:
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
come back with your results
gateway is your router .... so that's important
I t came back with
reply from 127.0.0.1 : bytes=32 time<1ms TTL=128
reply from 127.0.0.1 : bytes=32 time<1ms TTL=128
reply from 127.0.0.1 : bytes=32 time<1ms TTL=128
Reply from 127.0.0.1 : bytes=32 time<1ms TTL=128 packets sent =4, recieved =4 lost =0 (0%loss) approx round trip times in milliseconds: minimum = 0ms, maximum= 0ms average = 0ms
reply from 127.0.0.1 : bytes=32 time<1ms TTL=128
reply from 127.0.0.1 : bytes=32 time<1ms TTL=128
reply from 127.0.0.1 : bytes=32 time<1ms TTL=128
Reply from 127.0.0.1 : bytes=32 time<1ms TTL=128 packets sent =4, recieved =4 lost =0 (0%loss) approx round trip times in milliseconds: minimum = 0ms, maximum= 0ms average = 0ms
So the TCP stack hasn't fallen over then, thats good :)
Sounds to me like you have got the wireless network key wrong, I assume you have windows XP!
XP is a pain because if you use the wrong network key to connect wireless it will connect and won't report any errors but you will not be able to use the connection and your router won't assign you an IP address (thats why your getting 0.0.0.0)
disconnect from the wireless network and then connect again and it should prompt you for the wireless key again, re-enter it and it should work OK
If you don't know the wireless key then you will need to use the other compuer that does work to login to the wireless routers admin pages to get it, if you need help with this post back with make of router.
Sounds to me like you have got the wireless network key wrong, I assume you have windows XP!
XP is a pain because if you use the wrong network key to connect wireless it will connect and won't report any errors but you will not be able to use the connection and your router won't assign you an IP address (thats why your getting 0.0.0.0)
disconnect from the wireless network and then connect again and it should prompt you for the wireless key again, re-enter it and it should work OK
If you don't know the wireless key then you will need to use the other compuer that does work to login to the wireless routers admin pages to get it, if you need help with this post back with make of router.
chuck has the next bit covered
just to explain what I asked you to do
the rough guide
127.0.0.1 is the network within your machine - so if you ping (send a test message) and it replies it's an indication that the drivers and hardware are correct
ipconfig shows the other side of the hardware - the bit that connects to your router/modem
generally a network address is allocated automatically by the router
(known as dhcp) - if dhcp is working ... and the connection is there - it isn't talking to the router you generally get a 169 address
if the connection is there and dhcp is off (with wireless it's generally because the key is missing) you get 0.0.0.0
if the connection isn't there at all ... you get an error message
so you now know all about networking
just to explain what I asked you to do
the rough guide
127.0.0.1 is the network within your machine - so if you ping (send a test message) and it replies it's an indication that the drivers and hardware are correct
ipconfig shows the other side of the hardware - the bit that connects to your router/modem
generally a network address is allocated automatically by the router
(known as dhcp) - if dhcp is working ... and the connection is there - it isn't talking to the router you generally get a 169 address
if the connection is there and dhcp is off (with wireless it's generally because the key is missing) you get 0.0.0.0
if the connection isn't there at all ... you get an error message
so you now know all about networking
1 to 10 of 10
