On Sat, 08 Jan 2005 10:31:04 -0800, Tim Douglass
wrote:

.... snip

The point is that there is usually a reason for the stupid questions.
When you deal with a Windows system reboots are a normal part of any
debugging cycle because it is too stupid to forget anything until you
turn the power off. Especially network stuff.

You ought to try Windows systems on Novell networks. Not only do you
have to power off, you have to unhook the LAN cable (and shake the bits
out) before you can reboot and Novell forgets you were connected to the
network. Part of this may be because of a stupid policy that only allows
one simultaneous network logon per user id -- it's irritating as all get
out when an app freezes the computer and simply re-booting won't get you
back on the network.


I have had to turn off
(power off, not just rebood) every system on my network and bring them
back up again in order to restore communication. Win98 is really bad
that way, but XP does it quite a bit too. I find it is not uncommon to
need to reboot 15-20 times in order to make a network change work.
There is no logical explanation (other than that Microsoft writes
crummy software), but it *does* work a lot of the time. It frustrates
the heck out of me to reboot four times with nothing changing and have
it suddenly work on the fifth, but that's life in the MS world.

Tim Douglass

http://www.DouglassClan.com



+--------------------------------------------------------------------------------+

Now we'll just use some glue to hold things in place until the brads dry

+--------------------------------------------------------------------------------+