Attempted logon to workgroup

[John Fanton]

When I start XP, after I am presented with the desktop, my PC seems to be
trying to "log itself onto a network". There is significant back and forth
blinking of the act and enet lights on my DSL modem, prior to me having
initiated a DSL connection. I am guessing that the PC is trying to log into
a workgroup (as though it were on a LAN) and eventually gives up allowing
the boot process to complete (while this is going on other startup programs
do not run).

Does anyone have an idea if my analysis is correct, and if so how do I
remove this function. My XP implementation was an upgrade from ME, and my
PC originally was logged into a LAN so there may be some residual
functionality which is causing the problem.

Thanks for any suggestions.

[Steve Winograd]

In article <uROrktWmBHA.2212@tkmsftngp04>, "John Fanton"

There's no such thing as logging on to a workgroup. By definition, a
workgroup doesn't contain a server computer which would require a
logon.

I suspect that your PC is logging itself into your DSL connection and
obtaining an IP address from your Internet service provider. All
completely normal.

XP boots to the desktop faster than earlier versions of Windows. The
same DSL login process, with the same time delay, probably occurred
before the desktop appeared with when you ran Windows ME.
--
Best Wishes,
Steve Winograd, MS-MVP

Microsoft Most Valuable Professional - Windows XP
http://support.microsoft.com/support/mvp

Sorry, but I don't give technical support by E-mail.
Please post all questions in the news group, and don't
E-mail your reply to me.

Adding Windows XP to an Existing Network
http://www.practicallynetworked.com/sharing/xp/addxp.htm

Windows XP Internet Connection Sharing
http://www.practicallynetworked.com/sharing/xp_ics

Windows XP Professional File Sharing
http://www.practicallynetworked.com/sharing/xp_filesharing/index.htm

[John Fanton]

Steve,

Thank you for your response. You may be correct, as long as the IP
assignment is performed before I initiate the actual connection to the ISP.
However, I have noticed that the "residual" information about my previous
configuration (domain, computer name, workgroup) are still residing in my
network setup, although serving no purpose. I cannot seem to remove them
(if you try to delete both "Computer Name" and "workgroup Name" the Next
button becomes inactive (within network properties).

Not a big deal, I'm just curious (I actually am a relatively experienced
user, but not terribly network savvy).

JF
"Steve Winograd" <wino...@pobox.com> wrote in message
news:l51r3ukft4re0pndf...@4ax.com...

[Steve Winograd]

In article <e6r00gjmBHA.708@tkmsftngp03>, "John Fanton"

<jfa...@earthlink.net> wrote:
>Steve,
>
>Thank you for your response. You may be correct, as long as the IP
>assignment is performed before I initiate the actual connection to the ISP.
>However, I have noticed that the "residual" information about my previous
>configuration (domain, computer name, workgroup) are still residing in my
>network setup, although serving no purpose. I cannot seem to remove them
>(if you try to delete both "Computer Name" and "workgroup Name" the Next
>button becomes inactive (within network properties).
>
>Not a big deal, I'm just curious (I actually am a relatively experienced
>user, but not terribly network savvy).
>
>JF

Un-check Client for Microsoft Networks and File and Printer Sharing in
the DSL connection's Properties. That could stop your computer from
looking for other computers on the network connection.