I've spent the last few days racking my brain over this one, but here goes. We're running Windows Server 2003, Enterprise edition at work.
I installed a printer on Friday morning, Nashuatec DSM730 - printer / photocopier to the network, with no problems - as DNS / DHCP was enabled the printer was allocated it's IP Address and it was a simple process to set up users workstations (Windows XP Pro) TCP/IP setting / connecting to the printer / copier.
Anyway - I got a phone call in the afternoon that another Nashuatec, which was installed many months ago / connected to the network (On the 2nd floor of the building and working fine had stopped printing.
When I checked the printer and the user terminals, the IP address on the printer had changed (just the last two digits) and was different to what was being shown on the terminal computers.
I have tried amending the IP address on the user terminals, as well as deleting the old printer / settings from the PC, but the printer is failing to print. It is showing as connected and 'ready' in the printers and faxes window, but is failing to printe - with a connection time out error.
I have linked a PC on the 2nd floor to the new printer i have installed and this has worked fine. However, yesterday morning when the staff returned to work, the IP address had been changed (just the last to digits).
I have accessed the printers IP / Network settings / having turned off / unplugged the printer from the network initially, the Auto DNS / DHCP is set, so the printer is picking up an IP address. However, when I click 'test connection' - the printer is saying there is no connection to the server.
I'm a novice to networking, and was wondering if there was anyway I can check - server side why it is not picking up the printer.
I'm also aware that the problem may lie with the printer, as I've explained that the printer is not connecting to the server.
I must also state, that i have not amended or changed any of the settings on this printer. The weird thing is, that the printer is picking up an IP address allocated to it, but doesn't appear to be communicating to the server or vice versa. Not sure why it's stopped working all of a sudden and why they are not talking to each other.
Your help will greatly be appreciated.
Free Guide: Managing storage for virtual environments
Complete a brief survey to get a complimentary 70-page whitepaper featuring the best methods and solutions for your virtual environment, as well as hypervisor-specific management advice from TechTarget experts. Don’t miss out on this exclusive content!