Re: network goes down everyday at same time

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



jennyjen <jennyjen@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
We have two firewalls: One controls rules for our desktops and has .2
gateway and the other controls rules for our servers and has a .1
gateway. So physically we have two different firewalls that are the
same in brand but different in config.

This still makes no sense. Can you post a link to a JPG of your network
topology? Maybe a visio diagram? Don't post an attachment in here..... if
you can't do a link, at least try to draw it out in text form.


as for the DNS stuff you mentioned im not sure i know what you mean.
What i was trying to say is that all our internet requests go out
through our ISP. We have internal DNS to direct all incoming traffic
for our hosted websites and what not....

You're hosting public websites on your LAN? This is unwise.

I'm really confused as to your setup, so it would help greatly if you could
describe the network more fully. I can't picture this.

"Phillip Windell" wrote:

"jennyjen" <jennyjen@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:C60C9986-0833-4360-9A06-AA2854F86D3B@xxxxxxxxxxxxxxxx
Thanks for the help so far everyone..below are the answers to your
questions:
we have two firewalls (client side and server side)

What does that mean? Firewalls have nothing to do with "client
side" and "server side". Firewalls have to do with physical
Topology,..."client side" and "server side" are simply Software
Application Perspectives.

www.google.com, www.yahoo.com for you and i am able to get a reply.
As for
DNS all outgoing requests we use our ISPs DNS and all incomming
requests we
host our own DNS.

You can't do that. You have to use *only* your AD/DNS.
The ISP's DNS IP# is only to be listed in the Forwarders List on the
AD/DC/DNS machines. The ISP's DNS IP# should *never* be listed
anywhere else.

You can optionally forget about listing the ISP's DNS as a Forwarder
and your AD/DNS will default to using Root Hints.

--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or
Microsoft, or anyone else associated with me, including my cats.
-----------------------------------------------------



.



Relevant Pages

  • Re: .com domain not accessible from .local workstations. Server O
    ... I was able to get rid of it by resetting it up as the only gateway ... DNS server listed for both the Lan nic and the Internet nic should list ... Connection-specific DNS Suffix. ...
    (microsoft.public.windows.server.sbs)
  • Re: newbie lost in trying to setup NAT
    ... Also make sure you have not configured a default gateway on the private ... that sounds correct for the DNS forwarding. ... > be able to resolve both local and Internet names from this server. ...
    (microsoft.public.windows.server.networking)
  • Re: DMZ setup
    ... 80 http Allowed Connection Web Access Only 403 anonymous Internal External ... no gateway and no DNS numbers. ... "deny" with server publishing, just the listener, and the destination IP. ...
    (microsoft.public.isa)
  • Re: Build up NAT/VPN Role Server
    ... Ifyou are not running Active Directory you do not need to set up DNS. ... use the NAT server as a DNS proxy (by configuring that option on the RRAS ... > upload) 2 Client running Windows XP Pro ... > Gateway = Not Set ...
    (microsoft.public.windows.server.networking)
  • Re: ICS b/w 2 win2k pros, while one is part of a domain?
    ... On computer A run ipconfig /all and note the DNS server IP. ... have a blank default gateway. ... DSL connection, which he redistributes to end user, using DHCP. ...
    (microsoft.public.win2000.networking)