I could use a bit of ...

The Goal:

Add a wireless router to my existing network.

For security, I would like to place the wireless router and it's
clients outside the corporate firewall.

We currently have a DSL connection with 5 static IP's.

------------------------
Here is what I have done (feel free to snicker)

I plugged the ethernet connection from the DSL modem into a 4-port
mini-hub. I then plugged the Wireless router and the firewall into
the same hub.

Behind the firewall is a nat'ed LAN (192.168.0.1 - 192.168.0.255)

Our external IP addresses are: xx.xx.xx.60 - xx.xx.xx.64

xx.xx.xx.60 is picked up by the firewall and routed to our internal
mail server

xx.xx.xx.61 Is picked up by the firewall and routed to a remote
desktop host.

xx.xx.xx.62 Is the wireless router which has a nat'ed lan (192.168.1.1
- 192.168.1.255)

63 and 64 are not used.


From a PC using the wireless router I can surf the web and access
other remote desktops. However when I try to access the remote
desktop at xx.xx.xx.61 it cannot be found.

I'm guessing that the wireless router thinks that xx.xx.xx.61 belongs
to it and so it cannot locate it.

Any suggestions on how to fix this, or is it just a flawed plan from
the get-go?


Thanks.

Scamp@nospam.com wrote:
> I could use a bit of ...
>
<snip>
>
> Behind the firewall is a nat'ed LAN (192.168.0.1 - 192.168.0.255)
>
> Our external IP addresses are: xx.xx.xx.60 - xx.xx.xx.64
>
> xx.xx.xx.60 is picked up by the firewall and routed to our internal
> mail server
>
> xx.xx.xx.61 Is picked up by the firewall and routed to a remote
> desktop host.
>
> xx.xx.xx.62 Is the wireless router which has a nat'ed lan (192.168.1.1
> - 192.168.1.255)
>
> 63 and 64 are not used.
>
>
> From a PC using the wireless router I can surf the web and access
> other remote desktops. However when I try to access the remote
> desktop at xx.xx.xx.61 it cannot be found.

What about xx.xx.xx.60? What happens if you access these from the wired
lan? When you say `cannot be found' do you mean not found by the remote
desktop program or not found by pinging?

> I'm guessing that the wireless router thinks that xx.xx.xx.61 belongs
> to it and so it cannot locate it.

That may be problem. What is your IP address as seen by the rest of the
world from your wireless-connected PC (i.e., www.whatismyip.com)?

> Any suggestions on how to fix this, or is it just a flawed plan from
> the get-go?

What type of wireless router do you have? Most OTC ones can be
configured through a web-based interface. Usually you can set both the
IP address of the (wired) network interface, as well as the IP
range/subnet/etc for the built-in DHCP server.

> Thanks.

You're welcome