DHCP problems using 3com OfficeConnect

[Punce]

I've configured an OfficeConnect Remote 531s as a DHCP server with the following settings:

Start address: 192.168.10.10
End address: 192.168.10.20
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.10.1

If I then connect a 95/98/NT workstation to the LAN, I inherit the correct IP settings.

However, when I connect a Windows 2000 Pro workstation to the LAN, I inherit the following IP settings:

IP address: 192.168.10.10
Subnet Mask: 255.0.0.0
Default Gateway: -

There must be a difference in the way 2000 obtains a DHCP address, and the 3com router can't deal with it.

Any ideas anyone?

 

[MattWray]

Did you try a release/renew and see what happens? Matt Wray
CCNA, MCP
mwray77518@yahoo.com

 

[Punce]

Oh yes. As you can see it obtains the correct IP address, it just doesn't seem to obtain any other setting! Very odd.

Thanks

 

[Punce]

bump

 

[Firm]

It's likely that there is a problem with the NIC. Try a different NIC?

 

[echoecho]

is the card set up for DHCP. Verify that it is not set for static.

 

[Punce]

It's definitely set up for DHCP. If I connect the Win2K workstation to my NT LAN, I get the correct setting from my NT DHCP server.

But then I disconnect the Win2K from the LAN, and simply connect it straight into the 3com Router (crossover cable connecting them together) I get the above problem!

I've posted this problem on the 3com Routers forum also, but I'm doubting whether anyone reads that thread.

Thanks for your replies.

 

[echoecho]

Why are you using a crossover cable?

 

[MattWray]

I second Echo, I don't think you should be using a cross-over for that. Matt Wray
CCNA, MCP
mwray77518@yahoo.com

 

[Punce]

It actually doesn't matter which cable you use, as the OfficeConnect has a MDI/X switch on the back.

A crossover cable was the closest to grab at the time

And yes I have checked the link is working, I've had a telnet session through it.

I've been working with these routers for abuot 4 years now, and not had a problem with them (except for a few that have fried!) this is the most annoying bug I've seen to date