RDC Client printer access from a Win2008 RDP session that then connects to a Win2003 RDP session
I'm working with a special need for a client that has a Windows 2008 Standard x64 Server (non R2).
They have an VFP application that does not work well on a 64bit server. We have setup a dedicated Win2003 Standard Server SP2 and installed the application there and it runs great.
The issue: Remote users remote the Win2008 server via terminal services. They run apps there and then launch a new RDP session from the Win2008 server session to the Win2003 server to run the VFP app. Their local HP P2035n client printer shows up properly as a session printer on the Win2008 RDP session, but does not then display on the second Win2003 RDP session. Unfortunately, they need to print from that app as well.
I've installed the updated HP printer drivers on the local PC, the Win2008 terminal server and the Win2003 terminal server. Other Microsoft engineers I have spoken with said it "should" work, but does not. There is no VPN between the remote site and the server, otherwise I'd directly map it from the server. Printers defined locally on the Win2008 server show up as session printers on the Win2003 server, just not the remote client printers.
I appreciate any other thoughts on how this might be able to work without having to setup a VPN between the remote networks.
They have an VFP application that does not work well on a 64bit server. We have setup a dedicated Win2003 Standard Server SP2 and installed the application there and it runs great.
The issue: Remote users remote the Win2008 server via terminal services. They run apps there and then launch a new RDP session from the Win2008 server session to the Win2003 server to run the VFP app. Their local HP P2035n client printer shows up properly as a session printer on the Win2008 RDP session, but does not then display on the second Win2003 RDP session. Unfortunately, they need to print from that app as well.
I've installed the updated HP printer drivers on the local PC, the Win2008 terminal server and the Win2003 terminal server. Other Microsoft engineers I have spoken with said it "should" work, but does not. There is no VPN between the remote site and the server, otherwise I'd directly map it from the server. Printers defined locally on the Win2008 server show up as session printers on the Win2003 server, just not the remote client printers.
I appreciate any other thoughts on how this might be able to work without having to setup a VPN between the remote networks.
TechnicallyMaybe
I've never heard of printers being autocreated in a nested config. Te resolution is to have the users connect to the 2003 server from their local workstations.
ASKER
I have been able to get a HP P1006 to autocreate on the Win2008 server and then the Win2003 server, but not the HP P2025n.
Setting up 2 separate RDP connections from the client PC was a thought, but didn't work well for the clients need. If there is a low cost VPN client solution we could implement, we might be willing to try that if this is found to not be possible.
Setting up 2 separate RDP connections from the client PC was a thought, but didn't work well for the clients need. If there is a low cost VPN client solution we could implement, we might be willing to try that if this is found to not be possible.
Does the P2025n autocreate if you connect directly to the server? Because it may be an issue with 2003 not having a driver for that model.
ASKER
The P2035n autocreates in a Win2003 RDP session run directly from the Win2008 server just fine from a driver installed locally on the Win2008 server. But when a user (or admin) establishes a RDP session on the Win2008 server they get their autocreated session printer.from the driver that is installed on their remote PC, but does not create a new printer session on the Win2003 RDP session.
Is this a shared printer you could just install on the 2003 server and they can print to it instead of relying on an autocreated printer?
ASKER
No, the printer is not shared at the remote client location, but it could be quite easily. If it was, how would the server get access to the network share on the remote local network if there is no VPN in place between the two networks??? The server would not have access to any remote resources even though there is a RDP session between the client workstation and the Server. This is why I need terminal services to create the remote printer session. If there is a tool that allows for creation of remote printers, I am not aware of it. I found a link that talks about a Microsoft Printer redirection tool, but not sure if it will work for what I am trying to do. http://www.microsoft.com/downloads/details.aspx?FamilyId=9AD27BE9-40DB-484F-862E-38A094EEEAF7&displaylang=en
I am planning to dl it and see what the tool can do however and will update tomorrow.
I am planning to dl it and see what the tool can do however and will update tomorrow.
I am going to fall back on my first suggestion which is to initiate both from the client. An RDP connection through an RDP connection is a little awkward anyway. That particular printer model seems to not want to place nice when hopping onto the second server.
ASKER
Not an acceptable answer to run two RDP sessions from the client PC. Then I would need to change the listening port on the 2nd terminal server and also forward the port on the router which is already at it's max forward list. If you don't know a good solution, no need to continue with guess work. I've done enough of that myself. I'm looking for a person to answer that may have done this already or have a good solution to do what I am trying to do. If I don't get a solution here, I may open up a ticket with Microsoft directly, just didn't want to go that route first. Thx for your thoughts though.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.