Results 1 to 6 of 6

Thread: What kills XP...

  1. #1

    Thread Starter
    Addicted Member
    Join Date
    Jul 2002
    Posts
    135

    Talking What kills XP...

    What kills all XP and win2k machines on a network? It takes 30-40 min for XP to login, and then cant access any network stuff, but internet/email works?
    Hello? Underpaid code monkey speaking...

  2. #2
    PowerPoster Beacon's Avatar
    Join Date
    Jan 2001
    Location
    Pub Floor
    Posts
    3,188
    Hmm a virus or a virus scanner that scans on boot.

    Or incorrectly configured TCP-IP settings. But not 30mins to logon.

  3. #3
    Member alphanumeric's Avatar
    Join Date
    Jan 2003
    Location
    Sydney, Nova Scotia, Canada
    Posts
    62
    Do you have any mapped network shares?
    Speed up network browsing
    PC performance buffs have long measured hardware advances using a few simple metrics: Is it faster? Is it bigger? Does it have more blinky lights?

  4. #4
    PowerPoster Beacon's Avatar
    Join Date
    Jan 2001
    Location
    Pub Floor
    Posts
    3,188
    Hey Alpha,

    I'd doubt that 30mins is due to it checking for printers and scheduled tasks. But i've seen weireder things.

  5. #5
    Member alphanumeric's Avatar
    Join Date
    Jan 2003
    Location
    Sydney, Nova Scotia, Canada
    Posts
    62
    Originally posted by Beacon
    Hey Alpha,

    I'd doubt that 30mins is due to it checking for printers and scheduled tasks. But i've seen weireder things.
    Yeah I know, a real long shot, but maybe it accounts for some of the delay. I know my 2k PC took an agonizingly long time to see my 98 PC on my LAN before I did that reg hack. I don't have any mapped drives, just a couple of shared folders and a network printer.
    PC performance buffs have long measured hardware advances using a few simple metrics: Is it faster? Is it bigger? Does it have more blinky lights?

  6. #6

    Thread Starter
    Addicted Member
    Join Date
    Jul 2002
    Posts
    135
    Yeah, I have about a dozen network shares. It turned out to be something in the network, It took the network group and the "Intergration" team a day and 1/2 to figure out, and then they wouldn't even tell the computer support team what it was.
    Hello? Underpaid code monkey speaking...

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width