Bug 6089 – D link dir-615 wireless router incompatible with squeezebox 3

Bug 6089 - D link dir-615 wireless router incompatible with squeezebox 3

Summary:

D link dir-615 wireless router incompatible with squeezebox 3

Status:	RESOLVED WORKSFORME

Product:	SB 2/3
Classification:	Unclassified
Component:	Wireless
Version:	unspecified
Platform:	PC Windows XP

Importance:	P2 normal (vote)
Target Milestone:	---
Assigned To:	Unassigned bug - please assign me!

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2007-11-07 22:59 UTC by eric williams
Modified:	2007-12-27 12:08 UTC (History)
CC List:	0 users

See Also:
Category:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description eric williams 2007-11-07 22:59:47 UTC

I bought a new wireless n router, (d link dir-615) because my laptop was dropping connections with the old router (d link di-624).  Now the laptop doesn't drop anymore, but I'm unable to connect my squeezebox to it.  Tried b/g/n mixed mode, couldn't connect.  Tried g only, couldn't connect.  Tried unhooking the new router, and used the old router g only mode, connects fine.  I'm using wpa2 encryption, but tried wpa without any success.  

Right now as a workaround I'm running both the old wireless router and the new one, the wiring configuration is cable modem-----dir-615-----Desktop running slimserver
           |
           |
           -------Di-624

Not exactly an elegant solution, but at least I don't have to sit in silence where my squeezebox is.

Heard anyone getting this dir-615 to connect?

I'd appreciate any help.

Comment 1 KDF 2007-11-07 23:42:19 UTC

If there is a workaround, this is by definition not critical.  Please post on the forum or contact support@slimdevices.com for tips and possible solutions from other users with similar equipment.

Comment 2 Blackketter Dean 2007-12-27 12:08:02 UTC

This isn't really an acceptable workaround, but I do think that support may be able to resolve your issue.  If they can't, please reopen this bug.

Thanks!