Connect to Internet without Windows Domain Server
Katz
Newbie ✭
Comcast Internet is currently working, but only while our Windows Domain Server is ON. Once the Windows Server is offline/shutdown and using one of the computers, I am still able to access the different drives in the local network, BUT I cannot access the internet.
I am looking at the NAT Policies, but not entire sure what I am looking at. How can I make sure that my other computer will still have internet access even if the Windows Domain Server is offline? With the other windows, we created local users so that we need not be using the domain, but still, no internet. Please advise.
Category: Entry Level Firewalls
0
Answers
@Katz,
Welcome to SonicWall community.
So, the users that are not part of the domain, when you ping google.com on them, is it failing? Also, if you are pinging 8.8.8.8 from the same machine is that working fine?
It is highly unlikely that this would be a NAT policy issue as that would affect the internet access even when the internal DNS server is in use. Could you please run those tests and let us know the results?
Thanks!
Shipra Sahu
Technical Support Advisor, Premier Services
I think this is a DNS problem.
I would check what DNS servers are the clients using. DC IP address or public DNS server?
Try to PING 8.8.8.8 and 8.8.4.4.
Try "nslookup" and see if you can resolve some Internet names...
Hello,
Here are the tests I made
Local user(not domain user):
Ping 8.8.8.8 was a success
Ping 8.8.4.4 was a success
Ping google.com was a success
Web browser failed to connect
Nslookup was using the Domain Server's ip address as the default, but after disconnecting the domain server, it now says that the DNS request timed out. Default Server: Unknown.
Domain user
Ping 8.8.8.8 was a success
Ping 8.8.4.4 was a success
Ping google.com failed to connect
Web browser failed to connect
Nslookup was using the Domain Server's ip address as the default, but after disconnecting the domain server, it now says that the DNS request timed out. Default Server: Unknown.
New update:
Hello,
Here are the tests I made
Local user(not domain user):
Ping 8.8.8.8 was a success
Ping 8.8.4.4 was a success
Ping google.com failed to connect
Web browser failed to connect
Nslookup was using the Domain Server's ip address as the default, but after disconnecting the domain server, it now says that the DNS request timed out. Default Server: Unknown.
Domain user
Ping 8.8.8.8 was a success
Ping 8.8.4.4 was a success
Ping google.com failed to connect
Web browser failed to connect
Nslookup was using the Domain Server's ip address as the default, but after disconnecting the domain server, it now says that the DNS request timed out. Default Server: Unknown.
Have you tried changing the DNS servers on a client PC?
I mean, you could put 8.8.8.8 as the primary DNS server and 8.8.4.4 as the secondary DNS server on the client PC TCP/IP settings.
In case you have a DHCP server on the LAN, change the DNS servers it is offering to clients.
I can try that, thank you.
Also, if this works, would it be accurate to say that it'll have to be done to ALL computers instead of just on 1 place which is within the SonicWall configuration?
Yes, you should do that to all PCs on the LAN.
You could also setup a DHCP server on the firewall itself. And set the DNS option to give 8.8.8.8 and 8.8.4.4
In case you have too much PCs on the LAN, I would suggest the second option.
I'll likely have to go with the second option.
Would this be a good guide in adjusting the DHCP server on the firewall itself:
SonicWall: Network > DHCP Server > check the checkbox for "Enable DCHP Server"?
When I am adding DHCPv4 Server Lease Scopes DNS/WINS, I will set to:
select the radio button for "Specify Manually"
"DNS Server 1: 8.8.8.8"
"DNS Server 2: 8.8.4.4"
Yes @Katz that should do the trick.
I was able to test again today.
I followed the steps here on section: Resolution for SonicOS 6.5
I tried the IP address that the example has, but I kept getting the following error:
"Error: Total Number of DHCP leases exceeds the maximum 4096", but I eventually found a starting-ending IP Address that eventually worked.
2 Case Scenarios: