PDA

View Full Version : I spent 9 hours trying to setup slimserver with no avail...


mangotbg
2005-12-16, 14:02
I'm JUST waking up because I didn't fall asleep until 7:30AM (it's 3PM EST right now) or else I would have posted this sooner. I was too exhausted to post earlier.

Anyways enough of my sob story ;)... on to where I need to enlist your help!

I first came across this website:

http://forum.ecoustics.com/bbs/messages/34579/138845.html

I followed this guide to setup slimserver on my desktop machine. The machine is running Windows XP Pro SP2.

As seen by this screencapture I have gotten the server to work on the desktop:

http://img286.imageshack.us/img286/20/inaction6ge.jpg

The problem that I have is that I can't connect to the server from another PC.I setup my DNS w/ dyndns.org and I feel I've done so properly as seen here:

http://img504.imageshack.us/img504/9508/linksysovernet4ao.jpg

You would think with the proper port forwarding all would be peachy:

http://img504.imageshack.us/img504/2716/laptopaccess7gt.jpg

But is it?

http://img504.imageshack.us/img504/9118/addportnogo4ps.jpg

Nope. Notice the ssh port...I spent one of those hours alone trying to get that working gave up after realizing what's the use? I can't even connect regularly...possibly a wasted hour, but I still wouldn't mind having ssh once I do eventually get this software working.

I've tried allowing *.*.*.* for the IP, I've tried everything I could think of down to exact IPs...I don't know if this might be where my problem is? I find it odd that you list without spaces, atleast that's how they show it...

http://img161.imageshack.us/img161/1968/ipconfig2xz.jpg

As far as my firewall, I run F-Secure Internet Security 2006. I've tried every combination of running without the firewall running, allowing all UDP TCP connections, allowing slimserver as a program filter. I tried this for both the desktop and laptop.

http://img130.imageshack.us/img130/4944/firewall7sg.jpg

I've also tried connecting to a neighbors wifi network to access the server with no luck.

I think that about does it. This post took me one hour to produce, so maybe that shows you just how maticulous I have been with this installation. I just don't understand why I can't access the slimserver. I'm thinking it's some silly mistake of mine, that's why I'm showing you guys everything in hopes that you can find my mistake! Thanks in advanced!

Manny

MrC
2005-12-16, 14:17
it looks like you have several things assigned to port 9000. Thats a no-no. Just one service can be assigned and forwarded.

Move your Webcam at 9000 in your port forwards elsewhere, or else reassign slims 9000 to somethign else. I think I see that you also have itunes assigned to 9000. Again, you can't do this.

You need 9000 TCP and UDP for slim.

mangotbg
2005-12-16, 14:25
"webcam" and "itunes" are just names, if you look closely I'm forwarding both UDP TCP on port 9000. Regardless, I get the same results whenever I select "BOTH" on forwarding port 9000 on just one entry (i.e. if I were to remove "webcam" and replace "UDP" with "BOTH") I get the same results. It just so happens the last thing I did was try to seperate them and see if it works. Had I taken that screen cap earlier it would have shown this.

JJZolx
2005-12-16, 14:27
You would think with the proper port forwarding all would be peachy:

http://img504.imageshack.us/img504/2716/laptopaccess7gt.jpg
Is port-forwarding through your router the only thing that is _not_ working? You're playing music through the Squeezebox, right? Can you access the web server from another PC on your network behind the router? If so, can you also run SoftSqueeze on that other PC?

I'd skip the DynDNS stuff until you have port forwarding working properly. Until then, just address the machine by whatever external IP address your router has been assigned.

What are the "webcam" port forwarding entries in the LinkSys screenshot? Are these just misnamed or do you have another service running on the same PC that listens on the ports that SlimServer uses?

mangotbg
2005-12-16, 15:48
Is port-forwarding through your router the only thing that is _not_ working? You're playing music through the Squeezebox, right? Can you access the web server from another PC on your network behind the router? If so, can you also run SoftSqueeze on that other PC?

I'd skip the DynDNS stuff until you have port forwarding working properly. Until then, just address the machine by whatever external IP address your router has been assigned.

What are the "webcam" port forwarding entries in the LinkSys screenshot? Are these just misnamed or do you have another service running on the same PC that listens on the ports that SlimServer uses?

