Server configure for remote desktop

Microsoft Windows server 2003
January 25, 2010 at 23:51:44
Specs: Windows Vista, Xeon Server
Dear all,

I have
1. windows 2003 server with Teminal Server
2. Modem with Broadband Connection
3. Linksys Router
4. Registered IP, Gateway,

What i need.

1. I wanted to configure my server for Remote Desktop over WAN with
registered IP. (212.101.xx.xxx)
Subnet Mask (255.255.255.248)
Default Gateway ( 212.101.xx.xxx)
DNS (212.101.0.10)


Please let me know what i do specific changes on my modem and Router/

Awaiting your response at the earliest.



See More: Server configure for remote desktop

Report •

#1
January 26, 2010 at 05:58:22
Posting your entire external IP is not a good idea. I edited it for you.

As to your question, you have to enable RDC on the receiving end. On your server open your System Properties and click on the Remote tab. Put a check in the box beside, "allow users to connect remotely to this computer"

You will have to setup a "port forward" in your router. You'll want to forward port 3389 (RDC) to the internal IP of your server.


Report •

#2
January 26, 2010 at 07:24:19
First up all, thanks for your reply.

My problem is not to activate remote desktop access.. That all i did it.

My problem is how i configure router to communicate with server. My ISP given me one default gateway. so if i connect server through router, what ip i must give to router. is it necessary to specify Statit ip on router, so and so.


Report •

#3
January 26, 2010 at 07:36:38
As I said, you'll have to create a port forward on your router. You will want to forward port 3389 to the IP of your server.

Example:

Server IP = 192.168.0.1

In your router's management interface, find the "port forward" section and create a forward that looks like the following:

Forward port 3389 to IP 192.168.0.1

