When my laptop is on WiFi, I can print & ping our printers: > $ ping 10.250.0.119 > PING 10.250.0.119 (10.250.0.119) 56(84) bytes of data. > 64 bytes from 10.250.0.119: icmp_req=1 ttl=255 time=2.02 ms > 64 bytes from 10.250.0.119: icmp_req=2 ttl=255 time=1.17 ms BUT when I plug it into ethernet (and disable wifi, for good measure), I can no longer reach the printers: > $ ping 10.250.0.119 > PING 10.250.0.119 (10.250.0.119) 56(84) bytes of data. > [...nothing happens] (I'm using Nostromo (IP address 10.250.0.119) as an example.) This affects my desktop machine as well which is ethernet-only (no WiFi), so it's completely unable to print. I'm assuming this is a network-segmentation sort of issue...?
For reference, when my laptop is connected over WiFi, it gets assigned this IP: 10.250.7.235 and when it's connected over ethernet, it gets assigned this IP: 10.250.34.187
What port are you plugging into? That ip is on the wrong vlan.
I'm plugged into a switch, which is plugged into a blue port under my desk, labeled Loc 3.2105
(My desk is # 3013, near Very Good Very Mighty.)
Do you have anything else plugged into this switch?
My phone is plugged into the other jack -- the black one (but not into the switch). The switch has 2 desktops and 1 laptop connected to it.
Can you try switching the phone and switch? Black is the primary port and blue is generally for voice.
Ah, good to know. Thanks! I just left the office, actually, and I won't be back until next week. I'll give that a try when I'm back.
Looked at the config on the switch. Both of your desk ports are on voip which wouldn't have caused you any problems until you went to print. I can change one to corp, but I don't want to drop any sessions you might have going on the desktop so I will wait until you are ready to drop them.
No need to change the ports at this point until you move desks.
Thanks! I don't have any active sessions on that box, so whenever it's convenient for you, please go ahead and change the blue one to corp. (Or it can wait until next week, too; I don't expect to be printing while I'm away :))
This port was moved over to corp.
Verified fixed -- "ping 10.250.0.119" now succeeds on my desktop machine. Thanks!