[Scott F.]

Hiya Guys,

I've got a mystery I need some help solving. Hopefully you guys can help.

A couple of months ago, I replaced my main desktop PC. Attached to that PC are my Firewire drives loaded with Flac files. I'm running a pair of SB's (3's). They are working just fine, no issues at all. When I installed the new desktop, I installed SlimServer without any issues. It pulls up just fine when I double click its icon. Next, in my listeing room, I used to use my laptop as my remote for Slimserver using the web interface. It still works just fine when I type in http://192.168.1.106:9000/ into my address bar.

So, when I upgraded my desktop, I thought I'd retire my old desktop machine to my music room and use it as my remote. Where I'm running into trouble is when I type that same web interface address (http://192.168.1.106:9000/) into the browser bar, it doesn't pull up slimserver web interface.

Now, my network interface is working just fine. I can log onto my new server and access and alter any shared file I wish. I can read the music drives. I even tried setting slimserver as a shared folder. I've turned off my firewall thinking it my be the road block but that didn't work either. I also disabled all of my virus software thinking that might help but it didn't.

I've also tried typing in slimserver IP addresses from 0 through 10 thinking that might work but it didn't. I'm running version 6.5.4 - 12568 and firmware 81.

Does anybody have any suggestions  I've got to have overlooked something simple.

TIA 

[mgalusha]

I'd start by determining the exact address of each machine. If you're running windows you can do the following

Go to the start menu, click run and type "cmd" (no quotes) in the box and hit ok (you may already know this but just in case). You will get a lovely command window. Type ipconfig and hit enter. It will return the ip address of the machine. Do this on each machine to be sure there are no conflicts. Usually the OS will complain if there is but it's good to check. This way you will know for sure that your server is 192.168.1.106. If all the addresses are as expected try this from the command line on both the server and client machine: (in the same command window)

telnet 192.168.1.106 9000 <enter>
You should get a blank screen, type a "/" and hit enter and you should see something like this:

Code: [Select]

HTTP/1.1 400 Bad Request
Date: Sat, 07 Jun 2008 01:29:21 GMT
Server: libwww-perl-daemon/1.36
Content-Type: text/html
Content-Length: 57

<title>400 Bad Request</title>
                              <h1>400 Bad Request</h1>



Connection to host lost.

C:\>

If you get that, the machine is connecting to slim server and that rules out the firewall, if not something is blocking your connection. If you get it and can't connect with the browser then you have to try and figure out why the browser won't see the site.

Don't know if this will help but it's a starting place.

mike

[Scott F.]

Thanks Mike, I'll give that one a try first thing in the morning.

[PhilNYC]

This recently happened to me while running SlimCenter 7.1.  I ended up reinstalling 7.0.1. and it worked fine.  Then I reinstalled 7.1 and it's fine again.

[Scott F.]

Thanks Phil, I'll try that one too and see if it works.

[Scott F.]

Well, I started off installing the new Slimcenter 7.0.1. I didn't realize it would be a different interface from the old. It's OK but it will take some getting used to. I'm still having the same issues though. I checked my laptop and I connect without any issues. It's this darned desktop.

Mike, I did the telnet thing and on my new desktop it came up and acted just like you said it would. When I do the old desktop (which used to be my server), it times out on a bad connection. I tried pinging ....106... and it rejected all of the packets. Not really sure if a ping works  on Slimcenter but I tried it anyway.

I've got everything shut off as far as virus, internet and firewall protection on the new server. I also went in to my Linksys wireless router software and made sure that that it recognized the old server and wasn't blocking anything.

Could there be some switch in XP on my old machine that would block the connection? Reason I ask, that machine used to be the server and now its just another PC on the network. Maybe it still thinks its a server or something weird like that. That or some obscure administrative switch that I don't know about?

Another question, do I need to run Slimcenter on both machines? I guess thats easy enough to try. I'll download and install it to see if that is th hang up.


....hmmmmmmm    Any other suggestions?

TIA

[JEaton]

If .106 was the IP address of the old server machine then it's very unlikely to now be the address of the new one.  As Mike suggested, what are the results of Start > Run > "cmd" > "ipconfig" on _each_ machine on your network?  It's important to know the IP address of each computer.  You have to know the IP address of the new server before you can connect to it.

SlimServer doesn't need to be running on the machine you're using as a "remote".  In fact, to avoid confusion you should uninstall SlimServer on the old server.  At the very least, make sure it's shut down.

Don't do anything else until you figure out the IP address of the new server.  You're just going to be chasing your tail if you keep changing two things at a time while you troubleshoot the problem.

[Papajin]

Is it possible you're hard-coding the IP address of the old machine and it's the same as the new server?  I'd check the IP's of all machines and  make sure they're all Unique, and then make sure they're all similar.  For instance, if your new server is 192.168.1.106, but the old server is 10.0.0.1, you'll never be able to connect. 

Another possible thing to look for is if you're using a router, make sure you didn't hard code any IP's there.  For instance, I use DHCP on all my computers to get an IP assigned from my router, but I've set some machines up to always get the same IP from the router (using the MAC address).  Assuming you didn't change anything else in the configuration of the old machine, and it was functional on your network, a conflict of some sort may be likely.

Does the old machine have ANY network connectivity at all?  Can it ping other machines?

[Scott F.]

Thanks for the replies guys.

I double checked the ip addresses of both machines. The new server is 192.168.1.106 and the old machine is ....108. I haven't hard coded my router with any addresses, I let each machine negotiate the addy's automatically. When it comes to talking to the other machines on th  network, yes, I can log onto my new server and navigate, save or alter files without any issues. I just pinged it to make sure...no packet loss. It's when I type in http://192.168.1.106:9000/ to access Silmserver that it cames back as a failure to connect.

This is a weird one. I can even pull up Slimserver on my phone but not on my old machine.

[JEaton]

This is a weird one. I can even pull up Slimserver on my phone but not on my old machine.

The only thing I can really think of would be some kind of firewall issues.

Once you get the problem figured out you might want to look into how you can be sure your SqueezeCenter server always has the same IP address.  If you let the machines pull IP addresses through DHCP then they could end up with different addresses at some point (usually they'll keep getting the same IP address from the DHCP server, but not always).  When that happens, you'll end up going through the exercise of figuring out IP addresses all over again.  There are two ways to fix the address of the server: 1. assign it a static IP address (outside of the DHCP pool of addresses), or 2. Use the DHCP server to create a IP address reservation for the machine, which is done by correlating the unique MAC address of the computer's network card with the desired IP address.

[Papajin]

I'm still unclear whether or not the old server is capable of talking to any other machine in any fashion, whether it be a ping, traceroute, or anything else.  There has to be something fundamental wrong that we're just not seeing.  Did you check the IP configuration of the old server to see if anything is missing?