Windows 10: Ping went up by 15 on ethernet

Recently had a internet outage due to the old ports in my building. After the technician came and fixed it I noticed that my ping went up by 15 since before the outage. I've tried changing DNS, updating drivers, etc.Is there a reason for the increase in 15ms and any other ways to help it go back down? Thanks for the help

:)

 

Ethernet connection ok (assigned IP, etc) but not even ping works

Hi,

LAN is connected, DHCP assigned and IP and can see activity on Ethernet Status window both directions.

Windows 10: Firewall is off, antivirus is off, no VPN, all Policies no active, nothing odd configured.

The basic ping from the computer (general error) or from outside to it (time out) fails.

What else can I check (I had network reset, all the ipconfig and netsh suggested steps done).

Looks like something really deep is miss-configured.

Thanks,

 

Device in the same local network pings but the other one not.

If you can ping one device (192.168.0.251) but not the other (192.168.0.252) from your Windows Server 2012 R2 machine, it indicates that there might be an issue with the network configuration or connectivity of the second device. Here are some troubleshooting steps you can follow:

1. Check Device Configuration:
   
   • Ensure that the device with IP address 192.168.0.252 is correctly configured with the subnet mask (usually 255.255.255.0) and gateway (192.168.0.1).
     
   • Verify that there are no IP conflicts. Make sure that no other device on the network is using the same IP address (192.168.0.252).
     
2. Physical Connectivity:
   
   • Check the physical connections between the server and the device. Ensure that the Ethernet cable is securely connected to both ends.
     
   • Inspect the device's Ethernet port and cable for any physical damage or loose connections.
     
3. Firewall and Security Software:
   
   • Disable any firewall or security software on the Windows Server temporarily to rule out any interference with ping requests.
     
4. ARP Cache:
   
   • Sometimes, ARP (Address Resolution Protocol) cache can cause issues. You can try flushing the ARP cache on the Windows Server using the following command:
     
     
   • This command will clear the ARP cache, and the server will re-discover devices on the network.
     
5. Packet Capture:
   
   • You can use packet capture tools like Wireshark to capture network traffic between the server and the device (192.168.0.252). This can help you identify if the ping requests are reaching the device and if the device is responding.
     
6. Device Logs:
   
   • Check the logs or diagnostic information on the device itself (192.168.0.252) for any errors or issues that might be preventing it from responding to ping requests.
     
7. Network Switch/Router:
   
   • If there is a network switch or router between the server and the devices, check its configuration for any access control or firewall rules that might be blocking traffic to 192.168.0.252.
     
8. IP Configuration Conflict:
   
   • Double-check that there are no IP address conflicts within the network. No other device should be using the same IP address (192.168.0.252).
     

By following these steps, you should be able to identify and resolve the issue preventing you from pinging the device with IP address 192.168.0.252 from your Windows Server. If the problem persists, please provide more details about the error message or any specific issues you encounter during these troubleshooting steps, and I'll be happy to provide further assistance.

 

High Ping Help!!!!

You can try pinging your router to see if ping is excessively high between your computer and it. If it is you may have a faulty Ethernet cable or interference on your wireless network.

Type the following in the command prompt.
Code: ping 192.168.1.1[/quote] You can also substitute IP addresses for various website URLs to see if you get varying pings from different websites.

Code: ping www.google.com[/quote] The "tracert" command is also very useful for discovering where the latency is occurring between you and a designated location.

for example:

Code: tracert www.speedtest.net[/quote] this will give you a list of the amount of time it takes for your data to travel between each device it encounters on its way to www.speedtest.net. This is called a "hop".

If you have a long hop between your modem and the servers at your ISP (look for a hop with your ISP's name somewhere in its name) followed by short hops when the data leaves your ISP's infastructure then you know the trouble is with your ISP and not with your equipment. If you have consistently high ping throughout all hops you could have a malware problem

Knowing where the excess lag is occurring is the first step to figuring out how to fix it.