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
|
|||
|
|||
Some network protocols are missing on this computer?
I was have some flaky behavior WRT to my Ethernet at home so I brought
the notebook and a Cat 6 cable up to the University. Here it cannot connect. It set an auto-config IP which is useless. Network diagnostics reports some network diagnostics are missing on this computer and further probing reveals "Windows Sockets registry entries required for network connectivity are missing". Thanks in advance. |
Ads |
#2
|
|||
|
|||
Some network protocols are missing on this computer?
Norm X wrote:
Network diagnostics reports some network diagnostics are missing on this computer and further probing reveals "Windows Sockets registry entries required for network connectivity are missing". It's a long time (win9x days) since I've needed to reset winsock, but it seems you can still do it in win10 http://www.thewindowsclub.com/reset-tcp-ip-internet-protocol |
#3
|
|||
|
|||
Some network protocols are missing on this computer?
On 2016-02-01 12:57 PM, Andy Burns wrote:
Norm X wrote: Network diagnostics reports some network diagnostics are missing on this computer and further probing reveals "Windows Sockets registry entries required for network connectivity are missing". It's a long time (win9x days) since I've needed to reset winsock, but it seems you can still do it in win10 http://www.thewindowsclub.com/reset-tcp-ip-internet-protocol Thanks for the suggestion. As administrator, it failed thus: C:\WINDOWS\system32netsh int ip reset resettcpip.txt Resetting Interface, OK! Resetting Unicast Address, OK! Resetting Neighbor, OK! Resetting Path, OK! Resetting , failed. Access is denied. Resetting , OK! Restart the computer to complete this action. /// I guess I'll need to study the website further. |
#4
|
|||
|
|||
Some network protocols are missing on this computer?
Norm X wrote:
I was have some flaky behavior WRT to my Ethernet at home so I brought the notebook and a Cat 6 cable up to the University. Here it cannot connect. It set an auto-config IP which is useless. Network diagnostics reports some network diagnostics are missing on this computer and further probing reveals "Windows Sockets registry entries required for network connectivity are missing". Thanks in advance. If you are seeing that error on a network with Win10 devices and not seeing Win7 or earlier o/s devices Computername and their respective shares....ignore the Winsock error - it means nothing. MSFT is aware and working on a solution. Attempts to fix Winsock(patch or replace the file are not recommended). -- ....winston msft mvp windows experience |
#5
|
|||
|
|||
Some network protocols are missing on this computer?
On 2016-02-01 2:45 PM, ...winston‫ wrote:
Norm X wrote: I was have some flaky behavior WRT to my Ethernet at home so I brought the notebook and a Cat 6 cable up to the University. Here it cannot connect. It set an auto-config IP which is useless. Network diagnostics reports some network diagnostics are missing on this computer and further probing reveals "Windows Sockets registry entries required for network connectivity are missing". Thanks in advance. If you are seeing that error on a network with Win10 devices and not seeing Win7 or earlier o/s devices Computername and their respective shares....ignore the Winsock error - it means nothing. MSFT is aware and working on a solution. Attempts to fix Winsock(patch or replace the file are not recommended). Thank you for the recommendation. Let me add some details. I have a farm of 5 computers with one 5 port GHz Ethernet switch. I use Remote Desktop a lot and I have never had a network or RDP problem with Linux. The Ethernet problem I have with my Win10 machine is relatively recent. Sometimes 1 GHz Ethernet and RDP are stable over a period of days with Win10. On the farm I prefer to use static address and also IPv6 using a tunnel broker. Yesterday, At the university I could not connect autoconfig Ethernet period. I took my Win10 machine home and reverted to static addressing. It worked for a period of minutes. I tried to open RDP into my Win7 machine and it froze before it could fully open the screen. As is typical it tried to reconnect 10 times. Now that you have informed to wait for a Microsoft solution, I'll disconnect the Cat 6 Ethernet cable from a port in the floor of the library and relax. I still have WiFi. Thanks again. |
#6
|
|||
|
|||
Some network protocols are missing on this computer?
Norm X wrote:
On 2016-02-01 2:45 PM, ...winston‫ wrote: Norm X wrote: I was have some flaky behavior WRT to my Ethernet at home so I brought the notebook and a Cat 6 cable up to the University. Here it cannot connect. It set an auto-config IP which is useless. Network diagnostics reports some network diagnostics are missing on this computer and further probing reveals "Windows Sockets registry entries required for network connectivity are missing". Thanks in advance. If you are seeing that error on a network with Win10 devices and not seeing Win7 or earlier o/s devices Computername and their respective shares....ignore the Winsock error - it means nothing. MSFT is aware and working on a solution. Attempts to fix Winsock(patch or replace the file are not recommended). Thank you for the recommendation. Let me add some details. I have a farm of 5 computers with one 5 port GHz Ethernet switch. I use Remote Desktop a lot and I have never had a network or RDP problem with Linux. The Ethernet problem I have with my Win10 machine is relatively recent. Sometimes 1 GHz Ethernet and RDP are stable over a period of days with Win10. On the farm I prefer to use static address and also IPv6 using a tunnel broker. Yesterday, At the university I could not connect autoconfig Ethernet period. I took my Win10 machine home and reverted to static addressing. It worked for a period of minutes. I tried to open RDP into my Win7 machine and it froze before it could fully open the screen. As is typical it tried to reconnect 10 times. Now that you have informed to wait for a Microsoft solution, I'll disconnect the Cat 6 Ethernet cable from a port in the floor of the library and relax. I still have WiFi. Thanks again. Good luck. You are not the only one seeing a variety of different variation scenarios across the Win10 to other devices(o/s, NAT, Remote, etc.). In time it should shake out though it may take more adoption of Win10 in the Enterprise market and understanding of these networking issues to make progress on a solution in the Consumer and Small Business ecosystem. For my personal devices on a simple home network(all devices have a same username/pw non-MSFT account in Admin mode) - - the Win10 and Win8 devices aren't the problem and always appear automatically - for Win7 I just pin the //Computername as a shortcut to the Win10 Taskbar. Sometimes the Win7 device appears in the Navigation pane Network folder with the other o/s Computername, sometimes it doesn't...but clicking that pinned shortcut never fails to provide access to the Win7 device and its shares - it may take a few seconds to find it though. -- ....winston msft mvp windows experience |
Thread Tools | |
Display Modes | Rate This Thread |
|
|