First Post!
by Maarten Goldstein, Mar 11, 2007 4:05pm PDTWhoever smashed in my passenger seat window and stole my satnav equipment, thanks a lot. I had a great time tonight getting it repaired. Argh. Movie: I want what all men want, I just want it more.
Nintendo kicks off 'Crowdfarter' promo for Game & Wario
Narco Terror announced from Deep Silver
Call of Duty: Ghosts teaser gives tenuous look at next-gen COD
OZombie will be Spicy Horse's take on Oz
Deadpool listed for Wii U on Amazon Canada
CastleStorm assaulting XBLA next week
Leisure Suit Larry HD delayed until late June
Rhode Island looking to sell Amalur intellectual property
Resident Evil: Revelations DLC coming throughout June
Seeing Red: A History of the Xbox 360's Red Ring of Death



Now they use the new version of RDP and their printer is a Network Printer. That is to say, it is using a standard TCP/IP port and isn't connected over an SMB share. This printer never adds itself when connected to the remote client. Sometimes, and only sometimes, I can setup a local printer on the remote machine and then change the port to the proper TS port. However, quite often the port changes on connect or it just stays as inactive.
Any suggestions on how to make this work consistently or an idea for a work around? They had been told in the past that "it can't be done" but somehow it was working fine previously. However, we had to redo their network and their PCs and now it is being stupid.
Thread Truncated. Click to see all 10 replies.
In your case it sounds like there's some problem with this, but perhaps try mapping it off another PC smb share?
You must be logged in to post.