To connect from a remote PC you will need to know your external IP address. You can find this (if you don't already know it) by opening a web browser on your server and then google "what's my IP" and go to the link provided.


Report •

Related Solutions

#4
January 26, 2010 at 08:31:39
Dear Curt,

Yes i will give u exact scenario once again.

For me no need to fine "what is my IP". As i told u before, i have registered (dedicated) IP with me for my server. I wanted my router to configure to pass the request to my server.

On my server NIC i specified everything.
IP : 212.101.x.x, Sub : 255.255.255.248, Def Gate: 212.101.y.y and DNS

This means the IP of my router must be 212.101.y.y

then only i can make port forward to 212.102.x.x.
if i keep router ip with 192.168.1.1, then how i can configure port forward to my server static registered ip.

I hope now u understood my problem.

So please give me a description, what all configuration must be done on router.

Thanks


Report •

#5
January 26, 2010 at 09:13:11
Ok you're actually managing to confuse me.

Typical setup is as follows:

Internet >> SOHO Router >> Clients/Servers

Note, most SOHO Routers have 4 LAN ports. If you have more than 4 clients/servers then you need to add a switch and it looks as follows:


Internet >> SOHO Router >> Switch >> Clients/Servers

Once you have your router plugged in, you need to open a web browser and connect to it's management interface by putting the routers default IP address in the URL field of the browser.

Once connected, you'll have to login. Login and IP details will be in the setup guide.

Once logged in, go to the WAN setup and put your static IP settings, as provided by your ISP, into the WAN side of the router.

Then you should be able to connect to the internet.

If that's working, then you're ready to do the port forward.

First a couple details. In the case of a server, you should always use a static IP so it can never change. Most SOHO routers by default have a DHCP scope of 100 to 199 so choose an IP for your server that is not in that range. I would use something like .10 myself

ex:
Router IP = 192.168.0.1
DHCP Scope = 192.168.0.100 to 192.168.0.199

Give your server: 192.168.0.10 with Gateway IP: 192.168.0.1 (the router is the gateway).

Once your server has it's IP statically assigned and it's communicating on the internet properly you will want to create your port forward.

Again, connected to the router's management interface find the port forward section and setup a port forward. As I said previously (using the example IP I just mentioned above) the forward would look as follows:

Forward Port 3389 to 192.168.0.10

Once you have your server setup to allow RDC sessions to connect to it, you should then be able to connect remotely using RDC on whatever laptop/PC you're using at that moment in time.


Report •

#6
January 26, 2010 at 09:19:58
"IP with me for my server. I wanted my router to configure to pass the request to my server."

You misunderstand routing. It does not work like this. You can no assign a static public ip to your server yet have a router between the internet and your server.

That static ip goes on your routers wan port.
You use private ip for the server like 192.168.1.10 with the router at 192.168.1.1 for example


Report •

#7
January 26, 2010 at 09:38:21
Dear Curt,

Thanks a lot, you spent lots of time answering me.

Still i didn't got proper reply from u.

U said

Give your server: 192.168.0.10 with Gateway IP: 192.168.0.1 (the router is the gateway).

No problem for me to configure this.

But the scenario is different here.

I wanted to give my Server IP <b(212.101.1x.13x)> and Default Gateway (212.101.1x.13x)...

Did u got me??
Like STC(212.145.52.138) server


Report •

#8
January 26, 2010 at 09:41:16
Dear Curt,

Thanks a lot, you spent lots of time answering me.

Still i didn't got proper reply from u.

U said

Give your server: 192.168.0.10 with Gateway IP: 192.168.0.1 (the router is the gateway).


No problem for me to configure this.

But the scenario is different here.

I wanted to give my Server IP (212.101.1x.13x) and Default Gateway (212.101.1x.13x)... which i purchased from ISP to access my server from anywhere in the world..

Did u got me??
Like STC(212.145.52.138) , yahoo(217.45.85.142) servers


Report •

#9
January 26, 2010 at 10:01:57
niyassulaiman
then just connect the server to the modem with no router.

sure hope you don't do any financial stuff on this server :-)


Report •

#10
January 26, 2010 at 10:05:27
hello wanderer.

no my friend. i can't do it direct. coz its going to be our company file server.

I wanted to set up behind router.

Please give me how i can.. or help me to find any reference.


Report •

#11
January 26, 2010 at 10:45:47
Your thinking is going in circles.

You want the public ip on the server but you want it behind a router which also has to have a public ip. But being behind a router makes the servers ip private not public no matter what ip it is.

You have already been told in great detail how to do this.

internet modem<>public ip on router wan interface[router]<>lan containing server/pcs.

The public ip does not go on the server. You use port forwarding to forward services from the internet to your server thru the router.

You need to understand that given your example of
yahoo(217.45.85.142) servers that 217.45.85.142 is not a server. Yahoo has 1000's of servers.


Report •

#12
January 26, 2010 at 13:57:46
You could use a public, routable IP address behind your router/firewall but why bother? This could lead to some some issues I won't bother getting into for now.

What I detailed is the correct way to do this using Private nonroutable IP's and NAT. This is how 90+ % of companies do their networking.

Those IP's I listed in my detailed explanation on how to set this up were examples. What you should use depends entirely on you and what the LAN side of your router is set to use.

You responded to my last post with:

I wanted to give my Server IP (212.101.1x.13x) and Default Gateway (212.101.1x.13x)... which i purchased from ISP to access my server from anywhere in the world..

This is your external IP address (as provided by your ISP). As I pointed out before, as wanderer just pointed out, these TCP/IP settings need to be applied to the external (WAN) side of your router, not on the server's interface.

If you use Private IP addresses internally (ie: on the LAN side of your router) then the router itself will use NAT to ensure internet connectivity for all internal clients. It will also allow you to port forward incoming traffic so you can remote in to your server.

I suspect the real issue here is you lack knowledge, skill and experience in the networking area and I highly recommend you hire a skilled consultant to set you up if you want it done correctly.

I don't say this to disparage or insult you. I'm simply stating what I see to be fact and am indeed trying to help you out.


Report •

#13
January 27, 2010 at 02:43:44
Dear Curt and Wanderer,

I decided to connect the server to the modem with no router. and apply firewall on my server.

then tell me which is good modem to connect internet directly to my server.

Thanks for all you replies and help


Report •

#14
January 27, 2010 at 02:50:43
Dear Curt and Wanderer,

I decided to connect the server to the modem with no router. and apply firewall on my server.

then tell me which is good modem to connect internet directly to my server.

I have a Linksys Wireless-N ADSL+2 Gateway.. Here agian the problem is publich ip of my server. so please tell me which model Broadband modem have ethernet port .

Thanks for all you replies and help


Report •

#15
January 27, 2010 at 03:08:47
Also i have one Netopia 3346NEU-ENT ASDL Gateway

how about this one.


Report •

#16
January 27, 2010 at 05:15:29
You really need to hire a professional to come set this up for you.

Report •

#17
January 27, 2010 at 06:27:13
Hello Curt,

Please click the link below. so u can see my router details.

Please tell me where i can find the External (WAN) IP SIDE??

http://www.linksysbycisco.com/US/en/products/WRT160N

or if this product is not ok, please tell me which one i use?


Report •

#18
January 27, 2010 at 07:43:38
I've never used that particular router but if you connect to the management interface and just look through all the configurable settings I feel confident you will find it.

Report •

Ask Question