Dlink DSM-320 and CyberMediaGate

2005-02-24
2013-05-02
  • Victor Fariña

    Victor Fariña - 2005-02-24

    Anyone are trying to use CybermediaGate with Dlink DSM-320 ??? i am trying with no results .. i always obtain the same error when on the dlink i try to discover new servers :
    CyberGarage warning : Connection reset
    java.net.SocketException: Connection reset
        at java.net.SocketInputStream.read(SocketInputStream.java:168)
        at sun.nio.cs.StreamDecoder$CharsetSD.readBytes(StreamDecoder.java:408)
        at sun.nio.cs.StreamDecoder$CharsetSD.implRead(StreamDecoder.java:450)
        at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:182)
        at java.io.InputStreamReader.read(InputStreamReader.java:167)
        at java.io.BufferedReader.fill(BufferedReader.java:136)
        at java.io.BufferedReader.readLine(BufferedReader.java:299)
        at java.io.BufferedReader.readLine(BufferedReader.java:362)
        at org.cybergarage.http.HTTPPacket.set(HTTPPacket.java:132)
        at org.cybergarage.http.HTTPPacket.set(HTTPPacket.java:217)
        at org.cybergarage.http.HTTPPacket.set(HTTPPacket.java:222)
        at org.cybergarage.http.HTTPPacket.read(HTTPPacket.java:245)
        at org.cybergarage.http.HTTPRequest.read(HTTPRequest.java:331)
        at org.cybergarage.http.HTTPServerThread.run(HTTPServerThread.java:46)

    on the TV I obtaing "NO SERVERS FOUND"

    thanks

     
    • Joachim Martin

      Joachim Martin - 2006-09-20

      I am having the same problem- DSM-520 cannot see CyberMediaGate, but Cidero, Intel, and other control points can.

      It looks like CMG advertises itself correctly on startup, but doesn't respond to discovery requests correctly after it is running.

      If I restart CMG in the DSM-520 servers page, it shows up briefly.  After a while, the DSM does a refresh and tries to discover new servers, at which point CMG disappears.

      Any thoughts/fixes for this?

      Thanks

       
    • Joachim Martin

      Joachim Martin - 2006-09-22

      It turns out to be the random wait time- the MX header sent by the searching device.

      If I dial down the sleep time to MX*10ms instead of 1000ms, the DSM-finds it fine.

      Of course this goes against the whole idea of MX, to reduce load on the searching device, but I gotta do what I gotta do. Just wish there was a way to ID the DSM-520 in the SSDP request.

       

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks