Connecting to gateway on a different subnet?

By Dean Wheatley ·
I am trying to run a test system with very limited resources. I have an XP system running Windows Vista as a virtual machine. They are both part of a domain. I am trying to test a remote VPN connection through a secondary line we have and have setup the virtual machine with an IP address on a completely separate subnet, lets say, I am then trying to connect it to a gateway of I can't change the gateway IP and if I change the IP address of the virtual machine onto the same subnet as the gateway the test will be pointless as I will be on the same sub as the server i'm trying to connect to remotely (I think that makes sense:)).
Am i clutching at straws here or is there a better way?


This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Answers

Collapse -

well sorry but if you can't change the gateway

by CG IT In reply to Connecting to gateway on ...

your out of luck. The "gateway" address is literally the gateway out [and in] [the router that routes traffic].

Collapse -

Thought so....

by Dean Wheatley In reply to well sorry but if you ca ...

I figured there was little option. I did try and narrow it down using subnetting. IE i reset the IP on the client and used a very short mask, that included both gateway and client on ip x.x.x.252 and gateway x.x.x.254. I could then access the gateway IP and reach out to the internet. Odd thing was that I still could still ping x.x.x.2 (The computer I was trying to remote into). My understanding was that as the client was on a different subnet i shouldn't have been able to access it?


Collapse -

the only way to do this is with static routing on the router

by CG IT In reply to Thought so....

the router will route traffic to other subnets if you put in a static route so the router knows what to do with the packets it receives.

but you want remove access and unless the router knows what to do with the inbound traffic it will drop the packets.

You can route inbound traffic to other subnets but that doesn't mean that traffic on specific ports are allowed through the perimeter router firwall. For that you have to specify that the router forward all inbound traffic on a specific port to a specific host on a specific subnet.

While consumer level routers are somewhat sophisticated, their port forwarding through the firewall usually is limited to the routers subnet and not another subnet.

Related Discussions

Related Forums