SBS 2008 - Problem connecting clients to domain

satanicguardian · 15 Jan 2013 at 12:42

Hey guys, bit of a problem, I don't know if you remember a post I made in this forum a while back regarding reinstalling an SBS server. Either way, I have this freshly installed SBS server, it's all setup on it's own, connected to router and ready to start having clients assigned to it.

However - when I try and http://connect, it times out - Using a client PC I can ping the servers IP on the router which is 192.168.10.38 but I can't "ping connect"

I have tried manually setting the DNS server address and DNS suffix but I still get the same issue, I'm not sure if it's an issue with services not running or if it's a problem with the router getting in the way.

Currently the router is acting as DHCP server but I know it is possible to have this server acting as a local domain with the router assigning IP addresses as DHCP.

I'm starting to get confused though, could anyone help?

I'm happy to set up a teamviewer session if anyone is kind enough? (not a data security risk as no data is stored locally, all cloud based

)

Thanks in advanced, Jamie

satanicguardian · 15 Jan 2013 at 14:02

bremen1874 said:
You'd normally have DHCP on the server.

The PC needs the server ip for its DNS. This would autoconfigure if the DHCP was on the server.

The server also needs to point to itself for DNS.

For DHCP that means I'd need to remove the DHCP service from working on the router wouldn't I? Then enable it on the server?

The reason router is working DHCP is because before I reinstalled the server was very unreliable, if it crashed all the clients would lose internet, is there anyway to cut the reliance on server for internet access yet still use it as a domain?

satanicguardian · 15 Jan 2013 at 14:32

My brain has turned to a potato at the moment; I should log into my router and then change what? XD

satanicguardian · 15 Jan 2013 at 15:01

Changing that now will bring the clients offline won't it? I can't really afford down time, especially during hours

satanicguardian · 15 Jan 2013 at 15:42

iaind said:
Why would it?

Well at most it would assign new IP addresses and cause some problems?

(I said my brain was a potato today)

satanicguardian · 15 Jan 2013 at 15:43

What is it I need to change here?

satanicguardian · 15 Jan 2013 at 15:44

I'm guessing Static DNS 1?

satanicguardian · 15 Jan 2013 at 15:50

satanicguardian · 15 Jan 2013 at 15:50

SBS box is airtelserver, so yeah

satanicguardian · 15 Jan 2013 at 16:06

I just realised this, but it didn't work as static either, I am basically a potato.

Someone assist my lowly potatoness and tell me wtf I'm putting in here

satanicguardian · 15 Jan 2013 at 16:10

Noo

it wouldn't work on dynamic at all as far as I know, however I cannot remember how to go further without the assistance of you lovely people, damn my limited networking experience!

satanicguardian · 15 Jan 2013 at 16:16

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

satanicguardian · 15 Jan 2013 at 16:20

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 · 15 Jan 2013 at 16:26

Kaka said:
Also, get a better AV solution for you server.

Clamwin isn't that... well yes it is bad

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

satanicguardian · 15 Jan 2013 at 16:38

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.

Ok I rebooted the server and client laptop, still getting timeout on "ping connect" did I need to change anything on the routeR?

satanicguardian · 15 Jan 2013 at 16:38

Maybe it's a service not running?

satanicguardian · 15 Jan 2013 at 16:40

Yet strangely I can log onto the server with MSTSC from my own desktop, still can't get connect to ping

satanicguardian · 22 Jan 2013 at 09:22

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.

satanicguardian · 22 Jan 2013 at 12:34

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

I'm a networking noob

satanicguardian · 22 Jan 2013 at 16:20

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

And here is root hints, no idea what this bit means