I have a client that moved a Savin MP2352 from the office to his home so he could print documents locally while in RD. Initially when the printer company moved the printer they did not change the IP address on the old printer and gave the same IP to the new office printer (MP3054) that replaced it at the office. When the client tried to print to his local (home) printer in RD it would print to the new printer at the office. I changed the IP to one that was not being used at either location, had the SonicWall tech verify there was nothing in the firewall or VPN settings that would prevent printing. Yet, when I tried to print a test page to the local printer it still printed out to another printer in the remote location( office). It does not give any notification of an error. The home is on Verizon FIOS and from my understanding would require an additional router to create a subnet. Not too big of a deal but since the client set up all home users to print to the MP2352 it would mean all devices would have to be changed to the subnet He is willing to go that route should it be needed. My concern is that considering the printer is using a different IP and still having the same issue, subnetting would not solve the problem. Any insight would be helpful.
Software/Hardware used: Windows Server 2008 R2, Windows 7, Remote Desktop
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!