If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
New Situation. TCP/IP Can't Assign DHCP address
Previously I have asked in here about my mother's network
would completely shut down, and the only way she could get it back was to resstart the computer. Though last week it started off as they would have connection for about an hour. Then starting yesturday, the network would only last one minute. I got a reply back from here stating to make that 802.1x authentication is not enabled, which it wasn't. I also made sure that the Default IPaddress, Default Gateway, and subnet mask address were to the correct settings to what comcast requires which everything looked right as to the tcp/ip settins. However here's the weird part, we left it alone and went to our picnic and came back and my mother saw an error message on her laptop that the WEP somthing has been disabled do you want to continue anyway. She said yes, then she got another error that said the antena switch was not turned on however the switch in the back of the computer was turned on. She went downstairs and looked at the network connections and said both the 1394 and the Local Area Connection said disabled. She called comcast, and they said to try connecting the main computer directly to the modem and restart the computer. When she did that, the Local Area Connection re-enabled itself, HOWEVER it now keeps on signing an Automatic Private Address instead of dynamically assigning a DHCP address. Meaning she keeps on getting the 169.254.x.y instead. |
#2
|
|||
|
|||
In article , Bob N. says...
snip She went downstairs and looked at the network connections and said both the 1394 and the Local Area Connection said disabled. She called comcast, and they said to try connecting the main computer directly to the modem and restart the computer. When she did that, the Local Area Connection re-enabled itself, HOWEVER it now keeps on signing an Automatic Private Address instead of dynamically assigning a DHCP address. Meaning she keeps on getting the 169.254.x.y instead. The computer gets a "LinkLocal" (169.254.0.0/16) IP address when it can't get an IP address from a DHCP server. If this is happening when the computer is connected directly to the modem, then either the computer is misconfigured, or the modem isn't able to negotiate a connection with the service. -- Norman ~Win dain a lotica, En vai tu ri, Si lo ta ~Fin dein a loluca, En dragu a sei lain ~Vi fa-ru les shutai am, En riga-lint |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
How to tell which protocol (NetBUI or TCP/IP) each Network Neighborhood connection is using | Dave Burton | Networking | 26 | August 8th 04 07:22 AM |
How to tell which protocol (NetBUI or TCP/IP) each Network Neighborhood connection is using | Dave Burton | Networking | 26 | August 8th 04 07:22 AM |
Can't enter IP address in TCP/IP properties | John H. | Networking | 0 | July 12th 04 11:20 AM |
home networking - ICS problem | Bruce | Networking | 7 | July 1st 04 09:38 PM |
Wireless Interface Present / Can't PING Out | Fred Marshall | Networking | 4 | June 11th 04 02:15 AM |