it's just misnamed. It was for my webcam that I had forwarded to a dyndns a couple months ago, so I know port forwarding works...just not now? As for accessing it on the network, I can't. I type in 192.168.1.100:9000 and I get that same issue, it times out or doesn't respond in time. I can't access it on the network or from oustide the network? I dont actually have that $300 item I'm just using this to serve pc to pc.

mangotbg
2005-12-16, 15:57
http://img510.imageshack.us/img510/4153/updated6gi.jpg

Updated just to show you I've tried...

bishopdonmiguel
2005-12-16, 16:00
> Updated just to show you I've tried...

From what I can see, you are forwarding to 192.168.1.100 but your computer IP is 192.168.1.101, so the traffic is being forwarded into oblivion.

mangotbg
2005-12-16, 16:01
I just noticed I took that last screenshot from my laptop..that's why it says 192.168.1.101 and not 192.168.1.100. I thought I found the answer to my problem when I checked that screencap again...I thought my IP had changed...oh well

MrC
2005-12-16, 16:02
mangotbg,

I see that you have microsoft's antispyware running. Have you ensured that it is not blocking access? Try shutting it down.

What happens when you run

telnet 192.168.1.100 9000
?<Enter>

from a command window on your other PC?

JJZolx
2005-12-16, 16:03
it's just misnamed. It was for my webcam that I had forwarded to a dyndns a couple months ago, so I know port forwarding works...just not now? As for accessing it on the network, I can't. I type in 192.168.1.100:9000 and I get that same issue, it times out or doesn't respond in time. I can't access it on the network or from oustide the network? I dont actually have that $300 item I'm just using this to serve pc to pc.
Until you can get to the server from _behind_ the router using http://192.168.1.100:9000 then it's premature to test port forwarding and access from outside your network. Cuz it won't work.

You mentioned running F-Secure firewall. Have you checked to see if the Windows firewall is also enabled? If so, you'll need to add port exceptions or disable Windows firewall.

mangotbg
2005-12-16, 16:06
http://img365.imageshack.us/img365/7038/newnewupdate6yd.jpg

The first one says "wireless network"...this is my desktop network status page.

mangotbg
2005-12-16, 16:29
mangotbg,

I see that you have microsoft's antispyware running. Have you ensured that it is not blocking access? Try shutting it down.

What happens when you run

telnet 192.168.1.100 9000
?<Enter>

from a command window on your other PC?

This is what happens:
http://img510.imageshack.us/img510/7699/telnet1pb.jpg

Even when I am unprotected (and not running any other programs including antispyare).

http://img243.imageshack.us/img243/1578/unprotected6ja.jpg

JJZolx
2005-12-16, 16:38
You've posted screen shots showing the SlimServer web interface running in a browser window. I assume that the URL you're using is:

http://localhost:9000

What if, on the same machine you try to use:

http://192.168.1.100:9000

?

mangotbg
2005-12-16, 16:39
You've posted screen shots showing the SlimServer web interface running in a browser window. I assume that the URL you're using is:

http://localhost:9000

What if, on the same machine you try to use:

http://192.168.1.100:9000

?

It works. 1234567890

mangotbg
2005-12-16, 16:44
You actually bring up a good point, though...atleast you made me think of a question that hasn't been adressed from my first point:

Under Allowed IP Addresses can I do *.*.*.* and that just allow any IP address...so I wouldn't have to worry about it...right now i have like 5 ips in there just trying to cover all the bases, but I don't like that. However *.*.*.* doesn't help!

JJZolx
2005-12-16, 16:50
You actually bring up a good point, though...atleast you made me think of a question that hasn't been adressed from my first point:

Under Allowed IP Addresses can I do *.*.*.* and that just allow any IP address...so I wouldn't have to worry about it...right now i have like 5 ips in there just trying to cover all the bases, but I don't like that. However *.*.*.* doesn't help!
Do you actually have "Block Incoming Connections" enabled? You should be able to just set it to "Do not block" and not worry about the Allowed IP Addresses.

mangotbg
2005-12-16, 17:03
Do you actually have "Block Incoming Connections" enabled? You should be able to just set it to "Do not block" and not worry about the Allowed IP Addresses.


I didn't know those two options coordinated like that, but no I did not have it on "Block Incoming Connection". I have it on "Do not block" as you suggest.

I'm currently connecting the computer directly to the cable modem to see if it will work that way? That's the only thing I can think of right now...

JJZolx
2005-12-16, 17:10
I'm currently connecting the computer directly to the cable modem to see if it will work that way? That's the only thing I can think of right now...
Not sure what you'll be able to test by doing that. Obviously, _something_ is blocking access to your SlimServer. Most likely something running on the server machine itself. There's a very distant possibility that the router might be blocking traffic to the server from machines on the LAN, but most routers are configured by default to permit all LAN to LAN traffic, so that's unlikely unless you've fiddled with something there.

mangotbg
2005-12-16, 17:15
Not sure what you'll be able to test by doing that. Obviously, _something_ is blocking access to your SlimServer. Most likely something running on the server machine itself. There's a very distant possibility that the router might be blocking traffic to the server from machines on the LAN, but most routers are configured by default to permit all LAN to LAN traffic, so that's unlikely unless you've fiddled with something there.

Well, this is what I figured out by doing what I did... I can't even ping the desktop from my laptop. The laptop is connected wirelessly to my neighbor's router. My computer is directly hooked up to my cabe modem. I got a new IP address by doing so, but when I go to ping the new IP it times out? What?!?! What could be keeping my pc from being pingable?

JJZolx
2005-12-16, 17:23
Well, this is what I figured out by doing what I did... I can't even ping the desktop from my laptop. The laptop is connected wirelessly to my neighbor's router. My computer is directly hooked up to my cabe modem. I got a new IP address by doing so, but when I go to ping the new IP it times out? What?!?! What could be keeping my pc from being pingable?
A firewall can certainly do that. Did you try pinging 192.168.1.100 when both the laptop and server were on the LAN?

Back up a minute... What was the earlier screenshot showing a wireless connection with IP address .1.101? Was that on the SlimServer machine or the laptop? What exactly does you network normally look like - how is each machine connected to the router?

dean
2005-12-16, 17:24
I'd bet it's related to the firewall you've got installed on there.

I realize that it's turned off, but I've heard stories about
firewalls having to be uninstalled in order to fix similar problems.

On Dec 16, 2005, at 4:15 PM, mangotbg wrote:
> Well, this is what I figured out by doing what I did... I can't even
> ping the desktop from my laptop. The laptop is connected wirelessly to
> my neighbor's router. My computer is directly hooked up to my cabe
> modem. I got a new IP address by doing so, but when I go to ping the
> new IP it times out? What?!?! What could be keeping my pc from being
> pingable?

mangotbg
2005-12-16, 17:29
A firewall can certainly do that. Did you try pinging 192.168.1.100 when both the laptop and server were on the LAN?

Back up a minute... What was the earlier screenshot showing a wireless connection with IP address .1.101? Was that on the SlimServer machine or the laptop? What exactly does you network normally look like - how is each machine connected to the router?

192.168.1.101 is my laptop
192.168.1.100 is my desktop
192.168.1.2 is my router

My computer is connected to a hub that is connected to the router. The laptop connects wirelessly. I guess I haven't tried hooking the laptop up with RJ45.

Oh, and as "scary" as it can be to do this the computer is currently connected to the cable modem w/o any firewall...so I don't understand why I can't ping it? The laptop is behind a router, obviously, though...i dunno if that has something to do with it.

gjrhine
2005-12-16, 18:50
Why is the modem connected to the computer rather than the router?

Maditude
2005-12-16, 19:21
Why is the modem connected to the computer rather than the router?

A very good question...

mangotbg: I would highly recommend reconfiguring your network, like so:

1) Connect the cable-modem to your router's WAN port.
2) Connect the rest of your computers to your router's LAN port(s). If said router only has one LAN port, plug your computers into a switch or hub, and then the switch or hub into the routers LAN port. I'm sure you'll enjoy having all your computers able to access the internet.

That will at least get everything on the same network...
Your computers should all be getting a DHCP address from your router (might want to configure the one that will run slim-server with a static address).

mangotbg
2005-12-16, 19:39
A very good question...

mangotbg: I would highly recommend reconfiguring your network, like so:

1) Connect the cable-modem to your router's WAN port.
2) Connect the rest of your computers to your router's LAN port(s). If said router only has one LAN port, plug your computers into a switch or hub, and then the switch or hub into the routers LAN port. I'm sure you'll enjoy having all your computers able to access the internet.

