Problem during startup

[situman]

everytime after i reboot and get back into my desktop, i cant get online (I have dsl) or open My Computer. It takes about a minute or so for it to sign online and for everything to work smoothly. My friend said it is because the computer is searching automatically for an IP address. Now is there a way for me to solve this issue? Or that's the way it is? Computer runs fine, it's just that I have to wait a while before I can do anything. BTW I am running XP

[Paragon]

It would really help if we knew what kind of DSL connection you are running, is it PPOE? You're probably seeing the time wasted by your machine while it's looking for all the network settings...are you running a router? Have you checked the modem settings? There's a number of items that can cause what you are describing to happen...give us a bit more information and I think we can you.

Type of DSL Connedction? PPOE and etc.
Router and type if you are running one?
Type of Modem?
ISP for DSL?

[situman]

Sorry. Its verizon dsl, no router, westell dsl modem, and no router. I think it is PPOE. no clue really.

[Jim]

Sounds like you may have PPPoE, and need to manually enter an IP for the NIC to fix stalling.
This may fix you up:

Q: Help! I get stuck (pauses) regularly when I am surfing (#1271)
A: If your PC is freezing regularly, and you are on PPPoE, your computer may be looking around for a DHCP server that does not exist. Check the following: (windows)

Open control panel
· Open Network neighborhood
· Look for the first entry in the scroll box marked TCP/IP -> , that is associated with the hardware Ethernet card (ignore dialup, and VPN type bindings).
· Select "TCP/IP-> Name of NIC
· Select it and press properties
· Select IP address from the tab
· Is Obtain IP address automatically checked? If so, change that to Specify an IP address and enter 192.168.1.10, and 255.255.255.0, into IP address and subnet mask fields respectively.
· Click OK and OK, and the computer will build a driver information database and will require a reboot for the changes to take effect.
This assignment of a harmless local IP address to the TCP/IP settings bound (connected) to your network adapter will stop the in-built DHCP services from waking up every 10 minutes to look for a DHCP server so that it can "fill in the blanks". This should solve the freezing problem.

This taken from the Verizon FAQ at DSL Reports here (http://www.dslreports.com/faq/1271) .
Even better though, invest in a Linksys or similar router that will emulate a PPPoE connection, provide a NAT firewall and give you an "always on" connection.

HTH :thumb:

[Subsider]

Even better though, invest in a Linksys or similar router that will emulate a PPPoE connection, provide a NAT firewall and give you an "always on" connection.

that would be best !

[SubZero]

Do you see any harddisk activity while waiting for your system to start responding?

I'm not convinced it has anything to do with a router or internet connection. Make sure you check out what gets started up when you boot into windows.

Type msconfig at start, run and see what's listed under the startup tab. Try disabling suspicious ones and see what happens next time you reboot. Make sure you also check out the services tab. Another way is to use bootvis to analyze the boot process and see what happens there but that may be too advanced to try right now.

[situman]

this happens even after I set up an internet connection right after a fresh install. sigh...so i might have to invest in a router.

[SubZero]

Did you carry out Jim's suggestions??

Anyway, a router is an inexpensive, solid investiment and you'll sure enjoy the benefits of it.

[situman]

sure i followed jim's recommendations, not working! anyways i will think about getting a router.