after the serial cable fiasco was resolved, i gave ethernet a shot. i got the empeg to work with a static ip address, but i cannot get dhcp to work.

i have a broadband router/hub/dhcp server. my windows 2000 machine gets its address fine, but emplode will not find the empeg unless it has a static address. not a big deal, but it just bothers me when stuff like this dosen't work:)

any suggestions?

thanks,
jeremy

oh, i wish i wish i had an empeg...

Hmm..same problem.. only I'm using a 3com officeconnect 56k (56k modem, built in internet sharing and dhcp server..) Empeg just refuses to grab a dhcp number from it...
-mark

...proud to have owned one of the first Mark I units

oh, i wish i wish i had an empeg...


sorry but you cannot send any more posts until you resolve your sig line.


Murray 06000047
____________________

Well, this is not an issue with the empeg unit itself as it does support DHCP address acquisition. The problem is in the way that emplode discovers an empeg unit that is not in the static lookup table. If you read Mike's post here, you will see that they are working on "discovery" methods, which I suspect will include DHCP allocated empegs.

When you say you have a broadband server, what do you mean (OOI) ? ADSL?

You definitely need to change your sig.

One of the few remaining Mk1 owners... #00015

This is already in the standard version of emplode. It discovers empegs by broadcasting a UDP discovery packet to the local subnet. Most routers and bridges won't forward these discovery packets. If the unit is assigned a static IP, and emplode finds it, then this is working.

If the DHCP server is assigning an IP address on a different subnet, then emplode won't find it. This is not likely to be the case with one of these home/office router boxes. If this is the problem, we've got a fix to emplode which allows you to provide a specific IP address on which to find the empeg. It'll be in the next maintenance release.

I suspect, however, that this problem is caused by a, shall we say, "difference in interpretation" of the DHCP specification between your router and the empeg. If you could capture the serial output of the empeg when it's starting up, this would be a great help when diagnosing the problem.



Roger - not necessarily speaking for empeg

Doh! The release version of the player doesn't output enough logging to diagnose DHCP problems.

What kind of router is it (i.e. the manufacturer, etc.)?

Roger - not necessarily speaking for empeg

My unit is a 3com Officeconnect 56k ; here's a link to it on 3com's site:

http://www.3com.com/client/pcd/analog/lan_features.html

-mark

...proud to have owned one of the first Mark I units

my unit is a Linksys router with a built in 4 port 10/100 hub. mine is connected to a cable modem, but is meant to work with dsl, cable, etc.

when i plug it in with serial and ethernet, and set it to dhcp for discovery options and tell it to synch, it works, but i think it is still using the serial connection, since when i restart emplode it cannot find it.

so maybe the next release will take care of the problem? it really is not a big deal for me. it works fine with a static address. just wondering if anyone else had problems with it as well.

thanks,
jeremy

12 gig, green...

Same DHCP problem here. I'm using a Win2K Server as my DHCP server. I sniffed the network and captured the DHCP packets, but don't see the problem right off. The player does a DHCP Discovery packet, the server sends an Offer packet with an IP address, then the player sends a DHCP request packet with it's assigned IP address in the ciaddr field of the DHCP packet. That's when everything stops.

I tried doing a reservation of the IP address, but still no luck. It must be something with the DHCP Request packet that isn't prompting the DHCP servers to send a reply back.

Brian Van Mondfrans

Just to throw this into the mix, I use DHCP at work on a switched 10/100 Cisco (insert word here I can't think of) network.

The empeg was on a 10MB line (the guys that wired the network a couple of years ago only connected enough of the pairs for 10MB on that port. My computer and the DHCP server (NT4.0) are both on 100MB ports.

It finds the empeg every time, no problem. I've even deleted the empegs lease and it just gets a new one.

So I know DHCP works (at least for my setup.) I'd agree with Roger, and assume that the manufacturer of your hub has taken some liberties with DHCP. Does your hub/router give any statistics on DHCP addresses it has given out? At least maybe you can see if it thinks it gave one to the empeg.

I've all sorts of experience with two distinct subnets/IP ranges issues. Is it possible that your computer thinks it's on your ISP's network, and your empeg thinks it's on the internal network? i.e. you have address x.y.z.1 and your empeg thinks it's on 10.0.0.2 (or 192.168.?.?)?

Sorry for the rambling, hope this is of some help...

-Trevor

-----
Mk 2, Green 12GB 080000349

Could you forward these details to bugs@empeg.com, and we'll set up a W2K server on our test rig to try and analyse the problem. ISTR that we've fixed a problem with W2K in the maintenance release, but it'd be good to check it.

If you could grab a packet trace, that'd be good, too.



Roger - not necessarily speaking for empeg

I encountered the same thing when I tried to use DHCP. (My DHCP server at home is an Apple Airport...hey, it was there and it was easier than writing a dhcpd.conf file for the Linux box.)

The console messages showed a DISCOVER sent, an OFFER received, and a REQUEST sent, but no ACK from the Airport, therefore no address on the empeg.

There's something about the DISCOVER from the empeg that the DHCP servers don't like, but I haven't hooked up the sniffer at home yet.



-Zandr
Mk.I #150
Mk.II #39

I have NO problems using Win2K server to assign my empeg an IP address. Actually, I just add it to one of the ports on my 5 port hub and it connects without a problem.

On my 3com Officeconnect 56k hub/modem, my dhcp is working now:) (wasn't w/ 1.0)
-mark

MK2: 36gb
Tivo: 90gb
CPU: 120gb
...I think drive manufacturers love me!