Re: PPPoE and ADSL problem (1 solution)
From: Stephen Harris (cyberdiction_at_hotmail.com)
Date: 12/02/03
- Next message: Gazza: "Re: Installed New Ethernet Card. Now Software Bridge Doesn't Work."
- Previous message: Martin LECHNER: "ftp throug firewall problem"
- In reply to: Jacob Westenbach: "Re: PPPoE and ADSL problem (1 solution)"
- Next in thread: Tero Pihlajakoski: "Re: PPPoE and ADSL problem (1 solution)"
- Reply: Tero Pihlajakoski: "Re: PPPoE and ADSL problem (1 solution)"
- Reply: Jacob Westenbach: "Re: PPPoE and ADSL problem (1 solution)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Tue, 02 Dec 2003 20:03:52 GMT
"Jacob Westenbach" <westy528@yahoo.com> wrote in message
news:K85zb.73721$do1.66364@twister.austin.rr.com...
> "Tero Pihlajakoski" <tepihlaj@nopaju.spamoulu.fi> wrote in message
> news:bqief1$21f$1@ousrvr3.oulu.fi...
> > ---
> >
> > Hi,
> >
> > I recently re-installed linux as a second operating system along WinXP.
I
> > had huge problems getting up the internet connection (For finnish
> > googlers: Baana, Cisco, 575 LRE). I managed to connect exactly 2 times
> > (both with perfect connections). But after I'd shutdown and restarted,
the
> > system, it failed to connect with _any_ the PPPoE clients I found on the
> > net.
> >
> > Ok, the solution:
> >
> > I never turned off (complete shutdown) the computer _and_ the ADSL
modem.
> > It seems that XP puts the modem or the network card to some sort of
> > hibernate (or powersave) when it terminates (sigh). Linux then doesn't
> > automagically reset the setting... On my modem this is apparent from the
> > fact that the eth - light on the box "can't be lit" with normal means
> > (like ifconfig or ifup).
> >
> > So it was Windows after all...
> >
> > Does anyone know a more flexible way to solve this? I want to be able to
> > 'restart' windows and boot directly to Linux.
> >
> I hate to be the bearer of bad news, but you'll have to do a complete
> shutdown from Win and then boot into Linux. As you've already discovered,
> Win leaves the NIC in a state of limbo that I've never found a way to
> resolve w/o a cold start of the machine. Fortunately, going from Linux to
> Win does not have the same problem.
>
> JW
>
These conclusions don't seem quite right to me. You will find plenty
of evidence of win xp and linux dual booting and linux having connection
problems of a more advanced nature such as can only use numerical
ip addresses not alphabetical, which means the connection is made but
there is a hosts file un/mis configured. There is no need to turn off
computer.
I think the most likely reason is that the dsl service has not been
stopped. I think it is worth exploring. The win xp pppoe driver
works excellently and is easy to setup. Try clicking on "disconnect"
before restarting the computer and booting into linux. In linux I've
seen scripts for adsl start and asdl stop which I think follows the
idea of ppp-on (pon) and ppp-off (poff). I may be wrong, but I
think turning off the computer terminates the active dsl connection
which is properly terminated by "disconnect" or similar. Whether
this is a bug or not? Most ISPs now offer "Instant On" pppoe
connections by default rather than Always On. I haven't come
across enough information to say this situation is a windows bug
rather than an inconvenient default setting for one personally.
For instance the swat file in Samba is generated automatically
with disable = yes (in Samba 3pre+) when in order to use
swat that entry should read disable = no One would think
that most new users would want to use swat and that older
users don't use swat at all so that the default should be set
to disable = no which means swat is enabled. It is hard to
say if that is a bug or mistaken judgment, without having all the
information available to the programmer who makes the decision.
This may bring up issues with static and/or fixed IP addresses.
On my machine, I dual boot win xp and RH9 with one shared
Nic card without a problem. So do countless others. This leads
me to believe it is not the Nic card itself but due to user practice.
When the linux connection is working you could print out all
the relevant configuration files for the connection. Then create
the problem by booting into windows xp. Print out all the relevant
configuration files and see if they are identical to the working ones.
If they are not identical it is a linux config problem. If they are
identical then it points to the Nic card still in use because the
service on the card has not been terminated. A bit of a pain which
is why I think you should skip to troubleshooting the benefits or
not of turning the service off (disconnect) in windows first and
see what happens. It is an easy step to try.
Regards,
Stephen
- Next message: Gazza: "Re: Installed New Ethernet Card. Now Software Bridge Doesn't Work."
- Previous message: Martin LECHNER: "ftp throug firewall problem"
- In reply to: Jacob Westenbach: "Re: PPPoE and ADSL problem (1 solution)"
- Next in thread: Tero Pihlajakoski: "Re: PPPoE and ADSL problem (1 solution)"
- Reply: Tero Pihlajakoski: "Re: PPPoE and ADSL problem (1 solution)"
- Reply: Jacob Westenbach: "Re: PPPoE and ADSL problem (1 solution)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|