Question : Terminal Server 2008 printer redirection failure

Please help! I have a Windows Server 2008 terminal server, with printer redirection working perfectly for the last year for 10 users. The printer redirection has stopped working for all users. Have checked (and rechecked) the following ...
- RDP client has Printer checked under Local Resources tab
- Terminal Services Configuration/RDP-Tcp connection/Client Settings tab Windows Printer unchecked (not disabled)
- Group Policy on the SBS 2003 domain controller (Computer Configuration/Admin Templates/Windows Comp/Terminal Services/ClientServer data redirection) - all items Not configured
- Local Group Policy on the terminal server (Computer Configuration/Admin Templates/Windows Components/Terminal Services/Terminal Server/Printer Redirection) - all items not configured
- Event logs (system & application) not indicating any problems
The problem may have been triggered by installation then removal of vSpace software for NComputing L230 thin client.

Answer : Terminal Server 2008 printer redirection failure

--I have requirement to put my servers which are housed locally into a remote datacenter.

Typical scenario

--I am thinking of possible wan connection type it will be 100 mbs ethernet private leased line connecting to the datacenter.

Some type of Metro Optical Ethernet will meed your requirements.


--1) As there is no actual routing involved in the remote site. Put a switch out in the remote site. Create a 802.1 q trunk link from my asa to the switch in the remote site.Connecting one end of the 100 mbs to the asa another end to the switch.  Will this work switching over the wan connection? What would be disadvantages doing it this?

Yes this will work, if you go with a MOE type service, you will need to order the circuit with the capability of QinQ (this is needed as most providers are already using dot1q in their infrastructure) service if you plan to trunk the circuit from the data center to your office. I can not think of any disadvantages, only that the design and implementation required to meet your requirements; do you plan to keep these servers in the same subnet as they are now (you will not need to trunk in this case, if you have a switch at the office that has the capability of trunking [802.1q] then you can just connect
the P2P Ethernet link (MOE) to the switchport of the switch and configure it as an access port in the same vlan as the rest of your network), or do you plan to create a new security zone and new subnet between the data center and office (Highly recommended); this will allow you to segment the network [broadcast containment] and add ACLs for your companies security requirements (if any). Depending on how your current infrastructure is configured, you might need additional configurations to accommodate the new changes. What you are asking is completely doable, you just need to ensure you design the environment to be scalable.


**QinQ information:
http://lastmilefiber.net/Powerpoint_-_MOE_presentation.pdf
MOE – Traffic Partition Capability

Good Luck
Billy
Random Solutions  
 
programming4us programming4us