Thanks for the analysis - this sounds like a plan. I need to be away for
about three hours but will execute these steps when I return. I'm also
very glad that you were able to take a peek at the code as there's no
substitute for what the code actually says.


bpa;503279 Wrote: 
> Because your log file looks like your are using a standard English
> Windows system and the directories look normal, I've made the assumption
> that the problem is not in SBS or where it is installed and that it just
> as a result of SBS trying to do is open a port. 
> 
> I've spent time on some Slimserver problems where supporting app
> socketwrapper was prevented from running by various security s/w,
> malware and corrupted installations so I'm drawing on this knowledge.  
> 
> This problem is odd in that AFAICT internet usage is OK except for
> trying to open a UDP port.  The actual code is
> > 
Code:
--------------------
  >   > 
  >     $udpsock = IO::Socket::INET->new(
  >             Proto     => 'udp',
  >             LocalPort => SERVERPORT,
  >             LocalAddr => $main::localClientNetAddr
  > 
  >     ) or do {
  > 
  >             # XXX - exiting in a deep sub is kinda bad. should propagate up.
  >             logger('')->logdie("FATAL: There is already another copy of the 
Squeezebox Server running on this machine. ($!)");
  >     };
  > 
--------------------
> > 
> 
> It is important to try and identify theproblem because if it is
> because of a software settings or another s/w package rather than some
> sort of corruption, then after reformatting the problem is likely to
> recur.
> 
> However, you're right that we should try to resolve the issue even if
> it means the problem is not identified and taking drastic action such
> as a reformat & reinstall.
> 
> I suggest that bring the issue to a close by this evening with the
> following steps.
> 
> 1. Test that IP address is OK by running these commands and copy
> logged output.  The first one should fail but the log output might be
> interesting.  The second one needs the actual IP address of the PC
> (something like 192.168.1.120) - use ipconfig if necessary
> SqueezeSvr.exe --debug server=DEBUG,network.protocol=DEBUG
> --playeraddr=127.0.0.2
> SqueezeSvr.exe --debug server=DEBUG,network.protocol=DEBUG
> --playeraddr=PCIPADDR
> 
> These might test the possibility of the hosts file being corrupted.
> 
> 2. Run LSPFix (found here http://www.cexx.org/lspfix.htm ) - to stop
> LSPFix you use the "close window x" in top right.  Report list shown
> by LSPFix - I don't expect it to show anything new as Windows "netsh
> reset Winsock" more or less does the same thing.
> 3. Assuming you are confident that either you have Windows disks or
> Windows drivers are already on harddrive, delete all the network
> interface and re-install.
> 4. If all else fails - reinstall Windows.  Get SBS working as part of
> early packages (e.g. after standard Windows apps) and then install
> other user preferred packages.


-- 
Tom Hutcheson
------------------------------------------------------------------------
Tom Hutcheson's Profile: http://forums.slimdevices.com/member.php?userid=35487
View this thread: http://forums.slimdevices.com/showthread.php?t=73387

_______________________________________________
discuss mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/discuss

Reply via email to