Tom Hutcheson;503205 Wrote:
> Well I sure would like to be able to get this machine to run. I
> mentioned in my initial post that my friend bought herself a Classic for
> Christmas (after seeing mine for the last 6 years) so I'm working on
> getting SlimServer installed on her machine (this is her machine we're
> working on that I've moved to my house for now). I've alerted her to the
> possibility though that I don't see a light at the end of the tunnel yet
> and there may be no solution. I'm out of my debugging realm at this
> point but game and very happy to follow any and all leads you (or
> anyone) may have for me but at some point even you may be out of ideas.
> Knowing what you know and what we've seen so far, what are your best
> thoughts on what's going on? Seeing as how I'm thinking that you think
> that this is a low-levek software conflict, would you venture to say
> that if I reformatted the drive and started over that that would handle
> the issue? Obviously that's extreme and I would like to avoid that but I
> guess the question is - would it work?
>
> Thanks so much and hoping to hear your ideas-
> Tom
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.
--
bpa
------------------------------------------------------------------------
bpa's Profile: http://forums.slimdevices.com/member.php?userid=1806
View this thread: http://forums.slimdevices.com/showthread.php?t=73387
_______________________________________________
discuss mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/discuss
