When I setup my Versalink 400 series (C405) printer (ethernet cable connection, no WiFi) it automatically connected to my domain through the address of a virtual machine on our network. I've recently rebooted the VM and now I can't print. Shouldn't the printer have connected to workstations through the network using the printer's own IPv4 address instead of some random virtual machine?
Here's what happened. When I ran the initial setup for the 405n printer it chose an IP address for itself, and connected to our network. I also entered the credentials to connect to our server so I can scan to a directory on our network. The Configuration Report, DNS section identifies our Domain Name and under IPv4 it says that DHCP is enabled and it identifies the correct IP address for our server.
But when I installed Xerox SmartStart software on a workstation it identified the printer by the IP address that belongs to one of our virtual Windows machines. After installation, Xerox Print & Scan recognizes the correct IPv4 address for the printer but it names it by the network name of the virtual machine, and specifies the virtual machine's TCP/IP Address.
Fast forward to today, two months later, and I've had to reboot the virtual machine. And suddenly I cannot print. But I can scan.
Does anyone know what's going on? I don't understand why the printer even needs to identify with a network machine, after all it's got its own IPv4 address.
Thanks!
