Last night I reported that the latest build (1/26) of 6.5b1 worked on my
system. It did not exhibit the problem I originally started this thread
with.
Today I downloaded the 1/27 version, which I noticed was only 9MB
(instead of 14MB), and that didn't work at all. Wouldn't even start.
So I
This may sound a bit out there but - Run MSconfig. Go to the Startup
section. Uncheck any apps that were recently installed or that are
starting in the tray that you don't need.
I have had problems before with too many startup items and one of them
conflicts with something else during the boot
notanatheist Wrote:
How could I not comment on that? You mention not using the MS Firewall
but are you using any other software firewall such as sNorton Internet
Shitcurity or McCrappy? Zonealarm? Reboot the SB and be sure it's
getting an internal IP and not a 169?
I already tried turning
MarkH Wrote:
The problem seems to be that once a connection is made between client
and server, the server stops.
As in, crashes?
If so, go to the event log and tell us what the crash information is.
--
Michaelwagner
Michaelwagner Wrote:
As in, crashes?
If so, go to the event log and tell us what the crash information is.
No, it didn't crash. It just stopped. If the client is shut down, the
server can be restarted. If the client is still trying to connect, the
server tries to restart, but just
MarkH Wrote:
G. I hate Windows.
How could I not comment on that? You mention not using the MS Firewall
but are you using any other software firewall such as sNorton Internet
Shitcurity or McCrappy? Zonealarm? Reboot the SB and be sure it's
getting an internal IP and not a 169?
--
I'm using Win XP Pro SP2, patched up to date, and am not having any
issues. Might the Windows Firewall have got turned on at some point in
this process?
Ceejay
--
ceejay
ceejay's Profile:
No, that's not it. The firewall service isn't even running.
This feels strangely like the problem I had with my HP scanner not
being able to be accessed over the LAN after installing SP2. Had to
change some security settings to get it to work again (even HP didn't
know how to get it to work
