If you want to use any of the routing/firewall properties of sbs (or any
Windows server for that matter), the two NICs must be in different subnets.
The "private" side of your router must be in a different subnet from the
"public" side. If you are behind some other router, your "public" interface
may in fact have a private IP address.
"Lanwench [MVP - Exchange]"
<(E-Mail Removed) ahoo.com> wrote in message
news:(E-Mail Removed)...
> What version of SBS? Using ISA?
>
> Honestly, with a single server shop, I'd ditch the idea of using your only
> server/DC as a firewall/router. Get a decent firewall/gateway/router
> appliance - they're pretty cheap. Just my unsolicited $.02
>
> Shane Campbell wrote:
> > Hey all, i have recently installed a small buisness server
> > 2003 server at work and i tried to set it up as a
> > firewall. i have tried everthign i can to try and get the
> > 2nd network interface working, but it just wont, it says
> > it is connected and it gets an ip address fromt the
> > router, which has a built in dhcp server, but i cannot
> > acces the router, opinging or other wise, and i cannot
> > access the internet either,how ever it all works fine if i
> > plug the router into my primary network connection,
> >
> > Currently this is my config:
> >
> > Server Local area connection:
> > IP: 192.168.1.2
> > Subnet mask: 255.255.255.0
> > dns: 192.168.1.2
> >
> > network connection:
> > ip 192.168.1.253
> > subnet mask: 255.255.255.2
> > dns: 192.168.1.2
> >
> > i have tried changing the dns of the 2nd connection to my
> > routers ip address (192.168.1.1) and also putting them
> > both on a different subnet than the server network
> > connection, all to no avail, please help
> >
> > thanks
> > shane
>
>
|