Takes forever connecting when using a specific router

Rafael Mizrahi [Boxee] added a comment - 03/May/11 6:08 AM what do you mean by saying "to connect to the LAN " what is the action in boxee that you are doing which takes allot of time. and please specify how much is "forever" Please attach a Debug log to this issue. Settings > System > Debug > Debug Level = Debug ReStart Boxee, and after reproducing the problem, get the log and attach it to this issue. Boxee Box log may be found at http://Your_boxee_box_IP:8080/ click on the "Get latest " link. more information at http://support.boxee.tv/entries/329278-i-ve-been-asked-by-boxee-support-to-send-debug-logs-how-do-i-do-that http://support.boxee.tv/entries/43963-i-ve-been-asked-by-boxee-support-to-send-debug-logs-how-do-i-do-that DEBUG log slows down the performance. so afterward, switch the log level back to NONE

Robert Ylvestedt added a comment - 03/May/11 1:43 PM Debug log for BOXEE-9623

Robert Ylvestedt added a comment - 03/May/11 1:47 PM step 1: Loading image step 2: alot of boxes floating up in the air building another logo step 3: yet another logo step 4: Connect to account. Here is the problem. I clocked it at 131 seconds. With another router(D-Link DIR-655) it connects within 5 seconds.

Rafael Mizrahi [Boxee] added a comment - 04/May/11 5:15 AM I could not understand what is taking 131 seconds ? login into Boxee? connect to an SMB share ? I am trying to find in your log (root-boxee.log) file the area which takes 2 minutes ?

Rafael Mizrahi [Boxee] added a comment - 04/May/11 6:19 AM oh.. found it. in the log, I see a few block of 19:36:28.0615 T:3074361120 M:543674368 INFO: Host string <BA-076E75> wasn't found by gethostbyname - probably a NBT name (err 2) 19:36:38.0632 T:3074361120 M:543674368 INFO: Host string <BA-076E75> wasn't found by gethostbyname - probably a NBT name (err 2) 19:36:48.0648 T:3074361120 M:543674368 INFO: Host string <BA-076E75> wasn't found by gethostbyname - probably a NBT name (err 2) 19:36:58.0665 T:3074361120 M:543674368 INFO: Host string <BA-076E75> wasn't found by gethostbyname - probably a NBT name (err 2) 19:37:08.0682 T:3074361120 M:543666176 INFO: Host string <BA-076E75> wasn't found by gethostbyname - probably a NBT name (err 2) 19:37:18.0698 T:3074361120 M:543666176 INFO: Host string <BA-076E75> wasn't found by gethostbyname - probably a NBT name (err 2) 19:37:28.0715 T:3074361120 M:543670272 INFO: Host string <BA-076E75> wasn't found by gethostbyname - probably a NBT name (err 2) 19:37:38.0731 T:3074361120 M:543670272 INFO: Host string <BA-076E75> wasn't found by gethostbyname - probably a NBT name (err 2) 19:37:48.0748 T:3074361120 M:543670272 INFO: Host string <BA-076E75> wasn't found by gethostbyname - probably a NBT name (err 2) 19:37:58.0765 T:3074361120 M:543670272 INFO: Host string <BA-076E75> wasn't found by gethostbyname - probably a NBT name (err 2) I tend to believe that this is a problem in your network configuration.

Robert Ylvestedt added a comment - 04/May/11 9:21 AM hmm, BA-076E75 is the NAS.. Right before the home screen comes up, there's a connecting screen that takes a little over 2 minutes for it to connect. I'm interesting in the "wasn't found by gethostbyname - probably a NBT name (err 2)" I will check my router to see if there's some strange NetBios thing going on. Can the box handle IPv6? Found the following on another forum for something completely unrelated, but apparently gethostbyname can in some cases be a little off.. "Fixed name resolution in environments where gethostbyname can return   IPv6 (or other non-IPv4 addresses). In such an environment, Nmap   would wrongly use the first four bytes of the IPv6 address as an   IPv4 address. You could force this, at least on Debian, by adding   the line "options inet6" to /etc/resolv.conf or by running with   RES_OPTIONS=inet6 in the environment."

Rafael Mizrahi [Boxee] added a comment - 04/May/11 11:03 AM The BoxeeBox currently does not support IPv6

Robert Ylvestedt added a comment - 05/May/11 9:43 AM I can't find anything out of the ordinary with my network config. I find it very strange to have trouble resolving the IP for the NAS for two minutes and then everything works automagically. If the IP isn't resolved the box shuldn't be able to access the NAS at all.. :S

Robert Ylvestedt added a comment - 19/May/11 4:31 PM After an update to the latest firmware everything goes super smooth. The connecting takes 5-10 seconds. I would think this issue is solved and can be closed. :)

Rafael Mizrahi [Boxee] added a comment - 22/May/11 4:31 AM thank you Robert for reporting. I am hence closing this issue as cannot reproduce.