sbs2003 and 2003R2 Terminal server

I have a situation where i'm not sure as how to proceed. The modem has
port forwarding and is currently set to 192.168.1.1 and forwards only
required ports to 192.168.1.2 (windows server) all clients get dhcp from
the windows box on 192.168.2.xxx. I've added a terminal server on
192.168.2.210 as a fixed ip address. Should this be on the 192.168.1.xxx
subnet to allow access from the outside? i've set the proper port to go
to 192.168.2.210 on the modem and now i can't access the server from
outside the network. What do i need to do to make the existing serveices
stay with the SBS server and only the Remote desktop port go to terminal
services.

In news:(E-Mail Removed),
Andrew Mallette <(E-Mail Removed)> typed:
> I have a situation where i'm not sure as how to proceed. The modem has
> port forwarding and is currently set to 192.168.1.1 and forwards only
> required ports to 192.168.1.2 (windows server) all clients get dhcp
> from the windows box on 192.168.2.xxx. I've added a terminal server on
> 192.168.2.210 as a fixed ip address. Should this be on the
> 192.168.1.xxx subnet to allow access from the outside? i've set the
> proper port to go to 192.168.2.210 on the modem and now i can't
> access the server from outside the network. What do i need to do to
> make the existing serveices stay with the SBS server and only the
> Remote desktop port go to terminal services.



I think you'd better post in microsoft.public.windows.server.sbs and tell
the nice people in there exactly what your setup is - ISA? Two NICs?
Hardware firewall appliance?

i've posted the same question in the forum you recommended

Lanwench [MVP - Exchange] wrote:

> In news:(E-Mail Removed),
> Andrew Mallette <(E-Mail Removed)> typed:
>
>>I have a situation where i'm not sure as how to proceed. The modem has
>>port forwarding and is currently set to 192.168.1.1 and forwards only
>>required ports to 192.168.1.2 (windows server) all clients get dhcp
>>from the windows box on 192.168.2.xxx. I've added a terminal server on
>>192.168.2.210 as a fixed ip address. Should this be on the
>>192.168.1.xxx subnet to allow access from the outside? i've set the
>>proper port to go to 192.168.2.210 on the modem and now i can't
>>access the server from outside the network. What do i need to do to
>>make the existing serveices stay with the SBS server and only the
>>Remote desktop port go to terminal services.
>
>
>
>
> I think you'd better post in microsoft.public.windows.server.sbs and tell
> the nice people in there exactly what your setup is - ISA? Two NICs?
> Hardware firewall appliance?
>
>

"Andrew Mallette" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> i've posted the same question in the forum you recommended

Great - hope you get some help.

(note that it's a newsgroup, not a forum - there is a difference)

>
> Lanwench [MVP - Exchange] wrote:
>
>> In news:(E-Mail Removed),
>> Andrew Mallette <(E-Mail Removed)> typed:
>>
>>>I have a situation where i'm not sure as how to proceed. The modem has
>>>port forwarding and is currently set to 192.168.1.1 and forwards only
>>>required ports to 192.168.1.2 (windows server) all clients get dhcp
>>>from the windows box on 192.168.2.xxx. I've added a terminal server on
>>>192.168.2.210 as a fixed ip address. Should this be on the
>>>192.168.1.xxx subnet to allow access from the outside? i've set the
>>>proper port to go to 192.168.2.210 on the modem and now i can't
>>>access the server from outside the network. What do i need to do to
>>>make the existing serveices stay with the SBS server and only the
>>>Remote desktop port go to terminal services.
>>
>>
>>
>>
>> I think you'd better post in microsoft.public.windows.server.sbs and tell
>> the nice people in there exactly what your setup is - ISA? Two NICs?
>> Hardware firewall appliance?