trouble connecting through ethernet

First off, a belated Happy Thanksgiving for those of you stateside.

On to my problem. Ok, I'm running Windows XP and beta 13 on my car player and was running Emplode beta 13 as well. I was able to use an ethernet connection to access the player just find. I had to do a reinstall of XP, however, and also got a new motherboard with onboard LAN. My old mobo also had onboard LAN for what it's worth and that's how I connected to the Rio then as well. At any rate, I reinstalled Emplode beta 13 after my reformat but for some reason it can't find my player. It just keeps looking and looking but doesn't come up with anything. The only other difference between my currenct configuration and my old one is that I have added a network card. I have a cable connection and just have it connected through there. In my old config, I would remove the cable connection whenever I needed to access the Rio and plug in the crossover cable. Now I've always got the cable connected to the network card and my crossover cable connected to my onboard LAN. Any ideas on how to troubleshoot this would be much appreciated. Thanks.

I suggest giving your "rio ethernet" port a static IP address. I have seen in Windows XP that if one ethernet card gets a DHCP address and the other cannot, the one that cannot will get a DHCP address from the "good" ethernet port.

Try giving your your rio ethernet card and the empeg a static IP with the same subnet. You will probably use 192.168.0.1 for your computer and 192.168.0.2 for your empeg. The subnet should be 255.255.255.0 on both. Since you cannot connect to your empeg through ethernet now, you will have to make this change in Emplode with a serial connection.

Ok, thanks for the tip. Hate to be a noob, but I am. How do I assign a static IP address? Did you make those numbers up? Assume I'm a moron, cause I kinda am.

Use the numbers I said in the first post. Here's what Quantum says about creating IP addresses.

If Rob's suggestions don't prove fruitful, Nikko, make sure to go through the ethernet troubleshooting steps in the FAQ, here.

Got it fixed. Thanks all for your help.