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 | Rate Thread | Display Modes |
#1
|
|||
|
|||
cranky enet connection upon boot
My deskside machine has wired ethernet to my router. It has
forever been the case that Windows latches onto the network at boot every time with no problems until now. I cannot think of anything I have changed. Perhaps this is the result of an update, but now when I boot the machine the network connection does not take place and I have to fiddle with disabling/enabling the adapter a few times before it does connect. That's not a big problem, but I'm curious what might cause it. ...and it is not quite consistent - about one time in five it connects instantly just like it used to. Hardware diagnostics don't show anything. |
Ads |
#2
|
|||
|
|||
cranky enet connection upon boot
On Wed, 13 Mar 2019 19:48:01 -0400, Jason
wrote: My deskside machine has wired ethernet to my router. It has forever been the case that Windows latches onto the network at boot every time with no problems until now. I cannot think of anything I have changed. Perhaps this is the result of an update, but now when I boot the machine the network connection does not take place and I have to fiddle with disabling/enabling the adapter a few times before it does connect. That's not a big problem, but I'm curious what might cause it. ...and it is not quite consistent - about one time in five it connects instantly just like it used to. Hardware diagnostics don't show anything. Do you have a router? Are you using DHCP? Are you using address reservation, or whatever your router calls it? When it doesn't connect, what is your IP address? Is it in the range of 169.254.x.y? Do you have any other network devices on your LAN? If so, do any of them sometimes display similar behavior? If you're using a router and it's configured to use DHCP and the PC ends up with a 169.254.x.y address, the problem could be the PC or the router. You can work around that particular issue by configuring a static IP address (plus netmask, default gateway, and DNS servers) on your PC. If you set static values, it's one and done. You just need to take care to assign an IP address that's within your current subnet but not within your DHCP scope. The trick is to take a look at your networking info while you're experiencing the issue. Once you've resolved the issue, it's too late to do much troubleshooting. Command Prompt "ifconfig /all" would be a good start, or you can poke around in "Network and Internet Settings", then "Change Adapter Options", pick the adapter, then select Status from the context menu. |
#3
|
|||
|
|||
cranky enet connection upon boot
|
#4
|
|||
|
|||
cranky enet connection upon boot
On Thu, 14 Mar 2019 10:59:44 -0400, Jason
wrote: In article , says... The trick is to take a look at your networking info while you're experiencing the issue. Once you've resolved the issue, it's too late to do much troubleshooting. That's excellent advice (as is the rest you provided). I'll take a look next time it's broken at startup. Thanks. You're welcome. Good luck. |
#5
|
|||
|
|||
cranky enet connection upon boot
Jason wrote:
My deskside machine has wired ethernet to my router. It has forever been the case that Windows latches onto the network at boot every time with no problems until now. I cannot think of anything I have changed. Perhaps this is the result of an update, but now when I boot the machine the network connection does not take place and I have to fiddle with disabling/enabling the adapter a few times before it does connect. That's not a big problem, but I'm curious what might cause it. ...and it is not quite consistent - about one time in five it connects instantly just like it used to. Hardware diagnostics don't show anything. Well the first thing I do is test the cable. Most most folks don't have a test handy but my advise is always have a spare cable to test. If you unplug cable and reinsert it does the connection connect immediately? If so maybe the wire connector is loose or damaged. Next what happens if from a CMD windows you renew the DHCP lease with: ipconfig /renew -- Take care, Jonathan ------------------- LITTLE WORKS STUDIO http://www.LittleWorksStudio.com |
#6
|
|||
|
|||
TYPO cranky enet connection upon boot
"Jason" wrote in message
... In article , says... The trick is to take a look at your networking info while you're experiencing the issue. Once you've resolved the issue, it's too late to do much troubleshooting. That's excellent advice (as is the rest you provided). I'll take a look next time it's broken at startup. Thanks. There's a typo - use ipconfig /all -- Bob S. |
#7
|
|||
|
|||
TYPO cranky enet connection upon boot
On Thu, 14 Mar 2019 20:49:08 -0400, "n/a" wrote:
"Jason" wrote in message al-september.org... In article , says... The trick is to take a look at your networking info while you're experiencing the issue. Once you've resolved the issue, it's too late to do much troubleshooting. That's excellent advice (as is the rest you provided). I'll take a look next time it's broken at startup. Thanks. There's a typo - use ipconfig /all Good catch, thanks. |
Thread Tools | |
Display Modes | Rate This Thread |
|
|