Re: 1 NIC v. 2 NICS & remote access questions from beginner
- From: "Russell DeMarco" <rdemarco@xxxxxxxxxxxxx>
- Date: Tue, 19 Jul 2005 15:41:57 -0400
> There are a couple of ways that you could configure your network. Since
> you're using SBS Standard and not Premium, I'll assume that there is no
> ISA Server on your network.
>
> A typical configuration would be to have your ISP's router connected to
> your firewall device. [I'll assume that your Symantec router is really
> your firewall.] The firewall would have a public IP address assigned by
> the ISP to the WAN port, and it would have a private address
> (192.168.etc.etc) assigned to its LAN port.
>
> The server needs to have only a single NIC on the same subnet as the
> firewall LAN port. So if the firewall LAN port is at 192.168.0.1, then
> you could put your server at 192.168.0.2 and your workstations and
> network printers would follow the pattern.
All of the above is correct.
>
> To access features of the server remotely (such as Outlook Web Access or
> Remote Web Workplace), you will need to setup port forwarding on the
> firewall. Examples: port 25 for inbound email, 443 for HTTPS needed for
> OWA, 4125 needed for Remote Web, etc.
Which one of the above (or sharepoint?) allows our users to access files on
the server remotely? Is it better to use the router/firewall's VPN?
Here's where I get confused. Our router/firewall (Symantec) has public
ip...118 attached to it's WAN port that's our Gateway, correct? (We have a
block of 5 IPs.) We then followed SBS directions which stated we need to
have our ISP point a DNS "A" record to server.domainname.com and we told
them it'll be public ip...117. I assume this was to access the server
locally. We also had them point our MX pointer to .117. We're not using
Exchange YET.
So do I setup the .117 on our server's NIC? Do I port forward to the
servers private IP?
Thanks again.
> ______________________________________
> Bradley J. Dinerman, MVP - Windows Server Systems
> President, New England Information Security Group
> http://www.neisg.org
>
> Russell DeMarco wrote:
> > We have SBS 2003 std that we've been using for a few months now. We now
> > want to access the server remotely and setup Exchange. We have 1 NIC,
do we
> > need (or is it preferred) 2? The first NIC is a local IP 192..., do we
> > setup the 2nd NIC with one of our public IPs? Is there something I need
to
> > do in our Symantec router (forward ports or something)? (It's not
recognized
> > by SBS.) Is it better if I use the VPN in the router?
> >
> > Thanks.
> >
> >
.
- Follow-Ups:
- Re: 1 NIC v. 2 NICS & remote access questions from beginner
- From: Brad Dinerman [MVP - Windows Server Systems]
- Re: 1 NIC v. 2 NICS & remote access questions from beginner
- From: Darío Díaz Anzalone
- Re: 1 NIC v. 2 NICS & remote access questions from beginner
- References:
- 1 NIC v. 2 NICS & remote access questions from beginner
- From: Russell DeMarco
- Re: 1 NIC v. 2 NICS & remote access questions from beginner
- From: Brad Dinerman [MVP - Windows Server Systems]
- 1 NIC v. 2 NICS & remote access questions from beginner
- Prev by Date: Re: DHCP not sending DNS server
- Next by Date: Re: Totally the general topic in here
- Previous by thread: Re: 1 NIC v. 2 NICS & remote access questions from beginner
- Next by thread: Re: 1 NIC v. 2 NICS & remote access questions from beginner
- Index(es):
Relevant Pages
|