Whilst doing some test to pinpount my XBMC – Firefly connection problem, I might have found a bug in how the Firefly installer handles Vista Firefly rules:
TEST 1: VISTA with Firefly installed, windows firewall turned on
TEST 2: XP pro with firefly installed, windows firewall turned on
TEST 3: VISTA with Firefly installed, windows firewall turned off
TEST 4: XP pro with firefly installed, windows firewall turned off
When starting up firefly with -d9, test 2,3 and 4 yield result B
When starting up firefly with -d9, test 1 yields result A (so, the name doesn’t get registered in Bonjour)
IMHO this means Firefly isn’t properly registering itself in the Vista Firewall. Although when I look at the Exceptions list in the Windows Firewall Settings, both Bonjour and Firefly Media Server are registered with scope “any computer”, so that should be fine.
result A:
2007-02-13 17:32:45 (a02e3f68): Scanned 3 songs (was 3) in 0 seconds
result B:
2007-02-13 17:32:45 (a02e3f68): Scanned 3 songs (was 3) in 0 seconds
2007-02-13 17:32:46 (4021d85b): Got a reply for Firefly Media Server (2)._http._tcp.local.
2007-02-13 17:32:46 (4021d85b): Name now registered and active
2007-02-13 17:32:46 (4021d85b): Got a reply for Firefly Media Server (2)._daap._tcp.local.
2007-02-13 17:32:46 (4021d85b): Name now registered and active
2007-02-13 17:32:46 (4021d85b): Got a reply for Firefly Media Server (2)._rsp._tcp.local.
2007-02-13 17:32:46 (4021d85b): Name now registered and active