Allowing public access to 2 PC's on a private network

Hello,

I have a stupid problem that is really starting to aggravate me.... I am
running Windows server 2003 (SBS) with 2 NICS 1 is dedicated to our ADSL the
other internal (192.168.254.x). On this network I have 10 clients 2 of witch
I need to allow public and private access too.....

Right now all internal clients and VPN can connect to the machines but I
need to be able to connect with our public IP....
Basically give my public IP to a person they type it into a program and it
takes them to this machine....port forwarding.
If I connect these machines to the native side of the server (on a Linksys
router) I can access the machines from the internet but not on my LAN

Can some one please guide me in the right direction....? My sales team has
begun to get antsy about when they will be able to get access to these
systems from outside of the network.
I have considered making the sales guy's connect with the VPN but the app
they demo is a remote video surveillance system manager and uses live video
and audio streams (in other words it doesn't like VPN very much).


Any help will be greatly appreciated.

Since you have two NICs, you may want to setup NAT. this page may help, NAT and Firewall How to configure 2000/2003 NAT services and ports. Open RRAS>IP Routing>NAT, right-click external NIC>Properties>Services and ports, select a service or add ...
howtonetworking.com/Windows/NAT&firewall.htm


Don't send e-mail or reply to me except you need consulting services. Posting on MS newsgroup will benefit all readers and you may get more help.

Bob Lin, MS-MVP, MCSE & CNE
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
This posting is provided "AS IS" with no warranties.

"Jason" <(E-Mail Removed)> wrote in message news:B0E1234D-BE97-46C3-85F2-(E-Mail Removed)...
Hello,

I have a stupid problem that is really starting to aggravate me.... I am
running Windows server 2003 (SBS) with 2 NICS 1 is dedicated to our ADSL the
other internal (192.168.254.x). On this network I have 10 clients 2 of witch
I need to allow public and private access too.....

Right now all internal clients and VPN can connect to the machines but I
need to be able to connect with our public IP....
Basically give my public IP to a person they type it into a program and it
takes them to this machine....port forwarding.
If I connect these machines to the native side of the server (on a Linksys
router) I can access the machines from the internet but not on my LAN

Can some one please guide me in the right direction....? My sales team has
begun to get antsy about when they will be able to get access to these
systems from outside of the network.
I have considered making the sales guy's connect with the VPN but the app
they demo is a remote video surveillance system manager and uses live video
and audio streams (in other words it doesn't like VPN very much).


Any help will be greatly appreciated.

"Jason" <(E-Mail Removed)> wrote in message
news:B0E1234D-BE97-46C3-85F2-(E-Mail Removed)...

> Basically give my public IP to a person they type it into a program and it
> takes them to this machine....port forwarding.
> If I connect these machines to the native side of the server (on a Linksys
> router) I can access the machines from the internet but not on my LAN

Although the term "port forwarding" gets tossed around all the time,..it is
not a real "term". There is a thing called Port Address Translation (PAT),
but that is not what you are describing. What you need to do is Static-NAT
(aka Reverse-NAT).

I think Robert is pointing you in the right direction with that. You can
only do *one* machine. Only one instance of an Application on the same port
and IP# can be run at a time.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

Not sure if Remote Desktop would be a solution for you, but you could enable
remote desktop on those two machines, and change the default listening port
on them:
http://support.microsoft.com/default...b;en-us;187623

Set each machine to listen on a different port, then setup your firewall to
forward those ports to the respective LAN IP addresses. Sales guy would
connect via remote desktop client to public IP address x.x.x.xortnumber

HTH
-- Paul



"Jason" <(E-Mail Removed)> wrote in message
news:B0E1234D-BE97-46C3-85F2-(E-Mail Removed)...
> Hello,
>
> I have a stupid problem that is really starting to aggravate me.... I am
> running Windows server 2003 (SBS) with 2 NICS 1 is dedicated to our ADSL
> the
> other internal (192.168.254.x). On this network I have 10 clients 2 of
> witch
> I need to allow public and private access too.....
>
> Right now all internal clients and VPN can connect to the machines but I
> need to be able to connect with our public IP....
> Basically give my public IP to a person they type it into a program and it
> takes them to this machine....port forwarding.
> If I connect these machines to the native side of the server (on a Linksys
> router) I can access the machines from the internet but not on my LAN
>
> Can some one please guide me in the right direction....? My sales team has
> begun to get antsy about when they will be able to get access to these
> systems from outside of the network.
> I have considered making the sales guy's connect with the VPN but the app
> they demo is a remote video surveillance system manager and uses live
> video
> and audio streams (in other words it doesn't like VPN very much).
>
>
> Any help will be greatly appreciated.
>

Your needs are business class and deserve a business class solution.
i would reccomend a Netscreen Router/Firewall (or some other higher end
device)apliance and getting several static public IPs.

The netscreen will allow you to both map the internal ips to the external
ips and also controll access via a very comprehensive rule set.

One thing that does have me mystified is that you mentioned a dual homed SBS
server and also having a Lynksys router. Further more you infered that SBS
system was NATing your internal requests, and was assigned a public IP on its
external port.

This implies that your linksys router has the SBS server on its DMZ port. It
further implies that any system connected to the router is exposed to the
outside world.

I don't see the logic to this design at all.

"Jason" wrote:

> Hello,
>
> I have a stupid problem that is really starting to aggravate me.... I am
> running Windows server 2003 (SBS) with 2 NICS 1 is dedicated to our ADSL the
> other internal (192.168.254.x). On this network I have 10 clients 2 of witch
> I need to allow public and private access too.....
>
> Right now all internal clients and VPN can connect to the machines but I
> need to be able to connect with our public IP....
> Basically give my public IP to a person they type it into a program and it
> takes them to this machine....port forwarding.
> If I connect these machines to the native side of the server (on a Linksys
> router) I can access the machines from the internet but not on my LAN
>
> Can some one please guide me in the right direction....? My sales team has
> begun to get antsy about when they will be able to get access to these
> systems from outside of the network.
> I have considered making the sales guy's connect with the VPN but the app
> they demo is a remote video surveillance system manager and uses live video
> and audio streams (in other words it doesn't like VPN very much).
>
>
> Any help will be greatly appreciated.
>