03-10-2016 09:23 AM - edited 03-08-2019 04:55 AM
Hi,
I have a printer that shows offline depending on which xenapp server you use. From one xenapp server the printer shows online and can be reached via ping but the other shows it offline and can't ping it. The two xenapp servers are in the same subnet with consecutive IP addresses.
From the server showing offline I ran a tracert and it dies after the serial port on the remote site's ASA. From the other server, the tracert completes.
From the server showing offline, I can ping every other IP (some with a lower and higher IP) except this printer. I can ping the target printer from every other server in different subnets as well.
No ACLs are set to block this specific IP or the target xenserver IP.
Anyone seen this before or have an idea of what to check next? I'd like to avoid re-IPing the printer.
Thanks!
Solved! Go to Solution.
03-10-2016 09:37 AM
1. Verify that the gateway and mask are also properly set up on that printer.
2. Take the printer offline, and verify that you don't have anything else at that IP address
(it should be unreachable if the printer is disconnected/off, unless you have a duplicate IP somewhere).
03-10-2016 09:37 AM
1. Verify that the gateway and mask are also properly set up on that printer.
2. Take the printer offline, and verify that you don't have anything else at that IP address
(it should be unreachable if the printer is disconnected/off, unless you have a duplicate IP somewhere).
03-10-2016 12:18 PM
Gateway and mask are setup correctly.
Taking printer offline made it unreachable from all servers.
All servers except for this one xenserver can ping the printer and all other IPs on the target subnet are pingable from the xenserver.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide