[bpape]

The conflict is resolved.

I'd love to ping the router - but that requires knowing it's IP address - which we don't.  I did try pinging 192.168.0.1 and 192.168.1.1 (default for Linksys usually) and neither worked. 

Bob

When you get home tonight, try resetting the router to it's factory defaults

Instructions:

To reset the router via its web-based setup page, follow the steps below.

Resetting the Router Using the Web-Based Setup Page

Step 1:
Access the router’s web-based setup page. For instructions, click here.

Step 2:
When the router’s web-based setup page appears, click Password then select Yes on the Restore Factory Defaults option.

Not only should this reset the IP of the router to 192.168.1.1 but it should also bring up the setup page so we can see what's happening.

Bryan

[Bob in St. Louis]

Step 1:
Access the router’s web-based setup page. For instructions, click here.

When you say "the routers web-based set up page", do you mean here:
http://linksys.custhelp.com/cgi-bin/linksys.cfg/php/enduser/std_adp.php?p_faqid=3978&lid=9431637401B07

It looks like this:
=========================

There are two ways to reset the router to factory default, by pressing the Reset button of the router and resetting through the router’s web-based setup page. Pressing the Reset button on the back of the router for 30 seconds will reset your router to its factory default settings. Any settings on the router will be erased. The router’s IP address will become "192.168.1.1" and the password will be “admin”.

NOTE: Take note of the current settings of the device before resetting.

[bpape]

When you do that (hold the reset), according to the site, you'll get a screen to confirm (if you're connected).  Either way, we'll KNOW what the IP address and uname/pwd are for the router.

Bryan

[Bob in St. Louis]

Well that sounds easy enough.....
All I gotta do is push a button and write some numbers down.
Hell, not even I can screw that up. 

I'll let you know tonight when I get home. 

Bob

[bpape]

After you do the hard reset like that - just go do the DOS prompt and type:

PING 192.168.1.1 and hit ENTER

If it comes back with addresses and return times, we're getting somewhere.  If not, then it could either be a bum router or a bum cable as has been suggested.

There have been a few instances of routers getting 'stuck'.  In that case, you hold the reset for a minute and at the end of the minute, keep holding it while you unplug from the wall.  Leave it unplugged while holding the reset and plug back in.  After 30 seconds release it.  Seems odd but that's right from the Linksys support forum.

If you have to do this second part, you'll need to repeat the PING afterward.

Bryan

[Bob in St. Louis]

Alright, good deal. I can manage that.
I'm half tempted to call my wife at home right now and have her do it. Just so I can have "instant results", but that will do nothing more than frustrate her and I both. 

Bob

[Bob in St. Louis]

I'm typing this post as a "play by play" of what I do and the results. So it may seem a bit choppy.

When you do that (hold the reset), according to the site, you'll get a screen to confirm (if you're connected).  Either way, we'll KNOW what the IP address and uname/pwd are for the router.

