Login pause solved. Now get desktop, => 90 sec network initialized

T

Tom

As the title says. Here is my network setup

ppoe adapter
3com nic set using wizard to dial broadband

-bridged connections-
dlink card set with static ip, for lan. 10.xxx ip
1394 firewire

Basically now, windows comes up and desktop comes up all
icons but i can't access my networking config or anything
to do with the network for => 90 seconds. Remember, I must
manually dial or setup my ppoe to dial my DSL provider,
but even setting this to auto I still wait 90 seconds for
god knows what before i can access my networking stuff.
Anyone know why this is happening??? Response on this has
been horrible in the past, nobody has this problem and I
seem to be a unique person in a world of millions of
windows users that apparently don't have this problem.
Someone must know what is going on here.
 
M

Malke

Tom said:
As the title says. Here is my network setup

ppoe adapter
3com nic set using wizard to dial broadband

-bridged connections-
dlink card set with static ip, for lan. 10.xxx ip
1394 firewire

Basically now, windows comes up and desktop comes up all
icons but i can't access my networking config or anything
to do with the network for => 90 seconds. Remember, I must
manually dial or setup my ppoe to dial my DSL provider,
but even setting this to auto I still wait 90 seconds for
god knows what before i can access my networking stuff.
Anyone know why this is happening??? Response on this has
been horrible in the past, nobody has this problem and I
seem to be a unique person in a world of millions of
windows users that apparently don't have this problem.
Someone must know what is going on here.

Response may have been "horrible in the past" because this is not
Microsoft tech support. This is a newsgroup providing peer-to-peer help
with problems relating to the WinXP operating system. If you haven't
been answered, it is probably because nobody posting right now knows
the answer. I know I won't normally guess at a solution because I don't
want to mislead a poster into possibly doing something destructive to
their system. Also, as in your case, the reason(s) for your problems
could be quite complex, very hard to diagnose from Usenet postings.
Perhaps you should just call a local computer repair person who has
networking experience to come and look at your setup and make things
right. It may be a case where s/he can tell what's going on very
quickly by looking at things whereas the cause is not apparent from
reading about it.

Malke
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top