Bad Pings from Windows, Good from Linux
-
@scottalanmiller said in Bad Pings from Windows, Good from Linux:
@notverypunny said in Bad Pings from Windows, Good from Linux:
I assume that physical cables and connections have been checked / swapped / ruled out?
Same ones as the pings that work. So physically connections are ruled out.
Actually - I wouldn't be so quick there.
I had a situation 20 years ago where a Windows server would print OK to a printer, but as AS/400 refused to.
Turned out the cable on the printer was less than good. Windows could handle the latency of the traffic to the printer, the AS/400 could not.
-
@notverypunny said in Bad Pings from Windows, Good from Linux:
@scottalanmiller said in Bad Pings from Windows, Good from Linux:
@notverypunny said in Bad Pings from Windows, Good from Linux:
Cloned VMs? P2V? Restored / Replicated VMs
I believe that this is the case, but the old ones are definitely powered down.
Hmmmm.... if they're powered down and not unplugged with WoL enabled?
How does that work for VMs?
And this wouldn't explain the PCs having the same issue.
-
Do the Windows PCs print direct or through a Windows print server?
-
@Dashrender said in Bad Pings from Windows, Good from Linux:
Do the Windows PCs print direct or through a Windows print server?
Neither. IOGear
-
@Dashrender said in Bad Pings from Windows, Good from Linux:
@notverypunny said in Bad Pings from Windows, Good from Linux:
@scottalanmiller said in Bad Pings from Windows, Good from Linux:
@notverypunny said in Bad Pings from Windows, Good from Linux:
Cloned VMs? P2V? Restored / Replicated VMs
I believe that this is the case, but the old ones are definitely powered down.
Hmmmm.... if they're powered down and not unplugged with WoL enabled?
How does that work for VMs?
And this wouldn't explain the PCs having the same issue.
Was thinking P2V. If the VM kept the MAC from the source physical box and the source box is still plugged it but has WoL enabled the MAC will be on the network 2x, right?
I'll concede the point about the PCs...... Although it's not impossible that depending on the size of the organization, the P2V source could have been repurposed as an endpoint, or the NIC been salvaged and put into service in a desktop.
A quick scan with nmap or advanced ip scanner and sort the results by MAC to see if there's anything funky going on.
I've had a couple of machines with Asus boards and Intel NICs blank the MAC to all 0s. Strangely they kept on working and no conflicts since they weren't on the same L2 but it's something that can happen. Not just Asus boards either, I had found the fix on an MSI site or forum if my memory is correct.
-
@scottalanmiller said in Bad Pings from Windows, Good from Linux:
@Dashrender said in Bad Pings from Windows, Good from Linux:
Do the Windows PCs print direct or through a Windows print server?
Neither. IOGear
So the Windows client print direct to the IOGear, I assume because the printer itself doesn't have a built in network stack.
so - direct.
-
Start at Layer-1. Either check the cabling or replace the cabling to the IoGear print server. I have seen more times than I care to count weird inconsistent network connectivity to a device (one computer on network can ping it, a second cannot) fixed by simply replacing the cable.
-
@Dashrender said in Bad Pings from Windows, Good from Linux:
@scottalanmiller said in Bad Pings from Windows, Good from Linux:
@Dashrender said in Bad Pings from Windows, Good from Linux:
Do the Windows PCs print direct or through a Windows print server?
Neither. IOGear
So the Windows client print direct to the IOGear, I assume because the printer itself doesn't have a built in network stack.
so - direct.
If that's "direct", what isn't direct?
-
@scottalanmiller said in Bad Pings from Windows, Good from Linux:
@Dashrender said in Bad Pings from Windows, Good from Linux:
@scottalanmiller said in Bad Pings from Windows, Good from Linux:
@Dashrender said in Bad Pings from Windows, Good from Linux:
Do the Windows PCs print direct or through a Windows print server?
Neither. IOGear
So the Windows client print direct to the IOGear, I assume because the printer itself doesn't have a built in network stack.
so - direct.
If that's "direct", what isn't direct?
This is as direct as you can get in this scenario.
If it’s not obvious by now the entire point of my question was to determine if there was a print server between the windows client and the network stack handling traffic on behalf of the printing device.
For example if you were using a Windows print server then all the problems would likely be purely from the VM server and not really related to the windows client. -
Check in the Networking stack on the Windows systems and see if Flow Control is enabled (Rx & Tx Enabled). If it is, disable it.
How old is this IOGear device? Could it be a bug in the IOGear's firmware that dislikes (recent changes to) Windows? ...I mean we know Microsoft never breaks printing, right?
Check one of those Physical Windows boxes that's having a problem printing to it, and boot it from a Ubuntu / Fedora / Whatever Live ISO and see if you still have the ping issue.
-
@dafyre said in Bad Pings from Windows, Good from Linux:
How old is this IOGear device? Could it be a bug in the IOGear's firmware that dislikes (recent changes to) Windows? ...I mean we know Microsoft never breaks printing, right?
:face_with_tears_of_joy:
