Server 2003 DNS problems

[AmateurMCP]

Hi Guys,

My first post to the forum, i dont know if this is the right place to be asking this, but here we go:

I have setup a small server 2003 test lab to practice on, it contains a SERVER2003 enterprise edition and i have connected a client machine running windows 2000 through a small 4 port hub to allow the machines to communicate.

The problem is that under the client machine i can resolve DNS host names fine and i get a reply, when i try this on the server side to resolve the client host name to a TCP/IP address i constantly get timeout errors.

Anybody have any ideas, i have checked the DNS entries and the default gateway and made sure that the server is pointing to itself for resolution, but no joy,

Any help would be appreciated,

Regards,

Ian

 

[aftertaf]

check and see if your dns server allows dynamic updates.

try nslookup on the command line.


are the 2 machines the only ones that are connected up via the hub? no internet or uplink?

try pings between server and client, both my hostname, FQDN and IP address.
let us know which work and which dont...
David

Aftertaf

getting quite good at sorting out Windows problems...
An expert when it comes to crashing Linux distributions (mdk, debian - nothing withstands me)

 

[AmateurMCP]

I have checked the Dynamic updates, and both secure and non-secure are enabled. From the client end i can ping the server fine by both FQDN, ip and host name.

When i attempt to ping the client from the server by any of these methods i get timeout errors.

when i run nslookup, i get the message :

Default servers are not available
default server :UnKnown
Address: 127.0.0.1

Thanks for your quick reply

 

[Wishdiak]

AmateurMCP,

On the Windows 2003 Server's TCP/IP properties, what IP address do you have for DNS?

Wishdiak
A+, Network+, Security+, MCSA 2003 certified

http://www.wishdiak.com

 

[AmateurMCP]

Hi Wishdiak,

I have set the DNS address as that of the actual server i.e. 192.168.0.1 which is working as a DHCP,DNS server, i have set this as a static address as required by DHCP.

Regards,

Ian

 

[Wishdiak]

AmateurMCP,

I stil think that the problem is in your TCP/IP settings for the server.

You should have (manually assigned)
IP Address: 192.168.0.1 (or whatever the IP address is)
Subnet Mask: 255.255.255.0 (assuming that you're using a class C address)
Default Gateway: blank, or server IP, or the actual gateway IP
Primary DNS: 192.168.0.1 (or whatever the IP address is)
Secondary DNS: blank

Is that how you have it?

Wishdiak
A+, Network+, Security+, MCSA+Security

http://www.wishdiak.com

 

[AmateurMCP]

Hi,

Thats exactly how the server is setup, i cannot understand how the client can resolve ip addresses but the server cannot !, this has me baffled !

Any other ideas, i'm quite new to the server side of things, been trying out the training book as recommended by Microsoft and have followed everything they have said, apart from activating the product, as you do not have to do this for about 60 days, which is all i will be using it for ...

Any other ideas, suggestions ?

Thanks,

Ian

 

[aftertaf]

might not give us any more info but can you run ipconfig /all on both and post us the results??

Aftertaf

getting quite good at sorting out Windows problems...
An expert when it comes to crashing Linux distributions (mdk, debian - nothing withstands me)

 

[AmateurMCP]

Hi Sorry about the delay in getting back, the results are as follows:

Client Side:

C:\Documents and Settings\Administrator>ipconfig /all

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : DESKTOP03
Primary DNS Suffix . . . . . . . : contoso.com
Node Type . . . . . . . . . . . . : Mixed
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : contoso.com

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : contoso.com
Description . . . . . . . . . . . : Xircom Cardbus Ethernet 100 + Modem
56 (Ethernet Interface)
Physical Address. . . . . . . . . : 00-10-A4-9C-5D-C7
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.10
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
Lease Obtained. . . . . . . . . . : 17 February 2005 16:09:48
Lease Expires . . . . . . . . . . : 27 February 2005 19:09:48

Server Side:

C:\Documents and Settings\Administrator>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : server01
Primary Dns Suffix . . . . . . . : contoso.com
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : contoso.com

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : contoso.com
Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network Connection
Physical Address. . . . . . . . . : 00-0D-60-32-EE-82
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1


Any information gained from this, thanks,

Ian

 

[jdcosner]

I had a problem similar to what you have. My gateway, which is a different machine, had a firewall on it. I had to config ure the firewall to allow for ICS. Once I did that, things were fine.

 

[aftertaf]

try a blank gateway on your server....

you have no routing anyway...
and you say both types of ping fail when you try server->client

can the server ping itself, with 192.168.0.1 and 127.0.0.1

could be amessed up tcp/ip stack...

activate netbios on both and see if the server can 'see' the client...


Aftertaf

"Resolve is never stronger than the night before it was never weaker

 

[AmateurMCP]

Activated netbios on both machines and configure server to have a blank gateway, still cannot ping the client, the server however will respond to ping from itself.

 

[aftertaf]

on its own IP or the 127 address? or both?

Aftertaf

"Resolve is never stronger than the night before it was never weaker

 

[aftertaf]

ping is a tcp/ip utility... so netbios wont help.

but if you can see your server from your client with "\\servername" unc path, then it is a tcpIP problem and not a network/nic/cable problem...

Aftertaf

"Resolve is never stronger than the night before it was never weaker

 

[jostudent]

DHCP Enabled. . . . . . . . . . . : No

....Have you authorized the DHCP Scope? It looks like your Client is obtaining it's IP address from the server. Is this correct?

 

[AmateurMCP]

Yes, This is correct, i have configured a static ip for the server and set it up as the DHCP server. I have asked the client machine to gain its DHCP lease from the server which it appears to be doing a-okay. The problem is that the statically addressed server cannot find the client, i have checked everything that has been suggested and some other things besides, i have given up and am going to install a clean version of XP on another client.

 

[AmateurMCP]

XP worked, as soon as i installed it, the machine worked straight away and the server could ping the clients, guess i'll have to use XP for my Labs !

Thanks for all the help,

Ian

 

[aftertaf]

that is just downright annoying!

a bug, then ?

Aftertaf

"Resolve is never stronger than the night before it was never weaker

 

[vldb]

I ran into this same issue. When following the 70-290 training kit book. Very frustrating as I am new to this. I have had to start over several times. After reading "Mastering Windows Server 2003", Mark Minasi, I first created the DHCP server, then the DNS server. Then the AD. When creating the AD with DCPROMO, the software runs a DNS Registration Diagnostics. I would get an error but was given an option to install and configure the DNS server. To fix my problem, I had to go back to DNS and set up the Forward and Reverse Lookup Zones correctly. Then when I ran DCPROMO again, the DNS Registration Diagnostics passed and everything worked as advertised. I've got WIN98 and XP running as clients.