Nope. Nothing.
No screen popped up. I was connected to the net at the time(obvious, since I'm posting here now) if that makes a difference.
The "happy lights" went out, the power LED started blinking and never stopped.
I pulled the routers plug (110v). Plugged it back in, "Happy lights" back on.

After you do the hard reset like that - just go do the DOS prompt and type:
PING 192.168.1.1 and hit ENTER
If it comes back with addresses and return times, we're getting somewhere.  If not, then it could either be a bum router or a bum cable as has been suggested.

Nothing.
PING 192.168.1.1
"32 bytes of data"
"Request timed out"
Dead

There have been a few instances of routers getting 'stuck'.  In that case, you hold the reset for a minute and at the end of the minute, keep holding it while you unplug from the wall.  Leave it unplugged while holding the reset and plug back in.  After 30 seconds release it.  Seems odd but that's right from the Linksys support forum.
If you have to do this second part, you'll need to repeat the PING afterward.

I took you literally when you said "a minute", and held the reset button for 60 seconds. ----> Pulled the plug. ----> Counted to 30 ----> continued to hold the reset while plugging unit back to 110v. ----> watched 30 seconds click by.
Nothing. The "Happy power LED" continues to blink away into oblivion.
I pulled the 110V and reconnected. Happy lights back on.
-Each time the router was reconnected to 110v, the SqueezeBox responded with a message that it can't connect.
-Repinged;
PING 192.168.1.1
"32 bytes of data"
"Request timed out"
Dead

I tried a new ethernet cable.
Repinged 192.168.1.1:
"32 bytes"
"Request timed out"
Still dead

Connected ethernet cable to different 'output' port on router.
Repinged 192.168.1.1:   
"4 packets sent = 4 packets received"

So I pressed the SB remotes power button:

"Waking up SlimServer"..........
"Connecting to SlimServer".........
......display goes black. 

Damn.
Done for the night.
See you in the morning.

Bob

[richidoo]

Connected ethernet cable to different 'output' port on router.
Repinged 192.168.1.1:  
"4 packets sent = 4 packets received"

The SB can't connect because it still has the wrong IP address, and/or is still on a different network from the router, so they can't see each other. Now with the router hopefully working, you can try setting up DHCP in the router, if it's not already on by default. subnet mask is 255.255.255.0, router ip stays 192.168.1.1 and your DHCP range can be 192.168.1.100 - 150, that may be the stock setting. Then you just reboot the PC and the SB so they can get new IP addresses from the hopefully now working router.  Go through the SB setup again, select DHCP for a new IP address and pick the slimserver host by host name, not IP.

The fact that one switch port is dead, and the DHCP server in the router was or still is borked, strongly implies the router is the cause of your problems. When I saw the picture of Linksys above I smiled, I have lost 3 of them in 8 years. They really are disposable, it is sad because they are soooo pretty! Maybe try Dlink or another brand next?
Good luck Bob
Rich

[Bob in St. Louis]

Then you just reboot the PC and the SB so they can get new IP addresses from the hopefully now working router.  Go through the SB setup again, select DHCP for a new IP address and pick the slimserver host by host name, not IP.

IT'S ALIVE ! 

This morning I rebooted the PC and yanked the plug on the SB.
It works!
Strangely enough, I did not have to go through any set-up procedure.
Should I? ........ Or should I leave it alone?

The VU meters on the SB happily swinging away. 

Thanks guys, 

Bryan, you wanna come over NOW? aa I promise I won't put you to work this time. 

Bob

[ecramer]

Then you just reboot the PC and the SB so they can get new IP addresses from the hopefully now working router.  Go through the SB setup again, select DHCP for a new IP address and pick the slimserver host by host name, not IP.

IT'S ALIVE ! 

This morning I rebooted the PC and yanked the plug on the SB.
It works!
Strangely enough, I did not have to go through any set-up procedure.
Should I? ........ Or should I leave it alone?

The VU meters on the SB happily swinging away. 

Thanks guys, 

Bryan, you wanna come over NOW? aa I promise I won't put you to work this time. 

Bob

Yea  better get some cold one's for Bryan

[Bob in St. Louis]

Yea  better get some cold one's for Bryan

And a big wet sloppy kiss.   
I'd give one to Rich too, but he's too far away. 

Bob

[bpape]

Well, resetting the router at least got to the point where we KNOW what it is if there are any future problems.  

Just out of curiosity, what does SlimServer say it's IP address is at the bottom of the main networking page.  Is it still the external IP address?

I know I at least left it in a condition where it was POSSIBLE for it to work (no conflicting IP's, all on same 192.168.1.xxx, router assumed to be default 192.168.1.1, etc.

Whatever the reason, good deal that you're back up and functional again.

Will have to see - might be able to drop over sometime next week.  Gotta get some more of those IB subs you got cookin' in there

Bryan

[Bob in St. Louis]

The unit has been renamed and now refers to itself as "192.168.1.100".
Server IP address: 172.170.9.104

A huge thanks to all you guys for helping. Again, especially Bryan for the house call.

I'm sure you know I was joking about the big wet sloppy kiss. Homey really don't play 'dat. 

Next week sounds fine Bryan. (except Saturday the 16th, I have to work).

I'll have the Infinite Baffle warmed and ready. Eagerly looking forward to your impressions, thoughts and comments.

Bob

[WGH]

Great trouble shooting guys 

Wayne

[Len_Dreyer]

Good work all. This was a bit of a mindf**k, especially with the modem hookup. Consider making this thread a sticky. There is a lot of good info here.

One way of troubleshooting the integrity of the network, if the slimserver/pc is flaking out, is to test whether the SB3's internet radio is working, but with the PC modem setup????

[Bob in St. Louis]

One way of troubleshooting the integrity of the network, if the slimserver/pc is flaking out, is to test whether the SB3's internet radio is working, but with the PC modem setup????

Having a dial-up internet connection required me to have an internal 56k modem. Therefore, the router is #3 in the chain. (#1=PC, #2=Modem, #3=Wireless Router, #4=SB)
Internet radio and all the cool streaming things the SB can do are unavailable to me. That would work for folks with highspeed, but for those of us that live amongst the trees and crickets, we're screwed regarding that method of troubleshooting.

Otherwise, yea...It was indeed a head scratcher for a few days. I was beginning to have withdrawl symptoms.

Thanks Wayne and Len.

Bob