Re: firewalls 2 n ics and headaches :0

ok, i have all set up as follows:

sonic wall has wan ip of xxx.xxx.xxx.194

nic 1 has internal ip of 192.168.1.10
nic 2 has ip of xxx.xxx.xxx.195

dns on both nics are pointing at .10 and the dns forwarders are set to the
isps dns

but i cant get out online at all,

the sonicwall is attached on the wan port to the cisco router
the lan port on the sonicwall is pluged into the switch

the 2 nics on the server are pluged into the switch as well
all pcs are pluged into the switch

where can i be going wrong ?

when i log into the sonic wall i can run pings from it

"JML" wrote:

> http://www.smallbizserver.net/Default.aspx?tabid=154
>
> "patrick" <patrick@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:B52C48DA-8663-4343-A16C-EFC01AF20E83@xxxxxxxxxxxxxxxx
> > hi greg,
> >
> > when you say hard code one nic to do match the internal network on the
> > sonic
> > wall and the other for the range , can you be more specific ?
> >
> > thanks
> >
> >
> > "Greg" wrote:
> >
> >> Patrick,
> >>
> >> I have set this up many times. I would disable DHCP on the sonic wall.
> >> Hard code one nic to match the internal network on the sonicwall and the
> >> other for the range of your machines.
> >>
> >> I would then use DHCP, WINS and of course DNS from SBS2003. Works like a
> >> champ.
> >>
> >> Good luck.
> >>
> >> Greg
> >> "patrick" <patrick@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> >> news:5FF1DF9E-B2D1-44DC-BBD6-8DCEF5C574CE@xxxxxxxxxxxxxxxx
> >> > hi , i have a hp server , with 2 nics, i also have a sonic wall
> >> > firewall ,
> >> > handlining dhcp and all firewall activity.
> >> >
> >> > my question is that i have been told i should disable one of the nics
> >> > on
> >> > the
> >> > server as the sonic wall is handling the firewall
> >> >
> >> > is this correct ?
> >> >
> >> > also for some reason i cant access email from outside the firewall, i
> >> > can
> >> > access it using OWA but not if i set up outlook at a remote location,
> >> > also
> >> > no
> >> > remote desktop aceess.
> >> >
> >> > thanks
> >>
> >>
> >>
>
>
>
.

Relevant Pages

  • Re: Server 2003 Standard - Cannot browse domain with domain controller!
    ... Works great if you are routing to the internet but a WAN ... configuration requires such services on both NICs. ... We have just changed our configuration of our network so that our PDC ... DNS is the same. ...
    (microsoft.public.windows.server.networking)
  • Re: Problem with internet connection
    ... Depending on the hardware/NIC you maybe can use a teaming software to combine both physical NICs to a virtual, which then can be used for automatic failover or loadbalanced. ... Multihoming a server, using more then one ip address, can result in problems you don't wan't. ... Multihomed DCs, DNS, RRAS servers. ... there are some registry changes to eliminate the registration of the external NIC. ...
    (microsoft.public.windows.server.networking)
  • Re: Urgent! New router and big disaster
    ... NIC, you need to specify an external DNS server for DNS, instead of the ... Both NICs should point to his internal IP for DNS. ... forward ports to it reliably in the router. ...
    (microsoft.public.windows.server.sbs)
  • Re: issue with DC replication
    ... DNS server to ... As Jorge stated and explained why, multiple NICs on a DC is not recommended ... internet gateway, it is recommended to purchase an inexpensive, or cable/DLS ... there are some registry changes to eliminate the ...
    (microsoft.public.windows.server.active_directory)
  • Re: Machines not being registered in DNS anymore
    ... using two nics on a dc is only a problem when both nics are on the ... But if on different subnets, and one is NOT reachable by clients, yet the registration exists in DNS and will more than likely be given to a client in a query response, then YES it WILL be problematic. ... If you have an ISP's (or some other outside DNS server or even using your router as a DNS server) DNS addresses in your IP configuration, they need to be REMOVED and ONLY use the internal DNS server. ... there are some registry changes to eliminate the registration of the external NIC or simply use the internal networking routing to allow access. ...
    (microsoft.public.windows.server.dns)