Just Installed XP Pro. When I Try To Connect With My DSL I Hang For 45 Seconds Please Help

[Aenygma]

When I start my PC and try to connect with my DSL it just sits there and hangs for about 45 seconds, like its trying to resolve my IP or the modems IP or something.

Any ideas?



Also..I went to the update page. There are..
12 Critical Updates
13 Win XP Updates
2 Driver Updates
Also under the driver updates, it has no button for more info. One says K7 Processor Update. ( What are they fixing as I have an AMD XP 1900+ )

 

[Aenygma]

Anyone??

 

[owensdj]

wyst, sounds like the operating system might be waiting while trying to find a DHCP server to obtain an IP address. Does your DSL system use DHCP, or is it one of those PPPoE systems? Seems like most DSL systems use PPPoE.

 

[Aenygma]

I use a ppoe its SBC Global ( southwestern bell )

and this is really annoying.

 

[LongTimePCUser]

Are you using WinPoet or something like that? Nuke it. Windows XP has built in support for DSL.
Using the Windows XP support I connect to Verizon much faster than I used to when I was using Windows ME + WinPoet.

 

[Aenygma]

Nope, not using anything. Just used the connection wizard to set it up.

 

[Aenygma]

I went over this with SBC for about an hour ... we could not solve the issue.

 

[owensdj]

wyst, I've seen this happen with systems that have an Internet connection with a DSL system that uses PPPoE, but not specificially with Windows XP. I know that Windows XP has built-in support for PPPoE that wasn't present in earlier operating systems, so I'm not sure how it sets up your networking when you use PPPoE.

I still think it's doing the same thing I've seen with other operating systems. TCP/IP is set to use DHCP on your Ethernet network card, so it waits to try to find a DHCP server then gives up. The way you get around that is to put in a static, private IP address into your TCP/IP settings, like 192.168.0.1. This may not apply to Windows XP, but it's work looking into.

wyst, please let me know here if this solves your problem or not because I'd like to know if that applies to Windows XP. Good luck.

 

[Creedyou]

Do you get connected wyst or does it just stop trying?

 

[MikeOtis]

I too have had this problem, on my Dad?s computer running clean
installation of Windows XP Professional and a PPPoE DSL connection.
I have downloaded all available updates from Windows Update and the
problem persists. I am using XP?s built-in PPPoE support. Invariably
it will eventually make the connection, but always with that 45 second delay.

And I agree with wyst, it really is an irritating, albeit non-destructive, bug.

owensdj: that is a good suggestion, as you said I am not sure if it will apply to XP but I will definitely give it a shot next time I am home.

 

[Aenygma]

Yes, I have fixed it. And I did so by entering bogus Ip numbers. So yep that works in XP too.

On other boards I have been told there are a couple of other ways too. One was to go into my services and change Workstation to disabled. But I went with the Ip number way. So far so good.

 

[laFiera]

allright, i'm a total idiot when it comes to networking...
i have the same problem..southwestern bell dsl and it takes like a 1 min 15 seconds before i can make a connection...how do i assign the static ip addresss?????

 

[johnlog]

I solved logging onto DSL with XP simply by not turning off my DSL modem when I shut down my computer.

I have SBC Pacbell DSL. If I do turn off my DSL modem for any reason it does take a while to synchronize with DSL and then logs on. But that usually only takes about 15 seconds.

If you continue having those problems log onto DSL REPORTS and search for a fix for all kinds of DSL and cable modem problems and how to solve them.

http://www.speedguide.net/Cable_modems/cable_patches.shtml and:

http://www.dslreports.com/

 

[Don66]

You can try this
Works for me..

 

[Aenygma]

lafiera:

Go into Network connection, and pick the TCP/IP that is bound to your ethernet card. ( I use a Netgear) Then instead of having it checked off for it to get an IP address. Click the box where you assign the address, and just put in dummy numbers like 192.188.2.10 Then where it says subnet mask Change that to 255.255.255.0 or. since you are SBC I think they use 255.255.255.248 And then all will be good.