Hi,
I can not seem to get my SB3 to connect to my slim server. Help.
What works:
Connect to Squeeze Network: - Internet Radio, Pod Casts etc
Wired mode or wireless
What does not work:
I Can not connect to slim server. The set up will find the computer, but not connect to the server which is running in either wired or wireless mode. (Actually this worked once for about three lovely hours, but not since!)
Your thoughts on how to get this working are welcomed.
About my set up:
Server:
Win XPHome sp2, NO FIREWALL (turned off via services)
Slim Server 6.5.4
From server machine I can PING squeeze box
Wireless Access Point / Router:
DLINK DI-525 Rev “C”, firmware 323, broadcast in G mode only.
Encryption WPA2 Personal
Squeeze Box 3:
IP via DHCP – no problems
Squeeze Box find’s the server
Wireless Strength GT 70%
No Wireless Bridge
Firmware v 81
For some reason I suspect the DI-524. Are there any known issues with this Router/WAP? Is there a Router/WAP that has seems to work faithfully?
tia,
Results 1 to 3 of 3
-
2008-01-05, 22:30 #1Junior Member
- Join Date
- Jan 2008
- Posts
- 2
SB3 "Can't connect to slim server"
-
2008-01-06, 04:22 #2Junior Member
- Join Date
- Jan 2008
- Posts
- 1
I had a nightmare setting up my SB3. Everything worked until step to allocate IP automatically and then it just wouldn't progress. Luckily I had an experienced friend who already owned a SB and did some work on my PC. Turns out it's the router that's faulty. Here's how he diagnosed the problem:
1. Tried to install out of box, failed as described above.
2. My router was using 128-bit WEP encoding, so he decided to turn that off. No encryption.
3. Tried installing again. Worked perfectly! (Therefore it's about the router, not the software or SB3.)
4. Turned on 64-bit WEP. Connected perfectly again!
5. Changed the router settings to WPA encryption instead of WEP. Reinstalled, and everything worked properly.
6. Went back to 128-bit WEP. Guess what? Failed to connect.
So he deduced that something was up with the router which only affected 128-bit WEP. The solution was to switch the router to WPA.
Outcome: SB3 works perfectly now. My router uses better encryption method (I should have changed it to WPA years ago apparently, since WEP is so easy to hack!). The only slight issue was that I had to go around the house re-setting all the wireless hardware to connect using WPA -- e.g. Wii, laptop, palm, etc.
SB3 really should work out the box. If you ave connection problems suggest you disable encryption to see if it's to do with that.
-
2008-01-11, 08:26 #3Junior Member
- Join Date
- Jan 2008
- Posts
- 2
Fixed
I have identified the problem through a painful process of isolating components between SB3, Router and Server
It turns out that I had interference on my NIC (wired and wireless) on my server. The interference was caused by a Symantec VPN Client software package. In windows, “un-checking” the item (accessed by Properties General Tab) immediately fixed the problem. As I no longer require the VPN on my system, I have uninstalled it.

Reply With Quote
