I'm having an interesting DHCP problem that I would like to hear if anyone
has encountered before.

I have a 3640 with IP/IPX/Plus 12.0.7T feature set on. I need to use the T
track because I have a Fast ethernet channelized T1 module. A Novell 4.2
DHCP server is on this side.

I have a 1750 with 12.0.5 (XK train I think) IP/IPX/Plus feature set.
Windows 95 clients with Novell Netware Client (ver 3.2 some with updates and
some without) are on this side.

If I turn routing off, and only bridge, the clients can get a DHCP address
from the server. If I try to route IP and IPX (or IP only for that matter),
the clients can log onto the Novell server (IPX is required for login, not
IP) but dont get a DHCP address.

I know the ip helper is configured correctly, I tried forwarding to both the
server itself and to the subnet. BOOTP is forwarded by default, although I
did try entering ip forward protocol as well.

When the client tries to renew the address with winipcfg.exe, they get an
access denied message. I think this is the key, but I have never seen a
access denied message on Win9x. When the routers are bridging, the clients
can renew with out the access denied message.

I have confirmed that the DHCP server is getting the request and sending a
response with a sniffer. When I debug ip udp on the 1750, I see the both the
request and the response from the DHCP server, and I see a packet going from
the ethernet interface on the router to the DHCP client address, but there
is no ACK or accept message coming from the client.

Has anyone seen this before? I have tried 3 different software images
(12.0.4T ip/ipx/plus, 12.0.7T ip/ipx/plus, and 12.0.7T ip/ipx) with the same
results.

I appreciate any ideas that people would send my way

Scott Meyer
CCNA, CCDA, MCSE, etc
[EMAIL PROTECTED]

___________________________________
UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html
FAQ, list archives, and subscription info: http://www.groupstudy.com
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Reply via email to