Delayed net connectivity

[Guest JGundrey]

After boot-up, and then launch IE, the browser just sits there empty for

several minutes sometimes. Then, the home page pops up finally and web

browsing continues normally after that. During the time the browser is

blank, there is no "Local Area Network" icon (with the little blinking green

lights) in the system tray. After the web starts working, the little network

icon (with the two little monitors) appears in the tray.

 

IE 7, 32 bit. WinXP64 SP2. It used to work no problem. Nothing in my

hardware has changed. What gives?

[Guest Tony Sperling]

Re: Delayed net connectivity

 

Multitude of possible causes - best check your 'Event Viewer' and see if

there is any error, warning or tip to lead us on.

 

Often it might be a result of removing stuff that the system spends time

looking for. (Some USB Device?)

 

Depending on your Windows version you could try and delete your internet

connection and remove TCP/IP (Add, Remove Windows Components). This

reportedly doesn't work on the US version but I have done that a couple of

times with varying success on my International Version!

 

But look in your EV first.

 

 

Tony. . .

 

 

"JGundrey" <JGundrey@discussions.microsoft.com> wrote in message

news:28B0DB2D-04D4-4ED8-A218-5AD597BC1BDC@microsoft.com...

> After boot-up, and then launch IE, the browser just sits there empty for

> several minutes sometimes. Then, the home page pops up finally and web

> browsing continues normally after that. During the time the browser is

> blank, there is no "Local Area Network" icon (with the little blinking

> green

> lights) in the system tray. After the web starts working, the little

> network

> icon (with the two little monitors) appears in the tray.

>

> IE 7, 32 bit. WinXP64 SP2. It used to work no problem. Nothing in my

> hardware has changed. What gives?

[Guest Charlie Russel - MVP]

Re: Delayed net connectivity

 

Given the description, it sounds like his internet connection isn't

"enabled" until he tries to connect. This would be a typical scenario if,

for example, you had a DSL PPPoE connection that used a direct connection

from the DSL modem to the OPs network card, and the setting on the modem was

to not be always on. When that's the case, the first connection needs to

fire up the modem, connect to the ISP and then configure a DHCP address for

the connection. There is an appreciable time delay while this occurs.

 

Possible workarounds: Add a router to the network that is responsible for

maintaining the DSL (or cable or whatever) connection. The workstation then

gets plugged in to the router, and the router is responsible for DHCP

address assignments. Another workaround would be to log on to the DSL or

cable modem and change the settings on it. But if this is owned by the ISP,

chances are you don't have a way to do this. Another, less elegant,

workaround is to add a web site to your startup folder. This will force the

initial connection whenever you log in. It will still take an appreciable

time, but it will be part of the normal startup process.

 

--

Charlie.

http://msmvps.com/blogs/xperts64

http://mvp.support.microsoft.com/profile/charlie.russel

 

"Tony Sperling" <tony.sperling@dbREMOVEmail.dk> wrote in message

news:uCwQznYFJHA.6052@TK2MSFTNGP04.phx.gbl...

> Multitude of possible causes - best check your 'Event Viewer' and see if

> there is any error, warning or tip to lead us on.

>

> Often it might be a result of removing stuff that the system spends time

> looking for. (Some USB Device?)

>

> Depending on your Windows version you could try and delete your internet

> connection and remove TCP/IP (Add, Remove Windows Components). This

> reportedly doesn't work on the US version but I have done that a couple of

> times with varying success on my International Version!

>

> But look in your EV first.

>

>

> Tony. . .

>

>

> "JGundrey" <JGundrey@discussions.microsoft.com> wrote in message

> news:28B0DB2D-04D4-4ED8-A218-5AD597BC1BDC@microsoft.com...

>> After boot-up, and then launch IE, the browser just sits there empty for

>> several minutes sometimes. Then, the home page pops up finally and web

>> browsing continues normally after that. During the time the browser is

>> blank, there is no "Local Area Network" icon (with the little blinking

>> green

>> lights) in the system tray. After the web starts working, the little

>> network

>> icon (with the two little monitors) appears in the tray.

>>

>> IE 7, 32 bit. WinXP64 SP2. It used to work no problem. Nothing in my

>> hardware has changed. What gives?

>

>

[Guest Tony Sperling]

Re: Delayed net connectivity

 

I think you are right about that being 'typical' - it is so long ago that I

was on that type of connection so I wasn't even considering the possibility.

Even so, my broadband sits on a Router and I have seen those really

procrastinated connections here too. Usually not having a clue, I end up

doing something drastic, like taking it all down, and re-create it.

 

But we should perhaps consider (since this is said to be a change in

behavior?) that there are days, (weeks?) when even a 10Mb/s connection is

not fast at all. Internet is about to be bogged down and it may take that

long to reach your ISP??? If everyone was still on modems we wouldn't be

able to do anything at all with it.

 

 

Tony. . .

 

 

"Charlie Russel - MVP" <charlie@mvKILLALLSPAMMERSps.org> wrote in message

news:uDO00vbFJHA.3848@TK2MSFTNGP02.phx.gbl...

> Given the description, it sounds like his internet connection isn't

> "enabled" until he tries to connect. This would be a typical scenario if,

> for example, you had a DSL PPPoE connection that used a direct connection

> from the DSL modem to the OPs network card, and the setting on the modem

> was to not be always on. When that's the case, the first connection needs

> to fire up the modem, connect to the ISP and then configure a DHCP address

> for the connection. There is an appreciable time delay while this occurs.

>

> Possible workarounds: Add a router to the network that is responsible for

> maintaining the DSL (or cable or whatever) connection. The workstation

> then gets plugged in to the router, and the router is responsible for DHCP

> address assignments. Another workaround would be to log on to the DSL or

> cable modem and change the settings on it. But if this is owned by the

> ISP, chances are you don't have a way to do this. Another, less elegant,

> workaround is to add a web site to your startup folder. This will force

> the initial connection whenever you log in. It will still take an

> appreciable time, but it will be part of the normal startup process.

>

> --

> Charlie.

> http://msmvps.com/blogs/xperts64

> http://mvp.support.microsoft.com/profile/charlie.russel

>

> "Tony Sperling" <tony.sperling@dbREMOVEmail.dk> wrote in message

> news:uCwQznYFJHA.6052@TK2MSFTNGP04.phx.gbl...

>> Multitude of possible causes - best check your 'Event Viewer' and see if

>> there is any error, warning or tip to lead us on.

>>

>> Often it might be a result of removing stuff that the system spends time

>> looking for. (Some USB Device?)

>>

>> Depending on your Windows version you could try and delete your internet

>> connection and remove TCP/IP (Add, Remove Windows Components). This

>> reportedly doesn't work on the US version but I have done that a couple

>> of times with varying success on my International Version!

>>

>> But look in your EV first.

>>

>>

>> Tony. . .

>>

>>

>> "JGundrey" <JGundrey@discussions.microsoft.com> wrote in message

>> news:28B0DB2D-04D4-4ED8-A218-5AD597BC1BDC@microsoft.com...

>>> After boot-up, and then launch IE, the browser just sits there empty for

>>> several minutes sometimes. Then, the home page pops up finally and web

>>> browsing continues normally after that. During the time the browser is

>>> blank, there is no "Local Area Network" icon (with the little blinking

>>> green

>>> lights) in the system tray. After the web starts working, the little

>>> network

>>> icon (with the two little monitors) appears in the tray.

>>>

>>> IE 7, 32 bit. WinXP64 SP2. It used to work no problem. Nothing in my

>>> hardware has changed. What gives?

>>

>>

>