annoying server 2008 problem -.-

hellarda · 22 Jan 2011 at 22:06

Hi,

I have just installed SBS 2008 on my dell powerdge 2850 and a Server enterprise 2008 x86 on an HP server i have.

my problem is that i cannot add client computers to the SBS network, nor can i add the second server to the domain.

All computers/servers point to the 2850 for DNS and I have tried with static IP's and DHCP from the 2850.

i have set up a DHCP scope from the 2850, also DNS lookups are set up, all computers can ping the server.

when i go to http://Connect i get 'internet explorer cannot display the webpage' if i go to http://localhost i also get the same message.

this is really annoying me .

any ideas?

ta

Ali

P.S all clients are running WIN 7 ultimate

hellarda · 23 Jan 2011 at 12:43

anyone?

havok · 23 Jan 2011 at 13:14

Have you got two NIC's plugged in? - if so unplug one to test. eventlog clean?

hellarda · 23 Jan 2011 at 13:24

yeh i did but i tried without and didnt make a difference, clear eventlog? sorry im a noob at this stuff (im only 16)

cheers

havok · 23 Jan 2011 at 15:52

Errors in the eventlog? Also client pc's need to have DNS pointed at the SBS2008 server

hellarda · 23 Jan 2011 at 17:23

nope cant see any :/ all the clients do point to the server for DNS

cooljimy84 · 23 Jan 2011 at 21:16

can u resolve DNS from the server ?
i.e. on the client PC ping www.google.co.uk then try a local PC name, then try server name any of them work at all ?

oddjob62 · 23 Jan 2011 at 21:44

What happens when you try to add machines to the domain using the bog standard method (ie not using the connect wizard)?

hellarda · 23 Jan 2011 at 22:11

cant find the domain

and google and other client PC's work by IP not name and same with the server

oddjob62 · 23 Jan 2011 at 23:27

Is DNS working on the server? Does it work when you use FQDN as opposed to just host name?

havok · 24 Jan 2011 at 09:10

oddjob62 said:
Is DNS working on the server? Does it work when you use FQDN as opposed to just host name?

If this doesn't work, check the NIC properties on the server are pointing to itself for DNS. Also within the DNS server there is a 'forwarders' tab where you put the ISP's DNS server settings.

Toughnoodle · 24 Jan 2011 at 13:06

Sounds like you've got 2 problems: DNS and IIS (the Microsoft web server). You've got plenty to go on for the DNS side already. For IIS, I'd try iisreset in a cmd prompt. It's not as drastic as it sounds, it'll just restart the IIS services. Then, check for any stopped sites in the IIS Management interface.

zetec452 · 24 Jan 2011 at 18:24

Netdiag and dcdiag are handy tools to check the status of the server. You can run them in the command line and pipe them to a text file like so:

netdiag > C:\netdiag.txt

See if you can find any warnings after running these commands.

hellarda · 24 Jan 2011 at 18:37

ok will have a go at all these when i have time (probably won't be till the weekend as i have exams

)