extremely slow boot up times

[m0ng0d]

@Teletype post:20

OK. Here is another suggestion which should isolate the offending service responsible for stalling your system:

1. During the bootup phase (which means as soon as you can click on the Start button, and click on the Run command), run the SERVICES.MSC

2. Maximize its screen, and click on the Status column twice in order to sort the lines based on their loading order.

3. Press the F5 key repeatedly (every second or so) to refresh the screen.

4. You’ll note that as the services begin to run, their status changes to “Started”.

5. Keep your eyes on any line which states “Starting” for too long.
   (Note the difference between “Starting” and “Started”)

That would be the service which is stalling your system.

I found that there are no Starting Services by the time the desktop loads, and I launch Services. The slowness occurs in in 2 spots after the boot…

• authentication (login), and
• Loading the profile

… I’m beginning to wonder if I’ve really logged in at all… or have merely loaded with previously cached security.

Another authentication test I ran after boot (inspired by my issue here) was to create a “test.udl” file (Microsoft Data Link) on my desktop and try configure it to connect to our SQL server… I have no problems seeig the broadcasted SQL server(s) but if I choose Windows Authentication I’ll get another long wait.

I’ve even noticed inconsistant access to mapped network drives.

The more I type this post, the more convinced I am that it’s not a rouge service causing my greif, but an inability to authenticate properly on the domain with CPF set to “Custom”… If I set it to “Allow All”, things work flawlessly, even at login.

And just like posted in the link I attached above, the only log entries I get are:

• Date/Time :2006-09-19 08:53:57
  Severity :High
  Reporter :Network Monitor
  Description: Blocked by Protocol Analysis (Fragmented IP Packet)
  Direction: IP Outgoing
  Source: 192.168.1.58
  Destination: 192.168.1.200
  Protocol : UDP Reason: Fragmented IP packets are not allowed
• Date/Time :2006-09-19 08:53:57
  Severity :High
  Reporter :Network Monitor
  Description: Blocked by Protocol Analysis (Fake or Malformed UDP Packet)
  Direction: UDP Outgoing Source: 192.168.1.58:1996
  Destination: 192.168.1.200:88
  Reason: UDP packet length and the size on the wire(1500 bytes) do not match

It’s too bad that CPF doesn’t log anything while windows is booting.

UPDATE:

So as mentioned in the other post i provided a link to in this post… I had only played with the Block fragmented IP datagrams option… today I decided to play with the Do Protocal Analysis option… disabling it has cleared my problem… but why?

[attachment deleted by admin]

[kail]

Perhaps BootVis might help?

[m0ng0d]

@kail post:22

Perhaps BootVis might help?

Sounds like it certainly would. I gave it a fast try but must be using it wrong. After a reboot, I tried to open bootvis and it told me that it couldn’t find the BIN file… if you have used the tool yourself, could I ask you to highlight point-form the steps you take to set it up and view the results?

Many thanx in advance

[kail]

@m0ng0d post:23

Sounds like it certainly would. I gave it a fast try but must be using it wrong. After a reboot, I tried to open bootvis and it told me that it couldn’t find the BIN file… if you have used the tool yourself, could I ask you to highlight point-form the steps you take to set it up and view the results?

Sorry, I can’t. I’ve not used BootVis in years & I’m currently using W2k, which BootVis doesn’t run on. You’ll neeed an XPer to assist you. Sorry.

Edit: Do a search for *.BIN perhaps?

[m0ng0d]

Ah… it wasn;t that the file didnt exist, it was that the file had 0 bytes… so obviously I am doing something wrong if it’s was blank

So you dumped Fisher Price Win2K for Win2K eh? And I understand why too. (:NRD)