Sorry so late in commenting chicagoan. Yes, attempting to stabilize the environment. The AD machine is the authoritative DNS (we have 7 new servers in their rack enclosure, but no power, no config yet......one will be new DC and a second DC) Took a look at zones. We have forwarding and reverse setup. They're not fowarding through firewall (??how to??....examples or cut n paste of a working config would be nice).... DHCP was running, but now off. All have static IPs (that's taken a day and some change to do)...
Everyone is now on a private address space of :
192.168.206.x
sub 255.255.255.0
gateway 192.168.206.3 Metric 1
207.178.x.x Metric 2 both are Sonicwall box
DNS NS
207.178.x.x ISP Name server
192.168.206.4 AD NS
192.168.206.2 NT Server NS
This has returned internal connectivity and intermitent internet. Folks will loose their internet connection after a few minutes, hours, and in some cases, days. The XP and 2000 folks have the advantage of opening up a DOS Shell and doing an IPCONFIG /REGISTERDNS which returns internet accessability to them. ?!?!? Why isn't DNS refreshing their internet connections? Is it the Sonicwall? What to do..?~ The Novell server is rebuilt now, but today FS2 went down for no apparent reason, but that's a whole different story and as of yet, not addressed due to the other higher priorities. Any further assistance would be appreciated!! Thanks !!!!!
Main Topics
Browse All Topics





by: chicagoanPosted on 2004-01-08 at 20:25:02ID: 10077876
1st off you need to stabilize the environment.
I'd set the AD machine to be the authoritative DNS, and the NT machine to be slave and use these for your DNS servers.
(You really ought to consider another AD box)
Take a good look at your zone files and make sure there aren't conflicts or omissions.
I'd set them both to be forwarding DNS servers to reduce DNS traffic through your firewall and use your ISP's DNS servers for resolution, proxy that through the Sonic Wall if you must.
I'd run DHCP on your AD machine, or the NT machine if that's not possible.
Then if you're still having problems you can start to delve into the other issues.
Do you have DNS resolution, are the proper PTR records in place (not an issue for internet access).
Once DNS is working properly, you can start looking into the traffic, what happens to a tracerroute?
Get to that device and see what the problem is, work your way outward.
I don't see the correlation with your Novell server, internet access and straight TCP/IP printing, unless there were some IP services there.