Test win2003 server - DHCP server unreachable problem

[Eco]

Test to migrate NT to win2003 and then installed DHCP service. But when I
try to connected from win2k client, it showed that DHCP server unreachable.

I've checked that:
- scope is active
- related scope opiton are applied
- have authorized the dhcp server.

What else should I check? Should I change the computer name's dns suffix??
Pls help me to troubleshoot. Thanks.

 

[Kevin D. Goodknecht Sr. [MVP]]

Test to migrate NT to win2003 and then installed DHCP service. But
when I try to connected from win2k client, it showed that DHCP server
unreachable.

I've checked that:
- scope is active
- related scope opiton are applied
- have authorized the dhcp server.

What else should I check?

Check the cables and switch, check that the server has as static IP on the
same subnet as the scope.
Post an ipconfig /all from the server.

Should I change the computer name's dns
suffix?? Pls help me to troubleshoot. Thanks.

I can't think how this would be of benefit, as long as there isn't another
computer on the network with the same name, even then it should still be
able to get an IP address.

 

[Eco]

Check the cables and switch, check that the server has as static IP on the
same subnet as the scope.
Post an ipconfig /all from the server.

Here is the info. The lan card is applied with two ip group. One for
internal lan and the other fix ip is for access internet.
======================================================

ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : ntsrv3
Primary Dns Suffix . . . . . . . : local.com.tw
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : local.com.tw
com.tw

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel 8255x-based PCI Ethernet
Adapter (10/100)
Physical Address. . . . . . . . . : 00-D0-B7-B8-66-A7
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 202.72.228.107
Subnet Mask . . . . . . . . . . . : 255.255.255.240
IP Address. . . . . . . . . . . . : 192.168.33.254
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 202.72.228.97
DNS Servers . . . . . . . . . . . : 192.168.33.254
======================================================
Some info on the dhcp server.
Scope - Address pool: 192.168.33.50 ~ 192.168.33.100
Scope - Scope options: 006 DNS Server 192.168.33.254
015 DNS Domain Name local.com.tw
003 Router 192.168.33.254
======================================================

Thanks for your support.

 

[Kevin D. Goodknecht Sr. [MVP]]

Here is the info. The lan card is applied with two ip group. One for
internal lan and the other fix ip is for access internet.
======================================================

Windows IP Configuration

Host Name . . . . . . . . . . . . : ntsrv3
Primary Dns Suffix . . . . . . . : local.com.tw
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : local.com.tw
com.tw

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel 8255x-based PCI Ethernet
Adapter (10/100)
Physical Address. . . . . . . . . : 00-D0-B7-B8-66-A7
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 202.72.228.107
Subnet Mask . . . . . . . . . . . : 255.255.255.240
IP Address. . . . . . . . . . . . : 192.168.33.254
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 202.72.228.97
DNS Servers . . . . . . . . . . . : 192.168.33.254
======================================================
Some info on the dhcp server.
Scope - Address pool: 192.168.33.50 ~ 192.168.33.100
Scope - Scope options: 006 DNS Server 192.168.33.254
015 DNS Domain Name local.com.tw
003 Router 192.168.33.254
======================================================

This setup won't work. If you have a router, remove the public IP from this
NIC, and set the router's IP as the Default Gateway with the server's IP as
the DNS server. If you don't have a router, add a second NIC to the server,
put the Public IP and Gateway on the Second NIC, and configure NAT on the
server (don't use ICS on a server running DHCP or DNS)
Is this or are you planning to make this a Domain Controller?
Name resolution and connectivity issues on a Routing and Remote Access
Server that also runs DNS or WINS:
http://support.microsoft.com/kb/292822/en-us

 

[Kurt]

I agree that the setup will not work (unless the OP is doing something
really strange for some unkknown reason). But if the DHCP scope is active,
the server is authorized and the clients are on the wire, they should at
least get a DHCP address (with settings that don't work).

....kurt