SBS 2008 - Problem connecting clients to domain

Flattery will get you everywhere!

If your DHCP range starts at 192.168.10.20 then you need to use a free address before this range.

If its free use 192.168.10.2

so your settings will be ...

IP - 192.168.10.2
SM - 255.255.255.0
GW - 192.168.10.1
DNS - 192.168.10.2
 
Flattery is how I get by ;D Haha!

Ok cool, so I enter those settings into the server and then change what on the router? :)
Also, the network printer seems to work on 192.168.10.18 even though it's outside the ip range, not sure how :D
 
Your printer is on a static IP for the same reason that the server should be. So that it doesnt change and clients can find them.

On the router leave the Static DNS 1 as it is. It will be correct if that address is free and is going to be used for the server.

To be honest, it looks as though your router has been correctly setup, probably going back to your original SBS networking config before it was wiped.
 
Ok I've changed those settings on the server, the server is now using static 192.168.10.2
with a default gw at 192.168.10.1 a subnet mask of 255.255.255.0 and a primary DNS of 192.168.10.2

I've released and refreshed, then attempted to "ping connect" from a client on the same network, no response from connect but I can ping 192.168.10.2

Now what? :c
 
satanicguardian said:
Ok I've changed those settings on the server, the server is now using static 192.168.10.2
with a default gw at 192.168.10.1 a subnet mask of 255.255.255.0 and a primary DNS of 192.168.10.2

I've released and refreshed, then attempted to "ping connect" from a client on the same network, no response from connect but I can ping 192.168.10.2

Now what? :c
Click to expand...

Reboot the server. Your DNS wont be functioning correctly and all the things that rely on it will probably be not working. A reboot should clear it. If not, we'll need to look deeper at it.
 
Kaka said:
:eek:

Also, get a better AV solution for you server. :)
Click to expand...

Clamwin isn't that... well yes it is bad :D and haha boss won't fork out for anything, we don't use server for anything but local administration either - (I'd rather just migrate over to intune but for some reason MD wants to use this dinosaur of a server)

And yeah im rebooting it now :D
 
tribz said:
Reboot the server. Your DNS wont be functioning correctly and all the things that rely on it will probably be not working. A reboot should clear it. If not, we'll need to look deeper at it.
Click to expand...

Ok I rebooted the server and client laptop, still getting timeout on "ping connect" did I need to change anything on the routeR?
 
satanicguardian said:
Ok I've changed those settings on the server, the server is now using static 192.168.10.2
with a default gw at 192.168.10.1 a subnet mask of 255.255.255.0 and a primary DNS of 192.168.10.2

I've released and refreshed, then attempted to "ping connect" from a client on the same network, no response from connect but I can ping 192.168.10.2

Now what? :c
Click to expand...

Try ping connect.yourdomain.yourdomain

The router wont be handing out (and probably wont support it) a DNS suffix - although it might if you set the domain name on the router
 
Hi guys, sorry I thought I had replied to this!

The server is now up and running, I've managed to reconnect a client PC, I just have to change the main DNS address on the client PC to point to the server.

So yeah, that all works fine but I haven't had time to add all the users.

Since I've got the server working and have the ability to join the domain, all the client PC's connected to the network (even ones not on the domain) seem to be getting weird DNS caching problems.

Websites that users have been on before cache as they should, but for some reason if the user tries to go back and use them later it just shows, "this page could not be displayed".

The quick fix is to flush the DNS, I want to know why this is happening cause it's frustrating :( could anyone help with this? It's happening to all users, regardless of whether they are on the domain or not. :(
 
Yes iaind, I have even create batch files for the users to click on that release, renew and flush dns, sometimes even this won't work, and I don't know what they are so probably not :P I'm a networking noob
 
There are books and step-by-step guides available that'll lead you through the steps necessary to setup a SBS server. There are many small things that can cause you problems if you miss them.

DNS forwarders allow you to add the addresses of external DNS servers to the DNS server on the SBS box. Googling 'dns forwarders' should fill in the details.

Have you got the clients configured so they ONLY use the SBS server for DNS?
 
Basically, the DNS server is running on SBS - this will handle DNS queries for the internal network (this is why it wasnt working when you werent pointing clients to it) and queries for the internet.

But the DNS server has to know what to do for queries for domains it doesnt know about (eg the internet!). This can be done in one of 2 ways - root hints or forwarders. The server will be doing one of these! Root hints are a list of known servers for the root domains so it can recursively look up the hostname you're requesting. Forwarders are the more common way of handling it - which is just to pass the query onto another DNS server, this would normally be your ISP's DNS server but Google DNS or OpenDNS work well too.

So, start by finding out and understanding exactly how your server is behaving. Open up DNS management and look at the properties of the server object. Is there anything on the forwarders tab? If there is, these are the servers that your server will be talking to if it cant resolve a query itself. Make sure these are valid and servers you trust. OpenDNS is a nice one to use to provide extra security and a bit of web filtering too. If there's nothing configured as a forwarder, it will resort to root hints - these work just as well but require a bit more care and management. Check the root hints tab to make sure it's populated.

Now, you've already established that the problem appears to be DNS and found a potential fix. However, you've made the rookie mistake of finding a fix before confirming the problem. So lets take a PC currently experiencing an issue and probe deeper. Open a command prompt and try to ping the website by name - does it resolve and return a ping? If so, your issue isnt DNS related. If it doesnt resolve to the correct address, launch nslookup from the command prompt. When you launch nslookup, it will tell you which DNS server its using - this should be your SBS server, if not, your client configuration is still not right. At the nslookup > prompt, type the website name and hit enter, you should get an immediate response without any errors. If it's failing to resolve the DNS name, it will give you an error here.
 
forwarders_zps7d8f413a.png


Here is the forwarders tab, completely empty, should I set something up in it?

roothints_zpse603be6c.png


And here is root hints, no idea what this bit means :D
 
You must log in or register to reply here.
Back
Top Bottom