How do I redirect a RDP printer?

If you’re looking to redirect a RDP printer, there are a few things you’ll need to do. First, make sure that the printer is shared on the network. Next, open up the Remote Desktop Connection tool and enter in the IP address or hostname of the computer you want to connect to. Once connected, click on “Local Resources” and then “Printers”. From here, you should see your shared printer listed - simply select it and hit “OK”. Your RDP printer should now be redirected!

If you’re connected to a VPN and want to print on a local printer, you need to make your device visible on the local network. To do this, go to your VPN settings and look for the option to make your device visible on local networks.

It’s a common issue that printers go offline when connecting to a VPN (Virtual Private Network). The main causes are:

1. Incorrect printer settings: when you set up a printer, it’s important to make sure that the “use printer offline” option is unchecked. This setting can be found in theAdvanced tab under Printer Properties (in Windows) or in the Print & Scan Preferences (on a Mac). If this option is checked, it means that your computer is trying to use the printer while the VPN connection is active, which obviously won’t work!
2. IP address conflict: another possibility is that your computer and the printer are assigned different IP addresses when they’re connected to the VPN. This can happen if you’re using a public VPN service instead of one provided by your company. In this case, you’ll need to contact your VPN provider for help resolving the issue.
3. Firewall issues: finally, it’s possible that there’s a problem with your firewall settings. If you’re using a third-party firewall, make sure that it’s configured to allow traffic on port 9100 (which is used for printing). Alternatively, you can try temporarily disabling your firewall to see if that fixes the problem.

If you’re having trouble RDPing over your VPN, there are a few things you can check. Make sure that the NSG allows port 3389 for the VM you’re trying to RDP to, and that it also has the Vnet address range allowed. This issue can also occur if the VPN client doesn’t get the routes from Azure VPN gateway. The gateway should contain your Vnet address range and the P2S VPN address range.

The long answer is that it depends on how you set up your RDP connection and how your VPN is configured. By default, both RDP and VPN use strong encryption methods. However, there are some key differences between the two that can impact security:

RDP connections are typically initiated from a user’s PC, while VPNs can be initiated from anywhere. This means that if your PC is compromised, an attacker could potentially access your RDP session without needing to first connect to your VPN.

RDP sessions are often allowed through corporate firewall rules, while VPN connections may be more restricted. This means that an attacker with access to your company’s network could potentially intercept and eavesdrop on your RDP session data.

VPNs encrypt all traffic passing through them, while RDP only encrypts the initial login information. This means that once an attacker has access to your RPD session, they can sniff out any unencrypted data passing through it - including passwords and sensitive files.

Overall, both RDP and VPN connections can be quite secure if properly configured. However, due to the differences in their implementation, VPNs may provide slightly better security in certain situations.