troubleshooting Question

Watchguard Firewall in Server 2003 Environment - DNS Issues

Avatar of jaelae
jaelaeFlag for United States of America asked on
Software FirewallsWindows Server 2003DNS
4 Comments1 Solution563 ViewsLast Modified:
I'm having DNS woes with my newly installed Server 2003 environment.  We have a workgroup network that connects to our Watchguard Firewall via static address.  The firewall has interface0 set to internet and interface1 set to our internal network (192.168.1.0/24).  Interface0 is set to (192.168.1.1).

All desktops are configured static to connect to it.  The configuration on each machine would be similar to:
IP: 192.168.1.105
Subnet: 255.255.255.0
Gateway: 192.168.1.1
DNS: 4.2.2.2

This week I installed a Windows Server 2003 rack server and started a domain and made it to the DC.  It is set as follows:
IP: 192.168.1.2
Subnet: 255.255.255.0
Gateway: 192.168.1.2
DNS: 127.0.0.1

Now, my clients have to choose a different gateway and DNS to choose either internet / or server access.  I've tried having them point to the servers address as Gateway and DNS as I have installed DNS on the server, and set forwarding to send requests to the 192.168.1.1 or 4.2.2.2 address.  So far, I have been unlucky.  Anyone know what maybe going wrong?

THANKS!
Join the community to see this answer!
Join our exclusive community to see this answer & millions of others.
Unlock 1 Answer and 4 Comments.
Join the Community
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 1 Answer and 4 Comments.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros