waiting for 127.0.0.1

[Sybull]

After yesterdays succes with been given the asnwer to my streaming dropping the signal every 90 seconds, I am now faced with another problem.

Was listening to MP3 this morning no problem. Went out. Came back and now it dosn't work. The the squeezeceter seems to have trouble finding 127.0.0.1. Sometimes it takes a minute or so to do anything, othertimes it will not display anything and just says Waiting for 127.0.0.1. I can ping 127.0.0.1 no problem

I have iuninstalled Squeezecenter totaly, re set it up, but still the same problem.

I cannot access it from any device (laptop, PSP). Is this connected to the squeezecenter network being down ? Or is it my Router (which I havn't touched) ?

[Sybull]

3 Hours later and still no joy. Only yesterday I was saying how much I was enjoying this after having had a quick and much appreciated answer. I appears I spoke to soon. I have seen others report this problem but there did not appear to be a solution (but that was back in 2007). Has anyone any idea how to get out of this ?

Thanks

[Sybull]

I have played with it and it appears as soon as I try and add any track to the playlist or anything which requires dealing with a player Squeezecenter crashes.
If I right-click on the icon in the system tray and click EXIT, the icon disappears from the system tray, but if I look in taskmanager, the squeezecenter.exe process is still running. If I run squeezecenter and do everything BUT add a track or play a track it behaves fine. Exiting the software removes it from the list of processes. But as soon as I click on the + sign or the play sign, thats it. I have tried sevral PC's as players (even trying VLC media player on the server).

It was so happy over the last few days. What have I done to upset it ????

[Tejay]

Hmmm, you must have done something wrong, please read on.
127.0.0.1 is the local host, a loopback IP-number. You can ping this, and you get an answer.

But it is mostly used as a waste bin. Everything you send to this address goes down the drain without any problem. That's why you don't see something happening anymore.

My IP-number for Squeezecenter is something like 192.168.1.###, one of the private IP-addresses.

So most likely you router is down. But how did you send these messages? If this is from your computer and the same router, it is not down.
If you working with WiFi are you not on your neighbours (WiFi-)router?

[Zaragon]

Every computer on an IP network has the IP address 127.0.0.1 which is most often known as the loopback address or localhost. The main purpose is to allow applications to talk to each other or to themselves. Most computers will respond a ping of 127.0.0.1 even if they are not plugged into a network as the 'loopback' is done within the IP stack.

Not being able to ping 127.0.0.1 essentially means a fairly serious problem with networking.

The actual IP address a computer uses in a home network is normally assigned by the router and is usually in the range 192.168.0.x or 192.168.1.x most often depending upon the manufacturer of the router. The range doesn't really matter.

Pinging the IP address of the computer issuing the ping is essentially the same as pinging 127.0.0.1 as again it is turned around internally within the IP Stack. Again if this isn't working then it means a fairly serious problem.

The real test would be to ping the address of a different computer or of the router itself.

Sometimes you do see addresses that are in the 169. range this is a self assigned address and usually indicates that the device was unable to get an IP address automatically and not having one configured picks one in that range which it believe isn't in use.

Diagnosing network problems can sometimes be difficult. Start simply, one thing that you would expect to work is a normal browser so from the server try to connect to say this forum. If this works then try connecting the browser to the SqueezeServer on the same server. You should be able to use both http://127.0.0.1:9000 or the servers proper IP address.

If the first works and the second doesn't then my first thoughts would be either a problem with SqueezeCentre or more likely a firewall configuration problem.

The trick with faulting is to take it one step at a time and keeping the tests as simple as possible.

Try the above and let us know what happens. You can also contact support who will also help you through diagnosing your problem.

[Sybull]

Thank you for your response.

I can connect to SC by typing in Http://127.0.0.1:9000 or Http://<SC_server_ipaddress>:9000 no problem. I Removed the router out of the equation and plugged the server directly into the Cable modem. The server IP address changed from 196.168.0.x to 82.34.243.x. Using both 127.0.0.1 and the new IP address both brought up SC.

I can then go about SC no problem.

SC become unresponsive if I try and connect a player. This is both a player my PSP, over the wireless network (This has worked fine before) or, with the server plugged directly into my cable modem, I use VLC media player (on the server) to pick up network stream http://127.0.0.1:9000/stream.mp3 (which has worked in the past).

Thanks again

Then I get the "waiting for 127.0.0.1.."

[Tejay]

It seems that DHCP in your cable modem or the router gives you an IP-address during the boot up time. That's why you have the 127.0.0.1 address.

What about taken of all your equipment from that cable modem, do a full reboot with that modem (turn power off, wait at least 10 seconds, turn it on). Wait a few minutes. Then plug in your equipment again.

DHCP now gives you the private IP-addresses in the range 192.168.###.###.

Hope this helps.

[Sybull]

I do make a habit of turning my router and PC off everyday and also at night. Normally, when I turn on the modem I leave it for a while before turning on my PC.

The Cable modem is a small black box with only one RJ45 socket. I am not sure if it has any sort of DHCP services in it.

Another thing I noticed is, before when everything was OK, I could click on a song to start it playing and I would see the artrwork etc appear with "playing <name of the song>". I could then go round to my PSP, connect it up to the network and the music would start. Now when I click on a song to start it playing, nothing comes up.

[Tejay]

OK, that's not it.

That nothings coming up is most likely the IP-address 127.0.0.1, everything send to that is going into the waste bin. A ping though returns information, though.

A PSP is a Playstation? Or is it personal sound processor? A pretty shaved person? I am good in those riddles, I worked for a firm with dozens of those... OK off track.

First! I translate words I see from Dutch into English, So you maybe see other words!
A try to see whether there is a DHCP working: You can open SqueezeCenter? Then at the bottom right there is an item named, probably, installation. Click on it.
Then go to the tab Status.
In the Music System Information there is: The IP-address of this music system is: ###.###.###.###ort number.

In your pc go to Start/Run... Type in the command: cmd
Do a Return.
Type in the window (MS DOS prompt): ipconfig /all
And do a Return.

If this is good, it will provide you with some information.
Amongst: Standard gateway. The first three numbers should be the same as you found in Squeezecenter.

Now google for "What's my IP-number", and the result should be quiet different than the IP-addresses you found above. If so: DHCP is working.

Then I got some questions:
You have a cable modem, and on that your PC. Right?
Where does the server fit in? How is your Squeezebox connected to the PC or Server. Is it wired, or wireless (WiFi)? Does the, eventually, server has its own IP-address?

I know, no solution. Just trying to pin point the problem.

[Zaragon]

Tejay, sorry but 127.0.0.1 isn't a wastebin it is a valid ethernet address and one often used when an application wants to talk to another process on the same computer. I don't think it does but an example would be the SqueezeCenter talking to MySQL on the same box. I believe in many implementations it is faster than using the boxes 'real' IP address.

Sybull I'm following what you have tried and it seems like the computer is at least communicating with your network. If you have another PC (any operating system) with a browser can you get to the SC using the browser on the second machine. This should work. You will need to use the DHCP assigned address not 127.0.0.1.

One thing that does concern me a little is that you mentioned that when you plugged directly into the broadband your IP address changed from 196.168.0.x to an 82. address. Did you mean 192.168.0.x which is what I might expect to see. A 196.168.0.x address is routable which means that it can go outside of your router and communicate directly on the internet this would cause difficulties in itself. If it is really 196 then I suggest that you check your router config and make it 192.

It is beginning to seem as though it is on internal SC process which is having a problem. Take a look at the logs these can be found in settings status tab. At the bottom you can access the log file and see if there is anything in there relevant.

One area that occurred to me is are you using a Linux/Unix type OS or Windows? Did you upgrade anything at the time when it failed including any OS updates. It would also be worth checking if the MySQL service/app is also running.