Guest nl Posted September 6, 2008 Posted September 6, 2008 We have an old server sbs win2k; it has it's own domain. We have a 2003 server with it's own domain. When remoting desktop from home, after typing IP address it goes to the new server. How can I connect directly to the old server from home? Still be able to keep connecting to the new one also. thank you. Nereida
Guest Pegasus \(MVP\) Posted September 6, 2008 Posted September 6, 2008 Re: Terminal Services-Remote Desktop "nl" <nl@discussions.microsoft.com> wrote in message news:757BA834-215E-4ADE-A65C-B8052D37B6FF@microsoft.com... > We have an old server sbs win2k; it has it's own domain. We have a 2003 > server with it's own domain. > When remoting desktop from home, after typing IP address it goes to the > new > server. How can I connect directly to the old server from home? Still be > able to keep connecting to the new one also. > > thank you. > > Nereida It depends. If you're doing it via a VPN then you need to specify the old server's internal IP address when starting the session. If you're doing it directly then you need to change the old servers TS port from its default value of 3389 to something else, e.g. 3390. You must then create a rule in your router to forward port 3390 packets to your old server. You must also specify port 3390 when starting the RDP session.
Guest Lanwench [MVP - Exchange] Posted September 6, 2008 Posted September 6, 2008 Re: Terminal Services-Remote Desktop nl <nl@discussions.microsoft.com> wrote: > We have an old server sbs win2k; it has it's own domain. We have a > 2003 server with it's own domain. > When remoting desktop from home, after typing IP address it goes to > the new server. How can I connect directly to the old server from > home? Still be able to keep connecting to the new one also. > > thank you. > > Nereida If you have only one public IP (or a perimeter firewall/router that can't accept multiple IPs on its WAN interface(s)) then you will need to use something like VPN to connect to both remotely, as Pegasus suggested. Otherwise you can set up multiple public IPs and public hostnames and firewall rules, so that server.company1.com goes to the SBS box and server.company2.com goes to the W2003 DC. What's the reason you have two domains? If this is a situation where two companies are sharing an internet connection, you should segregate them with a router - and get multiple public IPs.
Guest nl Posted September 8, 2008 Posted September 8, 2008 Re: Terminal Services-Remote Desktop How can I tell if our firewall can accept multiple ips? "Lanwench [MVP - Exchange]" wrote: > nl <nl@discussions.microsoft.com> wrote: > > We have an old server sbs win2k; it has it's own domain. We have a > > 2003 server with it's own domain. > > When remoting desktop from home, after typing IP address it goes to > > the new server. How can I connect directly to the old server from > > home? Still be able to keep connecting to the new one also. > > > > thank you. > > > > Nereida > > If you have only one public IP (or a perimeter firewall/router that can't > accept multiple IPs on its WAN interface(s)) then you will need to use > something like VPN to connect to both remotely, as Pegasus suggested. > > Otherwise you can set up multiple public IPs and public hostnames and > firewall rules, so that server.company1.com goes to the SBS box and > server.company2.com goes to the W2003 DC. > > What's the reason you have two domains? If this is a situation where two > companies are sharing an internet connection, you should segregate them with > a router - and get multiple public IPs. > > >
Guest Lanwench [MVP - Exchange] Posted September 8, 2008 Posted September 8, 2008 Re: Terminal Services-Remote Desktop nl <nl@discussions.microsoft.com> wrote: > How can I tell if our firewall can accept multiple ips? You could look at the documentation or contact the manufacturer's support. Note that consumer-grade kit rarely permits this. > > "Lanwench [MVP - Exchange]" wrote: > >> nl <nl@discussions.microsoft.com> wrote: >>> We have an old server sbs win2k; it has it's own domain. We have a >>> 2003 server with it's own domain. >>> When remoting desktop from home, after typing IP address it goes to >>> the new server. How can I connect directly to the old server from >>> home? Still be able to keep connecting to the new one also. >>> >>> thank you. >>> >>> Nereida >> >> If you have only one public IP (or a perimeter firewall/router that >> can't accept multiple IPs on its WAN interface(s)) then you will >> need to use something like VPN to connect to both remotely, as >> Pegasus suggested. >> >> Otherwise you can set up multiple public IPs and public hostnames and >> firewall rules, so that server.company1.com goes to the SBS box and >> server.company2.com goes to the W2003 DC. >> >> What's the reason you have two domains? If this is a situation where >> two companies are sharing an internet connection, you should >> segregate them with a router - and get multiple public IPs.
Recommended Posts