Home of the Squeezebox™ & Transporter® network music players.
Page 1 of 4 123 ... LastLast
Results 1 to 10 of 34
  1. #1
    Junior Member
    Join Date
    Dec 2005
    Posts
    23

    I spent 9 hours trying to setup slimserver with no avail...

    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/messa...79/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/9...overnet4ao.jpg

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

    http://img504.imageshack.us/img504/2...paccess7gt.jpg

    But is it?

    http://img504.imageshack.us/img504/9...ortnogo4ps.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

  2. #2
    Senior Member
    Join Date
    May 2005
    Location
    In a house
    Posts
    1,629
    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.

  3. #3
    Junior Member
    Join Date
    Dec 2005
    Posts
    23
    "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.

  4. #4
    Senior Member
    Join Date
    Apr 2005
    Location
    Colorado
    Posts
    10,073
    Quote Originally Posted by mangotbg
    You would think with the proper port forwarding all would be peachy:

    http://img504.imageshack.us/img504/2...paccess7gt.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?

  5. #5
    Junior Member
    Join Date
    Dec 2005
    Posts
    23
    Quote Originally Posted by JJZolx
    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.

  6. #6
    Junior Member
    Join Date
    Dec 2005
    Posts
    23
    http://img510.imageshack.us/img510/4153/updated6gi.jpg

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

  7. #7
    Senior Member
    Join Date
    Apr 2005
    Posts
    135
    > 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.

  8. #8
    Junior Member
    Join Date
    Dec 2005
    Posts
    23
    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

  9. #9
    Senior Member
    Join Date
    May 2005
    Location
    In a house
    Posts
    1,629
    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?

  10. #10
    Senior Member
    Join Date
    Apr 2005
    Location
    Colorado
    Posts
    10,073
    Quote Originally Posted by mangotbg
    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.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •