wierd delay accessing internet on startup in new system

[BB Gun]

Here's the system: http://secure.newegg.com/app/WishR.asp?ID=606188 - built it for a friend this evening.

Freshly installed WinXP on the system above.  Patched and up to date.  nForce drivers up to date.  ATI drivers up to date.  DX9 up to date.

Connection to internet through WinPOET PPoE DSL connection.

Right after startup, clicking on "verizon voyager" which is the WinPOET logon, or any Internet Explorer icon results in nothing happening for about 2-3 minutes (give or take) before anything happens.

If we just wait after logon for a few minutes, then click on the "Verizon Voyager" icon, it comes right up.

What's weird is that task manager shows system idle 99%

Once connected, everything runs fine.  During this "dead" period, control panel, "my computer" windows, task manager,  etc all seem to run fine.

Anyone seen this symptom before?  Any clues on what I might do to try to figure it out?

Thanks,

BB

[Roscoroo]

is it reacquiring its ip addy ??? or having to go thru a log in at its isp ?

 could its AV and or Firewall be hanging it up some?
or a security setting thats holding it up ? <--this is what it sounds like.
(ive tightened bolth 98 and XP down so much that you couldnt get a browser to open , or it took 5 mins to open one befor )

If i hook up a freshly formated pc to my network . it always takes a min or two to acquire its own ip addy and for a browser to find its 1st website . but this only happens one time only. from then on it always loads right up .

some of the firewire / usb type connections have this problem also .  
 (ok theres my small amount of grey matter tossed out for ya  )

Ps, I'm suprised you got the monitor at newegg ... i would of ran down to Compu save in lynnwood for that . the rest of the setup looks pritty good though .

[BB Gun]

We hadn't installed the AV yet, so thats not it.

The WinXP firewall is turned on, but that was the only firewall on there at the time.  (I left last night right after I posted - he's finishing his downloads - media player, warbirds, acrobat, etc etc on his own)

I wonder if since its a PPoE connection, there IS no DHCP assignment UNTIL he logs in?  And that's what's causing the hangup?

I wonder if we get him a router that handles PPoE dial in connections, and which does the DHCP assignments on his own, if that would solve it.

Something to chew on.

I'm just a bit miffed - its the first build I've done in about the last 4 that have any issues at all.

Compusave didn't have the NEC.  Didn't work out too badly - not a single bad pixel that we could see.  Didn't do any thorough diagnostics (all white screen/all black screen etc) though.

Thanks for the thoughts.  Hope ya have enough grey matter left to get through the day.

BB

[Roscoroo]

I think you have it there with having to find DHCP assignment each time it logs on.

(get bigger Stick to wack it with  )

oh yea Friday nights just befor closing at Comusave ... bring cash
(I scored an A7N8X deluxe for $85 outta there a few weeks ago)