Ip Fowarding failure after upgrade to Windows 2003

We have a muti-homed W2K member server that was upgraded to Windows Server
2003 R2. NIC # 1 is for internal users on the LAN, the other NIC # 2 is set
up to use the DHCP Service to provide ip addresses for visitors to access the
Internet. Once I upgraded the server to 2003 the DHCP clients can no longer
access the internet.

NIC # 2 (assigned to DHCP) has 2 ip addresses, the first is a valid IP
address, say, 66.151.154.8 the second is 192.168.168.1

A PC connected to NIC #2 will receive the correct ip info by doing an
ipconfig /release and then an ipconfig /renew. I can then do a ping to
192.168.168.1 and also ping 66.151.154.8, but I cannot ping past 66.151.154.8.

I have set the IPEnableRouter registry setting to 1, and do not have RAS
enabled.

From the member server I can ping the web and also ping any DHCP clients. I
cannot ping a DHCP client from any other LAN PC other then the member server.

What am I missing.

Thanks.

Do unsuccessful pings time out, or give a message?

Does 'route print' command on the member server and a client machine reveal
anything?
--
Regards,
Newell White


"Charlie M" wrote:

> We have a muti-homed W2K member server that was upgraded to Windows Server
> 2003 R2. NIC # 1 is for internal users on the LAN, the other NIC # 2 is set
> up to use the DHCP Service to provide ip addresses for visitors to access the
> Internet. Once I upgraded the server to 2003 the DHCP clients can no longer
> access the internet.
>
> NIC # 2 (assigned to DHCP) has 2 ip addresses, the first is a valid IP
> address, say, 66.151.154.8 the second is 192.168.168.1
>
> A PC connected to NIC #2 will receive the correct ip info by doing an
> ipconfig /release and then an ipconfig /renew. I can then do a ping to
> 192.168.168.1 and also ping 66.151.154.8, but I cannot ping past 66.151.154.8.
>
> I have set the IPEnableRouter registry setting to 1, and do not have RAS
> enabled.
>
> From the member server I can ping the web and also ping any DHCP clients. I
> cannot ping a DHCP client from any other LAN PC other then the member server.
>
> What am I missing.
>
> Thanks.
>
>

Newell,

Thanks for the reply. Here is the route prints. The first one is from the
workstation the second one is from the server.

67.151.154.6 and 192.168.168.1 are the server ips

192.168.168.40 is the PC ip.

C:\Documents and Settings\Administrator.FMEW>route print
Interface List
0x1 ........................... MS TCP Loopback interface
0x10003 ...00 08 02 1d 73 79 ...... Intel(R) PRO/100 VM Network Connection

Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.168.1 192.168.168.40 20
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.168.0 255.255.255.0 192.168.168.40 192.168.168.40 20
192.168.168.40 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.168.255 255.255.255.255 192.168.168.40 192.168.168.40 20
224.0.0.0 240.0.0.0 192.168.168.40 192.168.168.40 20
255.255.255.255 255.255.255.255 192.168.168.40 192.168.168.40 1
Default Gateway: 192.168.168.1
Persistent Routes:
None

C:\Documents and Settings\Administrator.FMEW>route print

IPv4 Route Table
Interface List
0x1 ........................... MS TCP Loopback interface
0x10003 ...00 02 a5 40 26 58 ...... HP NC3123 Fast Ethernet NIC
0x10004 ...00 08 02 a2 ec b3 ...... HP NC3163 Fast Ethernet NIC

Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 67.151.154.2 67.151.154.6 1
67.151.154.0 255.255.255.128 67.151.154.6 67.151.154.6 1
67.151.154.6 255.255.255.255 127.0.0.1 127.0.0.1 1
67.255.255.255 255.255.255.255 67.151.154.6 67.151.154.6 1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.168.0 255.255.255.0 192.168.168.1 192.168.168.1 20
192.168.168.1 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.168.255 255.255.255.255 192.168.168.1 192.168.168.1 20
224.0.0.0 240.0.0.0 67.151.154.6 67.151.154.6 1
224.0.0.0 240.0.0.0 192.168.168.1 192.168.168.1 20
255.255.255.255 255.255.255.255 67.151.154.6 67.151.154.6 1
255.255.255.255 255.255.255.255 192.168.168.1 192.168.168.1 1
Default Gateway: 67.151.154.2
================================================== =========================
Persistent Routes:
Network Address Netmask Gateway Address Metric
67.151.154.111 255.255.255.255 192.168.0.1 1

C:\Documents and Settings\Administrator.FMEW>
C:\Documents and Settings\Administrator.FMEW>
"Newell White" wrote:

> Do unsuccessful pings time out, or give a message?
>
> Does 'route print' command on the member server and a client machine reveal
> anything?
> --
> Regards,
> Newell White
>
>
> "Charlie M" wrote:
>
> > We have a muti-homed W2K member server that was upgraded to Windows Server
> > 2003 R2. NIC # 1 is for internal users on the LAN, the other NIC # 2 is set
> > up to use the DHCP Service to provide ip addresses for visitors to access the
> > Internet. Once I upgraded the server to 2003 the DHCP clients can no longer
> > access the internet.
> >
> > NIC # 2 (assigned to DHCP) has 2 ip addresses, the first is a valid IP
> > address, say, 66.151.154.8 the second is 192.168.168.1
> >
> > A PC connected to NIC #2 will receive the correct ip info by doing an
> > ipconfig /release and then an ipconfig /renew. I can then do a ping to
> > 192.168.168.1 and also ping 66.151.154.8, but I cannot ping past 66.151.154.8.
> >
> > I have set the IPEnableRouter registry setting to 1, and do not have RAS
> > enabled.
> >
> > From the member server I can ping the web and also ping any DHCP clients. I
> > cannot ping a DHCP client from any other LAN PC other then the member server.
> >
> > What am I missing.
> >
> > Thanks.
> >
> >