Server 2003 help

PaulStat · 8 Dec 2006 at 09:53

Ok got a small problemette, it's been about 4 years since i've played around with any server OS, and i've never touched MS Server 2003. So here's the problem:

The new server has been created with a domain name of SEFASBRISTOL.

The problem is when you try and connect to this domain from a workstation
you get an error something like "Network Path not found".

I've tried all sorts to fix it, but it just won't work.

The new server is currently on its own subnet, so you'll need a PC on the
same subnet to try and connect. It still doesn't work though.

So ideas?

Burnsy2023 · 8 Dec 2006 at 09:59

Can you get a ping echo?

Burnsy

oddjob62 · 8 Dec 2006 at 10:00

Is the workstation pointing to the domain controller as its primary DNS server?

Burnsy2023 · 8 Dec 2006 at 10:02

oddjob62 said:
Is the workstation pointing to the domain controller as its primary DNS server?

Does the DC have DNS installed?

Burnsy

PaulStat · 8 Dec 2006 at 10:08

burnsy2023 said:
Does the DC have DNS installed?

Burnsy

Yes and the event viewer thingy tells me DNS is started for SEFASBRISTOL

oddjob62 · 8 Dec 2006 at 10:23

PaulStat said:
Yes and the event viewer thingy tells me DNS is started for SEFASBRISTOL

From the workstation can you ping the server using it's FQDN?

ruffneck · 8 Dec 2006 at 10:31

first thing first

try pinging the ip address of the DC if that works, try pinging the fqdn of the DC

just to identify if its a connectivity issue or dns issue or somthing else

MAREKB · 8 Dec 2006 at 10:42

On the workstation, pull up a command prompt and type in nslookup and double check the results, these should match your server running DNS.

PaulStat · 8 Dec 2006 at 11:04

Right ok, I can ping it by IP and I can ping by the name (mia) and by FQDN. If I try nslookup however i get:

DNS request timed out.
timeout was 2 seconds.
*** Can't find server name for address 192.168.1.1: Timed out
*** Default servers are not available
Default Server: UnKnown
Address: 192.168.1.1

oddjob62 · 8 Dec 2006 at 14:22

oddjob62 said:
Is the workstation pointing to the domain controller as its primary DNS server?

You never answered this one. Is 192.168.1.1 the ip of this new server?

Curiosityx · 8 Dec 2006 at 15:24

Is the primary dns suffix configured on the PC?

Right click > My computer > properties > Computer Name > Change > More > Primary dns suffix.

Also through active directory sites and services are both subnets configured for the client and server subnet.

Most likely it will be a DNS issue - Run DcDiag from the windows support tools on both the DC and client machine - Post the results.

Also from the client run

Nslookup:
set type=srv
(Type Domain name)

Post results.