That will at least get everything on the same network...
Your computers should all be getting a DHCP address from your router (might want to configure the one that will run slim-server with a static address).

As to why the modem _WAS_ connected directly to the computer was to see if I could get a ping. I couldn't. Shouldn't a computer connected directly to the modem, without any firewall *hardware or software based* be pingable by anyone else? It's not a rhetoricle question, I really think it should but it wouldn't? Wouldn't that seem as if something is off?

I'm going to try uninstalling my firewall as suggested and see if it is indeed somehow affecting the ports even though it was disabled.

mangotbg
2005-12-16, 20:12
Interesting news:

I disabled the laptop's wifi and connected to the same hub that the desktop is on (which is in turn connected to the Linksys router) using RJ45 cables.

Laptop IP = 192.168.1.102
Desktop IP = 192.168.1.100

192.168.1.102 still cannot ping 192.168.1.100

however

192.168.1.100 _CAN_ ping 192.168.1.102?

Can anyone explain this?

http://img215.imageshack.us/img215/953/ping8xx.jpg

gjrhine
2005-12-16, 20:19
Both connected to lan ports (not modem port)?

JJZolx
2005-12-16, 20:21
Interesting news:

I disabled the laptop's wifi and connected to the same hub that the desktop is on (which is in turn connected to the Linksys router) using RJ45 cables.

Laptop IP = 192.168.1.102
Desktop IP = 192.168.1.100

192.168.1.102 still cannot ping 192.168.1.100

however

192.168.1.100 _CAN_ ping 192.168.1.102?

Can anyone explain this?

http://img215.imageshack.us/img215/953/ping8xx.jpg
The laptop's ethernet port has a different MAC address than the wireless card. As far as your DHCP server is concerned the .101 address is still in use by the wireless card, so it handed out another IP address.

The reason you can ping the laptop is because the laptop isn't screwed up by some port blocking firewall software. The way most software firewalls will be configured on a desktop computer is that they will permit anything _out_, but only allow return traffic in response to an outgoing request.

mangotbg
2005-12-16, 20:39
The laptop's ethernet port has a different MAC address than the wireless card. As far as your DHCP server is concerned the .101 address is still in use by the wireless card, so it handed out another IP address.

The reason you can ping the laptop is because the laptop isn't screwed up by some port blocking firewall software. The way most software firewalls will be configured on a desktop computer is that they will permit anything _out_, but only allow return traffic in response to an outgoing request.

Is there anything I can do to fix this?

JJZolx
2005-12-16, 20:42
Is there anything I can do to fix this?
Have you uninstalled F-Secure and rebooted the PC yet?

mangotbg
2005-12-16, 20:46
Have you uninstalled F-Secure and rebooted the PC yet?


Yes I have. I am running firewall-less

I've also removed the hub that I was using. I wanted to see if maybe the hub was causing the problem. So now the laptop and desktop are both connected directed to the linksys router. Still no luck.

I'm thinking I may need a good ol' fassioned reboot. Atleast it'll give me a chance to make a bootable image so I won't have to start from scratch 6 months down the road.

Comments?

mangotbg
2005-12-16, 20:56
http://img352.imageshack.us/img352/1037/breakthrough3nv.jpg

So I decided to run CrapCleaner. Apparently F-Secure has a couple broken registry entries. However, CC can't remove them.

JJZolx
2005-12-16, 20:58
Yes I have. I am running firewall-less

I've also removed the hub that I was using. I wanted to see if maybe the hub was causing the problem. So now the laptop and desktop are both connected directed to the linksys router. Still no luck.

I'm thinking I may need a good ol' fassioned reboot. Atleast it'll give me a chance to make a bootable image so I won't have to start from scratch 6 months down the road.

Comments?
I'm about out of ideas.

What are you calling a "reboot"? You should have rebooted (restarted the PC) by now. If you're talking about reinstalling Windows, I dunno, maybe. XP seems pretty robust - I've yet to run into a situation requiring reinstallation of the OS, unlike previous versions of Windows.

JJZolx
2005-12-16, 21:00
http://img352.imageshack.us/img352/1037/breakthrough3nv.jpg

So I decided to run CrapCleaner. Apparently F-Secure has a couple broken registry entries. However, CC can't remove them.
Sure doesn't look like you've _removed_ F-Secure to me if there's still a 'C:\Program Files\F-Secure Internet Security' folder.