Routing question

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

Hi,

I've set the IP to windows server 2003 PC from private range 10.0.0.10 I've also set its gateway to IP of the router 192.168.1.1 then I enabled Routing and Remote access where I set static route IP 10.0.0.0, 255.0.0.0 => 192.168.1.1
My routing table is looking like this now:



Is actually ever gonna work like this? Basically I would like to test it if I can run the PC with different IP than router.

 

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

tbh i don't know about how the RRAS works, but i think you would need an interface which is connected to the 192.168.1.0 network.

Basically, a 10.0.0.10 interface cannot use a DG of 192.168.1.0.

 

You need to have two nics, one with the 192.168.x.x address, the other with the 10.x.x.x address. On each workstation connecting to the 10.x.x.x network you would then use the 10.x.x.x address of the server as the default gateway, you wouldn't need to set a gateway on that particular NIC (server) because the default gateway would be set as the 192.168.x.x of the router on the secondary NIC. It would sort out the routing of all traffic that way.

E.G

10.0.0.11 (workstation) would have the DG as 10.0.0.10 (server with two nics), any traffic for any other network except 10.0.0.0 would then go to 10.0.0.10 for a route beyond that network. 10.0.0.10 would look at it's routing table and see that 192.168.1.10 has the default gateway sat as 192.168.1.1 and direct all traffic out through that NIC>

 

Thank you very good explanation ;).

Edit:

I've just tested and it's still not working do I have to add some route apart from that are existing at the moment?

Settings:

Server

NIC1
IP 192.168.1.130
Subnet 255.255.255.0
DG 192.168.1.1 (router)

NIC2
IP 10.0.0.10
Subnet 255.0.0.0
No DG

Workstation:
IP 10.0.0.11
Subnet 255.0.0.0
DG 10.0.0.10 (Server)

Both machines ping each other and i have internet connection on the server but not on the workstation?
I restarted both PCs. Do I have to add some route?

Routing table form server:




OK everything fine now enabling NAT on the interface with 192.168.1.130 helped.

 

Hi,

I have another question is there some port forwarding in windows 2003? I would like to enabled it so I could RDP to PCs from LAN (I've set this on router before but I'm wondering now if there is such a option in windows 2003).

Basically I have one public IP and I would like to RDP to machines from LAN with different ports, for example:
-PC 1 IP xxxx.xxx.xxx.xxxx:3390
-PC 2 IP xxxx.xxx.xxx.xxxx:3391

Servers has two NICs
NIC1 is with public IP with NAT enabled on it
NIC2 has IP from private range and I have network connection on clients,

- so I've set something like this but it's not working:



I would like to achieve this without changing default RDP port of desired machines

Edit:

OK sorry but this solution is actually works just second reboot of routing services helped

 

Yes, I'm just learning/testing everything ;). I have few PCs and I would like to RDP to all of them from external network (internet) so that's why I have to use different ports for RDP connections with just single, public IP.

As I said the solution above is working ;)

 

Actually from a security stand point if you are trying to RDP from externally you are better off changing the default port of RDP.

You can then connect to the machine by using machinenameort

 

I just get my new toy Linksys WAG 320N ;)