Re: In over my head... sbs 2003, router
- From: TF <tdqh1922@xxxxxxxxx>
- Date: Mon, 10 Dec 2007 10:42:17 -0800 (PST)
On Dec 10, 11:43 am, "Merv Porter [SBS-MVP]"
What leads you to believe that a single NIC solution will solve the
The two Nic setups allow the SBS servers to be isolated from each other so
they can run as independent domains. If you shift to single NICs you'll
have to deal with DHCP issues and IP address ranges for each each domain.
Since VPN port 1723 is hardcoded into Windows and can't be forwarded to
multiple IPs, even with single NICs, only one SBS will still only be able to
receive VPN requests. SSL port 443 will have to be changed to something
else for one of the SBS servers. Same for RWW 4125. And port 25 for email
will also have to be changed on one SBS server. In your scenario, I think
single NICs (unless you add an additional router for each domain) would
compound the problem.
Merv Porter [SBS-MVP]
"TravisF" <tdqh1...@xxxxxxxxx> wrote in message
arrggh. I am in a pickle. Can someone please offer a little direction.
I would be most grateful.
I'm trying to help a small business with a 2 server, 2 domain setup.
Servers are dual nics, then sharing a cisco 851 router for internet,
For reasons too long to blather about, its a bit of a mess with
outside vpn access, static routes etc.
Servers get bogged down often and users can't get to other resources
etc..mostly internet and webmail. So I would like to change the setup
so servers are 1 nic each. I know the 2 nic solution is the standard
but I don't wish to debate that right now.
What would I have to do to the router if I changed this?
What would be best way to change things?
How would I run dhcp?
Can I have 2 domains on same wire like this? Or even same subnet?
i.e. now server1 wan nic is 192.168.3.x and server2 wan nic is
and separate subnets on the lan sides.
What if I just used 3.x and 3.y ? or would it have to be i.e. 3.x and
Problem is I don't get much time on the system, so I need a sound way
to simplify this mess without spending too much time. The domains have
to be kept separate ( too much time/work to consolidate anyway)
Thanks in advance for suggestions!!
Thanks for that reply.
Maybe. This is why I'm trying to figure out what's the best option.
We're using cisco's vpn and authentication not the server's. Not using
email or RWW on the servers.
As mentioned, I'm more interested in creating a way for users to get
to the internet and webmail if either server is busy or down.
- Prev by Date: Re: External SMTP Exchange Setup
- Next by Date: Re: Critical Error - DCOM cannot start
- Previous by thread: Re: In over my head... sbs 2003, router
- Next by thread: Re: In over my head... sbs 2003, router