Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

HOWTO: Making a dial-up connection "always on" with ADSL

0 views
Skip to first unread message

Morten Tvedten

unread,
Aug 8, 2001, 6:08:34 PM8/8/01
to
I have finnaly found a way to alwasy be conneted with ADSL.
I found this "Recepie" in the RASPPPOE readme file for Windows 2000.

You do not need to use RASPPPOE. it Works for the built-in ADSL connections
as well. For Windows XP and 2000.

WARNING: Editing your Registry is not for dummys! Be Carefull!

Extract from Readme2k.htm:

5.6 Making a dial-up connection "always on"
Users who enjoy flat rate Internet access may find it desirable to turn
their connection into an "always on" connection that is established once
when the machine boots (before any user logs in) and kept until the machine
is shut down. To make your dial-up connection "always on", follow these
steps:

a.. If your service provider requires authentication, make sure you have
saved the password by checking the Save Password checkbox in the Connect
Connection Name window and connecting at least once.
b.. Right-click the My Network Places icon on your desktop and select
Properties to bring up the Network and Dial-up Connections window.
c.. Locate the Dial-up connection you created for PPP over Ethernet,
right-click it and select Properties.
d.. Select the Options tab and clear all checkboxes under Dialing
options.
e.. Under Redialing options, set Idle time before hanging up: to never
and check the Redial if line is dropped checkbox.
f.. Click OK to save the changes.
g.. Now click the Start button, select Settings then Control Panel to
open the Control Panel window.
h.. In the Control Panel window, double-click Scheduled Tasks.
i.. In the Scheduled Tasks window, double-click Add Scheduled Task.
j.. On the welcome screen of the Scheduled Task Wizard, click Next.
k.. At the program selection step, click Browse... and browse to your
WINNT\System32 directory.
l.. Type RASPHONE.EXE (note the spelling!) in the File name: edit box or
locate it in the directory and select it and click Open.
m.. Make up a name for this task and under Perform this task: select
When my computer starts. Click Next.
n.. Enter your password. Note: The task must be run under the same
account which the dial-up entry was created under.
o.. At the final step, make sure that Open advanced properties for this
task when I click finish is checked and click Finish.
p.. In the advanced properties, edit the Run: edit box and append the
command-line parameters " -d "Connection Name"".
q.. Go to the Settings tab and clear all checkboxes on that page.
r.. Click OK to close the task's properties.
s.. Finally, you need to make a little registry change to prevent
Windows from disconnecting when a user logs on and off again:
Run REGEDIT and navigate to:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon

Then right-click the right-hand pane, select New -> String Value, name
the value KeepRasConnections and set it to 1.

a.. Reboot. Windows will establish the connection automatically and keep
it until you shut the machine down.
b.. NOTE: The connection will not be properly terminated when shutting
the machine down or rebooting. This can cause problems with service
providers who take very long to detect such a dropped connection and limit
the number of concurrent connections. See Known Issues for further details.

7.7 When a dial-up connection is made "always on", it is not properly
terminated when shutting the machine down or rebooting
When you configure a PPP over Ethernet dial-up connection to be "always
on", the connection will not be properly terminated when shutting the
machine down or rebooting. This causes problems with service providers who
take very long to detect such a dropped connection and limit the number of
concurrent connections - after several reboots, you may find yourself to log
on to your service provider for some time. To work around this problem,
always disconnect your "always on" connection manually before rebooting.

Background: Investigation revealed that the protocol receives no
indication that the system is going down. Neither the MiniportHalt(), nor
the ProtocolUnbindAdapter(), nor the ProtocolPnPEvent() and not even the
ProtocolStatus() handler are called to indicate the shutdown. Thus, it is
not possible for the protocol to terminate its outstanding connections prior
to the shutdown. This is apparently a shortcoming of Windows 2000.

======================================

More information on RASPPPOE: http://user.cs.tu-berlin.de/~normanb/

Morten


0 new messages