Tip: Run a free scan for common Windows errors ad

re: VPN Client gets error 733 to server 2003 and RDP not working Monday, January 16, 2006 at 6:36 am Posted by Curt R (773 messages posted) No, you don't need to make it a DC in either case. I have my router port forwarding RDP sessions to my XP Pro PC and it works wonderfully. Check the documentation on your router regarding port forwarding and ensure you have it setup correctly. On Friday, January 13, 2006 at 10:58 am, Mike wrote: >I have server 2003, netgear router, and all ports forwarded to "file server" (not >domain controller) of ports 1723, 47, and 3389. I can't get vpn to login correctly >nor remote desktop via terminal services. Do I need to make this server a domain >controller to allow vpn or rdp? Is netgear known for not allowing vpn? [Reply or follow-up to this message] Tip: Use one of the [Reply or follow-up to this message] links above to add a message to this thread Search this forum Start a new thread on a different subject Report abuse of the forum Return to the Windows Server 2003 Discussion Forum