Network connection drops while on cable

Question

Network connection drops while on cable

Anonymous

I have the following setup:

2 x windows 10 and 1 X windows 7 computers connected to the same router through cable having 192.168.0.1 as the router gateway.

win7-box: 192.168.0.38
win10-box1: 192.168.0.211
win10-box2: 192.168.0.24

I am connecting from win7-box, which I'm using as the main machine, through RDP to the other 2 win10 machines.

The connection to 192.168.0.211 runs smoothly but when I connect to 192.168.0.24, the connection gets interrupted after 30-60 seconds and I get the "This computer can't connect to the remote computer" error:

While ping 192.168.0.24 -t from 192.168.0.38 was running I got this:

Even if after the The connection has been lost error that corresponds to the Request timed outping error - the connection seems to be restored (as ping is up again), if I try to RDP again I get the "Destination host unreachable" error.

Now I cannot RDP to 192.168.0.24 anymore until I manually log into this host by physically using its keyboard.

I also did a ping 192.168.0.1 -t on 192.168.0.24 and noticed the General Failure error that corresponds to the Request timed out from the win7-box

I also noticed that I get the General Failure error intermittently, even if don't try a RDP connection on this win10-box2 machine.

What I did:

I tried a Network Reset from the Network&Internet settings:

Tried switching the cable itself and the cable port on the router
Tried using a different static ip, other than 192.168.0.24
Tried using the wireless connection to the same router and noticed that even if do get some isolated Request timed out error when continuously pinging win10-box's ip, no issues are found and RDP connection is stable.

I assume this has to be something wrong in my current win10-box2 configuration as the router seems to be working fine on other devices.

The network configuration on win10-box2 is as follows:

The question would be - what else should I try/check in order to solve this issue?

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

3 answers

Answer 1

Hi,[Jorje]

I'm Independent Advisor. I hope it helps.

Click Start, and type "cmd".

Right-click Command Prompt and run it as administrator.
Copy and paste the below one line at a time, pressing enter each time:

netsh winsock reset - and press Enter.

netsh int ip reset - and press Enter.

ipconfig /release - and press Enter.

ipconfig /renew - and press Enter.

ipconfig /flushdns - and press Enter

You could also try resetting your DNS service with the following steps:

Press Windows Key+R and type "services.msc" and press OK.
Scroll down to find DNS Client.
Right-click it and click Restart.

Otherwise, see if resetting your Hosts file to default fixes the issue:

https://support.microsoft.com/en-au/help/972034...

https://support.microsoft.com/en-us/help/10741/...

Hope this helps. Keep us posted on the status for further assistance.

Answer 2

Hi Guys,

To solve this problem, try uninstalling your Version of "npcap" in your Apps & Features.

If you are required to use npcap drivers for software like WireShark, nmap, ... consider installing the drivers without creating the Npcap Loopback Adapter.

This was the solution for one of our customers.

Hope this could help you out.

Best Regards

Michael

Answer 3

Hi Philip,

So here is the output for the commands you have suggested:

C:\WINDOWS\system32>netsh winsock reset

Sucessfully reset the Winsock Catalog.

You must restart the computer in order to complete the reset.

C:\WINDOWS\system32>netsh int ip reset

Resetting Compartment Forwarding, OK!

Resetting Compartment, OK!

Resetting Control Protocol, OK!

Resetting Echo Sequence Request, OK!

Resetting Global, OK!

Resetting Interface, OK!

Resetting Anycast Address, OK!

Resetting Multicast Address, OK!

Resetting Unicast Address, OK!

Resetting Neighbor, OK!

Resetting Path, OK!

Resetting Potential, OK!

Resetting Prefix Policy, OK!

Resetting Proxy Neighbor, OK!

Resetting Route, OK!

Resetting Site Prefix, OK!

Resetting Subinterface, OK!

Resetting Wakeup Pattern, OK!

Resetting Resolve Neighbor, OK!

Resetting , OK!

Resetting , failed.

Access is denied.

Resetting , OK!

Restart the computer to complete this action.

C:\WINDOWS\system32>ipconfig /release

Windows IP Configuration

No operation can be performed on Ethernet 3 while it has its media disconnected.

An error occurred while releasing interface Npcap Loopback Adapter : An address has not yet been associated with the network endpoint.

No operation can be performed on Wi-Fi while it has its media disconnected.

Ethernet adapter Ethernet 3:

Media State . . . . . . . . . . . : Media disconnected

Connection-specific DNS Suffix . :

Ethernet adapter Npcap Loopback Adapter:

Connection-specific DNS Suffix . :

Link-local IPv6 Address . . . . . : fe80::92b3:4c41:93d7:1a1f%13

Autoconfiguration IPv4 Address. . : 169.254.26.31

Subnet Mask . . . . . . . . . . . : 255.255.0.0

Default Gateway . . . . . . . . . :

Wireless LAN adapter Wi-Fi:

Media State . . . . . . . . . . . : Media disconnected

Connection-specific DNS Suffix . : home

Ethernet adapter Ethernet 2:

Connection-specific DNS Suffix . :

Link-local IPv6 Address . . . . . : fe80::d920:f57c:d7b:e334%27

Default Gateway . . . . . . . . . :

C:\WINDOWS\system32>ipconfig /renew

Windows IP Configuration

No operation can be performed on Ethernet 3 while it has its media disconnected.

^C

[here I was forced to Ctrl+c as the command seemed to hang]

C:\WINDOWS\system32>ipconfig /flushdns

Windows IP Configuration

Successfully flushed the DNS Resolver Cache.

C:\WINDOWS\system32>

Also tried to reset the DNS service but I was unable as the right-click menu was grayed out:

After doing all that, my internet connection was unavailable:

So I was forced to Troubleshoot:

Did a reboot. The problem persists. Now what?

For example, if I play Starcraft online, I get the same behavior where the connection drops somewhere at the beginning of the game.

I was pinging google here.