andrewgymsource
asked on
VPN and MS2k Terminal Server don't mix
In a sleepy haze, I selected “Disable Routing and Remote Access” instead of just “All Tasks > Restart” and ever since then, I’ve had a problem.
The Server is running Terminal Server and now when I start the VPN, Terminal Server is un-ping-able. When I Stop the VPN process, Terminal Server is available again.
None of the outside networking was changed so I have to believe it’s an internal problem with the server settings. I’ve modified the In/Out Filters to include UDP Ports 3389, 50 and 51 just in case.
So the question is what have I done wrong?
The Server is running Terminal Server and now when I start the VPN, Terminal Server is un-ping-able. When I Stop the VPN process, Terminal Server is available again.
None of the outside networking was changed so I have to believe it’s an internal problem with the server settings. I’ve modified the In/Out Filters to include UDP Ports 3389, 50 and 51 just in case.
So the question is what have I done wrong?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
One more bit of additional information – when I remove all the entries in both Inbound and Outbound filters within the VPN settings, both the Terminal Server and the VPN can be up at the same time.