I wouldn't reinstall Win2k if I were you. It looks very unlikely that the problem could be caused by anything at the PC end.

I'd give Roger a chance to read the thread again before resorting to anything like that.

When you tested the Receiver with the friends machine was it on your network ?

No, we used a switch that was only connected to his PC and the receiver. At home, he has a very similar setup though. He has the same router (possibly different firmware). I did not try my receiver on his home network. I may buy a Ethernet cross-over cable to try a direct connect to my PC. Do you think that is worth it?

I think I'd wait and see what Roger has to say. Then again, a cross over cable always comes in handy anyway...

I'd give Roger a chance to read the thread again before resorting to anything like that.

I'm already reading the thread.

For some reason that I can't fathom the Receiver never does the UDP broadcast to find the server.

It's just that I've come to more or less the same conclusion as you. The only thing that I can think of is that the Receiver is sending the packet, but it's being dropped by the router. However, this makes very little sense, since Ethereal (presumably running on the host Win2k box) is seeing the DHCP packets.

Could we recap the OP's network topology? Maybe there's something important that I'm missing.

Then again, a cross over cable always comes in handy anyway

Well, a cross-over cable would come in handy, but I'm not sure if Win2k's automatic link detection will play nice with the Receiver.

It's worth a try -- we need to take the router completely out of the equation.

Configure the 2k box for static IP, and try it with a cross-over cable. Alternatively, get hold of a 10Mbps hub from somewhere, and try with that.

I don't know of anyone with a Linksys router, otherwise I'd investigate the DHCP server on that.

I'm already reading the thread.

I know, you just hadn't had chance to read and respond to the latest details. I didn't want the OP reinstalling Win2k til you had had time to read the latest posts.

The only thing that I can think of is that the Receiver is sending the packet, but it's being dropped by the router. However, this makes very little sense, since Ethereal (presumably running on the host Win2k box) is seeing the DHCP packets.

Could we recap the OP's network topology? Maybe there's something important that I'm missing.

As I understand it things are real simple:

-1 receiver
-1 Win2k PC (with Zone Alarm, but turned off in these tests)
-1 LinkSys WiFi switch/router (but in these tests the PC and Receiver are both just plugged into the switch)

Router is using 192.168.1.0
PC using 192.168.1.100
Receiver given 192.168.1.101

Netmask on PC and Receiver 255.255.255.0, don't know about the router but I assume that is also 255.255.255.0

Not a setup that should really be causing a problems.

since Ethereal (presumably running on the host Win2k box) is seeing the DHCP packets

A worry is that Zone Alarm might be hiding packets from Ethereal, even when it is turned off. I don't know which hooks into the network stack at the lowest level.

I don't know of anyone with a Linksys router, otherwise I'd investigate the DHCP server on that.

I can't be the DHCP on the LinkSys at fault. The Ethereal traces have been run both using DHCP on the router and using ARM's DHCP. The failure has been the same in both cases.

I uninstalled Zone Alarm about a week ago. The router is using 192.168.1.1. The router is using the same netmask (255.255.255.0).

It can't be the DHCP on the LinkSys at fault.

No. Fair point. What I meant to suggest is that possibly the router is dropping the packets on the floor. I don't know why it would, but until it's taken completely out ot the equation -- either by using a cross-over cable or a hub, it can't be discounted.

Actually, thinking about it, Hugo uses a Linksys router on his cable. His Receiver works. I'll ask him if his network topology is particularly different from this one.

Actually, thinking about it, Hugo uses a Linksys router on his cable. His Receiver works. I'll ask him if his network topology is particularly different from this one.

Don't forget however that the underlying hardware/firmware of LinkSys routers varies as they are not all designed by the same manufacturer. You would need to know that they were similar models of router to compare them sensibly.

It's a BEFSR41 with the latest firmware, if that helps...

Hugo

I am using a BEFW11S4 v.2 with the latest firmware

OK, I'm not following this thread closely but wanted to let you know that:

I've got several linksys switches with Receivers (five currently) connect with no problems. I've got a linksys 5port, 8port, 16 port and a linksys cable/dsl router with no problems at all.

I'm at work so I can't give any real details of the model numbers but can if needed.

Good luck.

Well, a friend gave me an old Win98 PC to mess around with and it worked. Not sure what is wrong with my Win2K box, but I think it needs to be cleaned up. Thanks for all of your help.

I reinstalled Win2K this weekend and now it works perfectly. Thanks for all of your help.