How to automate an ADSL internet connection after turning of a PC?

Hello!
How to prevent the need to run a connection and click the "Connect" every
time after turning on a PC to connect (to the Internet)? How to automate the
running the connection and clicking the "Connect" after turning on a PC?
Best regards,
Dima

"Dima" <Dima@discussions.microsoft.com> wrote in message
newsC0DCC19-62F0-40C6-9CC8-7D9534C48841@microsoft.com...
> Hello!
> How to prevent the need to run a connection and click the "Connect" every
> time after turning on a PC to connect (to the Internet)? How to automate
> the
> running the connection and clicking the "Connect" after turning on a PC?
> Best regards,
> Dima
>

The best way is to replace your ADSL modem with an ADSL
modem/router. With a modem/router you get an automatic and
permanent connection. You could also connect more than one
PC to the same modem/router.

If this is not an option then you could send the appropriate
keystrokes to the modem by using AutoIt
(http://groups.yahoo.com/group/autoit)

On Jan 11, 5:02*pm, Dima <D...@discussions.microsoft.com> wrote:
> Hello!
> How to prevent the need to run a connection and click the "Connect" every
> time after turning on a PC to connect (to the Internet)? How to automate the
> running the connection and clicking the "Connect" after turning on a PC?
> Best regards,
> Dima

Hello Dima,

One way is to get a router (a wired one is good enough if you don't
need to connect a computer wirelessly). The router sits between your
modem and your computer. The connection settings are stored in the
router, so that it is "always on".

Here's one:
http://www.newegg.com/Product/Produc...82E16833117301

Alternatively, depending on what is required for you to enter to
connect (username, password, etc.) you may be able to run a script at
startup.

=?Utf-8?B?RGltYQ==?= <Dima@discussions.microsoft.com> wrote in
newsC0DCC19-62F0-40C6-9CC8-7D9534C48841@microsoft.com:

> Hello!
> How to prevent the need to run a connection and click the "Connect"
> every time after turning on a PC to connect (to the Internet)? How to
> automate the running the connection and clicking the "Connect" after
> turning on a PC? Best regards,
> Dima
>

To add to the other replies......

Installing a NAT rtr for a stand-alone PC is much better than connecting
it directly to the internet.

While a NAT router is not a *true* firewall, it will protect you from
port scans and such. Maybe you don't think you're PC is getting hit up
from teh outside world, you may be wrong. Here's a log from my rtr...

Friday, January 11, 2008 11:45:19 AM Unrecognized access from
24.64.156.49:18012 to UDP port 1028
Friday, January 11, 2008 11:48:24 AM Unrecognized access from
76.166.208.1:1180 to TCP port 2968
Friday, January 11, 2008 11:48:27 AM Unrecognized access from
76.166.208.1:1180 to TCP port 2968
Friday, January 11, 2008 11:48:33 AM Unrecognized access from
76.166.208.1:1180 to TCP port 2968
Friday, January 11, 2008 11:53:44 AM Unrecognized access from
24.64.51.252:26454 to UDP port 1026
Friday, January 11, 2008 11:53:44 AM Unrecognized access from
24.64.51.252:26454 to UDP port 1027
Friday, January 11, 2008 11:53:44 AM Unrecognized access from
24.64.51.252:26454 to UDP port 1028
Friday, January 11, 2008 11:56:54 AM Unrecognized access from
222.161.2.24:38410 to UDP port 1027
Friday, January 11, 2008 11:58:57 AM Unrecognized access from
125.65.112.152:6000 to TCP port 7212
Friday, January 11, 2008 11:58:57 AM Unrecognized access from
125.65.112.152:6000 to TCP port 8000
Friday, January 11, 2008 12:00:27 PM Unrecognized access from
24.64.22.164:30467 to UDP port 1026
Friday, January 11, 2008 12:00:27 PM Unrecognized access from
24.64.22.164:30467 to UDP port 1027
Friday, January 11, 2008 12:00:27 PM Unrecognized access from
24.64.22.164:30467 to UDP port 1028
Friday, January 11, 2008 12:01:19 PM Unrecognized access from
24.64.5.16:3502 to UDP port 1026
Friday, January 11, 2008 12:01:19 PM Unrecognized access from
24.64.5.16:3502 to UDP port 1027
Friday, January 11, 2008 12:01:19 PM Unrecognized access from
24.64.5.16:3502 to UDP port 1028
Friday, January 11, 2008 12:01:44 PM Unrecognized access from
24.64.181.28:8650 to UDP port 1026
Friday, January 11, 2008 12:01:44 PM Unrecognized access from
24.64.181.28:8650 to UDP port 1027
Friday, January 11, 2008 12:01:44 PM Unrecognized access from
24.64.181.28:8650 to UDP port 1028
Friday, January 11, 2008 12:13:05 PM Unrecognized access from
221.208.208.93:52537 to UDP port 1027
Friday, January 11, 2008 12:13:05 PM Unrecognized access from
221.208.208.93:52537 to UDP port 1026
Friday, January 11, 2008 12:13:05 PM Unrecognized access from
221.208.208.93:52537 to UDP port 1027
Friday, January 11, 2008 12:18:17 PM Unrecognized access from
202.97.238.202:43363 to UDP port 1027
Friday, January 11, 2008 12:18:54 PM Unrecognized access from
209.213.65.234:24093 to TCP port 25
Friday, January 11, 2008 12:30:31 PM Unrecognized access from
24.64.34.16:31578 to UDP port 1026
Friday, January 11, 2008 12:30:31 PM Unrecognized access from
24.64.34.16:31578 to UDP port 1027
Friday, January 11, 2008 12:30:31 PM Unrecognized access from
24.64.34.16:31578 to UDP port 1028
Friday, January 11, 2008 12:31:32 PM Unrecognized access from
121.18.13.107:12200 to TCP port 9788
Friday, January 11, 2008 12:42:02 PM Unrecognized access from
222.161.2.24:46917 to UDP port 1027
Friday, January 11, 2008 12:42:02 PM Unrecognized access from
222.161.2.24:46913 to UDP port 1026
Friday, January 11, 2008 12:45:09 PM Unrecognized access from
202.97.238.202:53088 to UDP port 1026
Friday, January 11, 2008 12:47:35 PM Unrecognized access from
76.166.208.1:1989 to TCP port 2968
Friday, January 11, 2008 12:47:38 PM Unrecognized access from
76.166.208.1:1989 to TCP port 2968
Friday, January 11, 2008 12:47:44 PM Unrecognized access from
76.166.208.1:1989 to TCP port 2968
Friday, January 11, 2008 12:51:59 PM Unrecognized access from
76.166.208.1:2522 to TCP port 2968
Friday, January 11, 2008 12:52:02 PM Unrecognized access from
76.166.208.1:2522 to TCP port 2968
Friday, January 11, 2008 12:52:08 PM Unrecognized access from
76.166.208.1:2522 to TCP port 2968
Friday, January 11, 2008 12:53:31 PM Unrecognized access from
217.204.34.34:24981 to TCP port 10000
Friday, January 11, 2008 12:59:37 PM Unrecognized access from
24.64.159.12:19801 to UDP port 1026
Friday, January 11, 2008 12:59:37 PM Unrecognized access from
24.64.159.12:19801 to UDP port 1027
Friday, January 11, 2008 12:59:37 PM Unrecognized access from
24.64.159.12:19801 to UDP port 1028
Friday, January 11, 2008 1:02:59 PM Unrecognized access from
221.209.110.13:34291 to UDP port 1027
Friday, January 11, 2008 1:04:04 PM Unrecognized access from
222.216.28.161:6000 to TCP port 7212
Friday, January 11, 2008 1:16:15 PM Unrecognized access from
24.64.25.207:11360 to UDP port 1026
Friday, January 11, 2008 1:16:15 PM Unrecognized access from
24.64.25.207:11360 to UDP port 1027
Friday, January 11, 2008 1:16:14 PM Unrecognized access from
24.64.25.207:11360 to UDP port 1028
Friday, January 11, 2008 1:19:15 PM Unrecognized access from
24.64.211.118:29450 to UDP port 1026
Friday, January 11, 2008 1:19:15 PM Unrecognized access from
24.64.211.118:29450 to UDP port 1027
Friday, January 11, 2008 1:19:15 PM Unrecognized access from
24.64.211.118:29450 to UDP port 1028
Friday, January 11, 2008 1:20:20 PM Unrecognized access from
24.64.209.111:30181 to UDP port 1026
Friday, January 11, 2008 1:20:20 PM Unrecognized access from
24.64.209.111:30181 to UDP port 1027
Friday, January 11, 2008 1:20:20 PM Unrecognized access from
24.64.209.111:30181 to UDP port 1028
Friday, January 11, 2008 1:20:50 PM Unrecognized access from
125.65.112.192:6000 to TCP port 8000
Friday, January 11, 2008 1:20:50 PM Unrecognized access from
125.65.112.192:6000 to TCP port 7212
Friday, January 11, 2008 1:26:13 PM Unrecognized access from
202.97.238.203:39349 to UDP port 1026
Friday, January 11, 2008 1:26:13 PM Unrecognized access from
202.97.238.203:39349 to UDP port 1027
Friday, January 11, 2008 1:29:37 PM Unrecognized access from
76.246.111.38:4190 to TCP port 5900
Friday, January 11, 2008 1:29:40 PM Unrecognized access from
76.246.111.38:4190 to TCP port 5900
Friday, January 11, 2008 1:32:11 PM Unrecognized access from
24.64.129.207:12731 to UDP port 1026
Friday, January 11, 2008 1:32:11 PM Unrecognized access from
24.64.129.207:12731 to UDP port 1027
Friday, January 11, 2008 1:32:11 PM Unrecognized access from
24.64.129.207:12731 to UDP port 1028
Friday, January 11, 2008 1:39:15 PM Unrecognized access from
24.64.237.219:29247 to UDP port 1026
Friday, January 11, 2008 1:39:15 PM Unrecognized access from
24.64.237.219:29247 to UDP port 1027
Friday, January 11, 2008 1:39:15 PM Unrecognized access from
24.64.237.219:29247 to UDP port 1028
Friday, January 11, 2008 1:47:09 PM Unrecognized access from
24.64.122.51:10787 to UDP port 1026
Friday, January 11, 2008 1:47:09 PM Unrecognized access from
24.64.122.51:10787 to UDP port 1027
Friday, January 11, 2008 1:47:09 PM Unrecognized access from
24.64.122.51:10787 to UDP port 1028
Friday, January 11, 2008 1:51:47 PM Unrecognized access from
24.64.213.165:20110 to UDP port 1026
Friday, January 11, 2008 1:51:47 PM Unrecognized access from
24.64.213.165:20110 to UDP port 1027
Friday, January 11, 2008 1:51:47 PM Unrecognized access from
24.64.213.165:20110 to UDP port 1028
Friday, January 11, 2008 1:55:20 PM Unrecognized access from
24.64.62.11:18310 to UDP port 1026
Friday, January 11, 2008 1:55:20 PM Unrecognized access from
24.64.62.11:18310 to UDP port 1027
Friday, January 11, 2008 1:55:20 PM Unrecognized access from
24.64.62.11:18310 to UDP port 1028
Friday, January 11, 2008 2:01:07 PM Unrecognized access from
59.63.157.211:6000 to TCP port 7212
Friday, January 11, 2008 2:01:07 PM Unrecognized access from
59.63.157.211:6000 to TCP port 8000
Friday, January 11, 2008 2:09:47 PM Unrecognized access from
125.65.112.152:6000 to TCP port 7212
Friday, January 11, 2008 2:09:47 PM Unrecognized access from
125.65.112.152:6000 to TCP port 8000
Friday, January 11, 2008 2:09:59 PM Unrecognized access from
24.64.98.94:10664 to UDP port 1026
Friday, January 11, 2008 2:09:59 PM Unrecognized access from
24.64.98.94:10664 to UDP port 1027
Friday, January 11, 2008 2:09:59 PM Unrecognized access from
24.64.98.94:10664 to UDP port 1028
Friday, January 11, 2008 2:13:24 PM Unrecognized access from
24.64.55.154:11688 to UDP port 1026
Friday, January 11, 2008 2:13:24 PM Unrecognized access from
24.64.55.154:11688 to UDP port 1027
Friday, January 11, 2008 2:13:24 PM Unrecognized access from
24.64.55.154:11688 to UDP port 1028
Friday, January 11, 2008 2:23:59 PM Unrecognized access from
38.20.8.177:30663 to UDP port 1026
Friday, January 11, 2008 2:24:36 PM Unrecognized access from
218.10.137.141:60864 to UDP port 1027
Friday, January 11, 2008 2:24:58 PM Unrecognized access from
125.65.113.4:12200 to TCP port 8000
Friday, January 11, 2008 2:26:27 PM Unrecognized access from
24.64.126.160:29861 to UDP port 1026
Friday, January 11, 2008 2:26:27 PM Unrecognized access from
24.64.126.160:29861 to UDP port 1027
Friday, January 11, 2008 2:26:27 PM Unrecognized access from
24.64.126.160:29861 to UDP port 1028
Friday, January 11, 2008 2:32:46 PM Unrecognized access from
24.64.7.44:11262 to UDP port 1026
Friday, January 11, 2008 2:32:46 PM Unrecognized access from
24.64.7.44:11262 to UDP port 1027
Friday, January 11, 2008 2:32:46 PM Unrecognized access from
24.64.7.44:11262 to UDP port 1028
Friday, January 11, 2008 2:53:30 PM Unrecognized access from
24.64.33.75:25400 to UDP port 1026
Friday, January 11, 2008 2:53:30 PM Unrecognized access from
24.64.33.75:25400 to UDP port 1027
Friday, January 11, 2008 2:53:30 PM Unrecognized access from
24.64.33.75:25400 to UDP port 1028
Friday, January 11, 2008 2:54:40 PM Unrecognized access from
202.97.179.126:40855 to UDP port 1434
Friday, January 11, 2008 3:04:14 PM Unrecognized access from
218.10.137.140:37219 to UDP port 1026
Friday, January 11, 2008 3:04:14 PM Unrecognized access from
218.10.137.140:37220 to UDP port 1027
Friday, January 11, 2008 3:06:45 PM Unrecognized access from
24.64.16.169:3144 to UDP port 1026
Friday, January 11, 2008 3:06:45 PM Unrecognized access from
24.64.16.169:3144 to UDP port 1027
Friday, January 11, 2008 3:06:45 PM Unrecognized access from
24.64.16.169:3144 to UDP port 1028
Friday, January 11, 2008 3:07:25 PM Unrecognized access from
76.18.84.140:1702 to TCP port 2967
Friday, January 11, 2008 3:07:28 PM Unrecognized access from
76.18.84.140:1702 to TCP port 2967
Friday, January 11, 2008 3:07:34 PM Unrecognized access from
76.18.84.140:1702 to TCP port 2967
Friday, January 11, 2008 3:08:58 PM Unrecognized access from
24.64.29.150:20563 to UDP port 1026
Friday, January 11, 2008 3:08:58 PM Unrecognized access from
24.64.29.150:20563 to UDP port 1027
Friday, January 11, 2008 3:08:58 PM Unrecognized access from
24.64.29.150:20563 to UDP port 1028
Friday, January 11, 2008 3:24:34 PM Unrecognized access from
24.64.189.19:13018 to UDP port 1026
Friday, January 11, 2008 3:24:34 PM Unrecognized access from
24.64.189.19:13018 to UDP port 1027
Friday, January 11, 2008 3:24:34 PM Unrecognized access from
24.64.189.19:13018 to UDP port 1028
Friday, January 11, 2008 3:37:01 PM Unrecognized access from
125.65.112.192:6000 to TCP port 8000
Friday, January 11, 2008 3:37:01 PM Unrecognized access from
125.65.112.192:6000 to TCP port 7212
Friday, January 11, 2008 3:37:13 PM Unrecognized access from
24.64.101.180:6149 to UDP port 1026
Friday, January 11, 2008 3:37:13 PM Unrecognized access from
24.64.101.180:6149 to UDP port 1027
Friday, January 11, 2008 3:37:13 PM Unrecognized access from
24.64.101.180:6149 to UDP port 1028
Friday, January 11, 2008 3:43:24 PM Unrecognized access from
125.65.113.4:12200 to TCP port 8000
Friday, January 11, 2008 3:43:43 PM Unrecognized access from
121.18.13.107:12200 to TCP port 9788
Friday, January 11, 2008 3:46:34 PM Unrecognized access from
24.64.10.158:16572 to UDP port 1026
Friday, January 11, 2008 3:46:34 PM Unrecognized access from
24.64.10.158:16572 to UDP port 1027
Friday, January 11, 2008 3:46:34 PM Unrecognized access from
24.64.10.158:16572 to UDP port 1028
Friday, January 11, 2008 3:53:12 PM Unrecognized access from
24.64.106.187:14890 to UDP port 1026
Friday, January 11, 2008 3:53:12 PM Unrecognized access from
24.64.106.187:14890 to UDP port 1027
Friday, January 11, 2008 3:53:12 PM Unrecognized access from
24.64.106.187:14890 to UDP port 1028
Friday, January 11, 2008 4:13:27 PM Unrecognized access from
72.45.218.126:1188 to TCP port 80
Friday, January 11, 2008 4:13:30 PM Unrecognized access from
72.45.218.126:1188 to TCP port 80
Friday, January 11, 2008 4:13:36 PM Unrecognized access from
72.45.218.126:1188 to TCP port 80
Friday, January 11, 2008 4:13:48 PM Unrecognized access from
72.45.218.126:1188 to TCP port 80
Friday, January 11, 2008 4:14:26 PM Unrecognized access from
222.161.2.24:40946 to UDP port 1026
Friday, January 11, 2008 4:16:24 PM Unrecognized access from
221.209.110.50:40618 to UDP port 1026
Friday, January 11, 2008 4:21:48 PM Unrecognized access from
125.65.112.152:6000 to TCP port 7212
Friday, January 11, 2008 4:21:48 PM Unrecognized access from
125.65.112.152:6000 to TCP port 8000
Friday, January 11, 2008 4:24:23 PM Unrecognized access from
202.97.238.204:46130 to UDP port 1026
Friday, January 11, 2008 4:27:52 PM Unrecognized access from
24.64.175.188:31565 to UDP port 1026
Friday, January 11, 2008 4:27:52 PM Unrecognized access from
24.64.175.188:31565 to UDP port 1027
Friday, January 11, 2008 4:27:52 PM Unrecognized access from
24.64.175.188:31565 to UDP port 1028
Friday, January 11, 2008 4:37:03 PM Unrecognized access from
222.161.2.24:34099 to UDP port 1026
Friday, January 11, 2008 4:39:50 PM Unrecognized access from
59.63.157.211:6000 to TCP port 7212
Friday, January 11, 2008 4:39:50 PM Unrecognized access from
59.63.157.211:6000 to TCP port 8000
Friday, January 11, 2008 4:42:18 PM Unrecognized access from
24.64.166.46:26920 to UDP port 1026
Friday, January 11, 2008 4:42:18 PM Unrecognized access from
24.64.166.46:26920 to UDP port 1027
Friday, January 11, 2008 4:42:18 PM Unrecognized access from
24.64.166.46:26920 to UDP port 1028
Friday, January 11, 2008 4:57:35 PM Unrecognized access from
121.18.13.107:12200 to TCP port 9788
Friday, January 11, 2008 4:57:35 PM Unrecognized access from
121.18.13.107:12200 to TCP port 7788
Friday, January 11, 2008 4:57:35 PM Unrecognized access from
121.18.13.107:12200 to TCP port 7212
Friday, January 11, 2008 5:01:28 PM Unrecognized access from
76.166.208.1:2773 to TCP port 2968
Friday, January 11, 2008 5:01:31 PM Unrecognized access from
76.166.208.1:2773 to TCP port 2968
Friday, January 11, 2008 5:01:37 PM Unrecognized access from
76.166.208.1:2773 to TCP port 2968
Friday, January 11, 2008 5:02:47 PM Unrecognized access from
125.65.113.4:12200 to TCP port 8000
Friday, January 11, 2008 5:02:47 PM Unrecognized access from
125.65.113.4:12200 to TCP port 3128
Friday, January 11, 2008 5:06:52 PM Unrecognized access from
24.64.57.88:32908 to UDP port 1026
Friday, January 11, 2008 5:06:52 PM Unrecognized access from
24.64.57.88:32908 to UDP port 1027
Friday, January 11, 2008 5:06:52 PM Unrecognized access from
24.64.57.88:32908 to UDP port 1028
Friday, January 11, 2008 5:07:51 PM Unrecognized access from
24.64.29.56:7053 to UDP port 1026
Friday, January 11, 2008 5:07:51 PM Unrecognized access from
24.64.29.56:7053 to UDP port 1027
Friday, January 11, 2008 5:07:51 PM Unrecognized access from
24.64.29.56:7053 to UDP port 1028
Friday, January 11, 2008 5:09:35 PM Unrecognized access from
76.119.56.81:1671 to TCP port 2967
Friday, January 11, 2008 5:09:38 PM Unrecognized access from
76.119.56.81:1671 to TCP port 2967
Friday, January 11, 2008 5:13:44 PM Unrecognized access from
121.18.13.107:12200 to TCP port 9788
Friday, January 11, 2008 5:24:54 PM Unrecognized access from
222.161.2.24:44833 to UDP port 1027
Friday, January 11, 2008 5:27:01 PM Unrecognized access from
202.97.238.194:53748 to UDP port 1026
Friday, January 11, 2008 5:27:01 PM Unrecognized access from
202.97.238.194:53748 to UDP port 1027
Friday, January 11, 2008 5:27:01 PM Unrecognized access from
202.97.238.194:53749 to UDP port 1026
Friday, January 11, 2008 5:29:38 PM Unrecognized access from
121.18.13.107:12200 to TCP port 9788
Friday, January 11, 2008 5:30:01 PM Unrecognized access from
24.64.67.52:31712 to UDP port 1026
Friday, January 11, 2008 5:30:01 PM Unrecognized access from
24.64.67.52:31712 to UDP port 1027
Friday, January 11, 2008 5:30:01 PM Unrecognized access from
24.64.67.52:31712 to UDP port 1028
Friday, January 11, 2008 5:30:16 PM Unrecognized access from
222.216.28.161:6000 to TCP port 7212
Friday, January 11, 2008 5:32:03 PM Unrecognized access from
221.208.208.97:36274 to UDP port 1026
Friday, January 11, 2008 5:44:27 PM Unrecognized access from
121.18.13.107:12200 to TCP port 9788
Friday, January 11, 2008 5:44:27 PM Unrecognized access from
121.18.13.107:12200 to TCP port 7788
Friday, January 11, 2008 5:44:27 PM Unrecognized access from
121.18.13.107:12200 to TCP port 7212
Friday, January 11, 2008 5:47:25 PM Unrecognized access from
24.64.193.48:34077 to UDP port 1026
Friday, January 11, 2008 5:47:25 PM Unrecognized access from
24.64.193.48:34077 to UDP port 1027
Friday, January 11, 2008 5:47:25 PM Unrecognized access from
24.64.193.48:34077 to UDP port 1028
Friday, January 11, 2008 5:48:46 PM Unrecognized access from
222.161.2.24:43316 to UDP port 1027

Now, your PC's no going to do anything unless there is a piece of s/w
running listening on those ports, like a server you might want to run for
some reason or another, or Windows firewall would stop it also, but why
have those packets hitting your PC unless absolutely necessary ?

Here's another one....do you rememebr the Sasser worm from a few years
back ? (I think it was Sasser....) The RPC issue, where you didn't need
to run anyting, just being connecting to the internet was how to be
infected. Guess what, just about noone that was using a NAT rtr was
infected. Need I say more ?

Router is your best option, thought to automate the connection, go into
Network Connections and right-click the 'connectoid' for the modem. Select
"Create Shortcut" and answer OK to "Desktop"

Transfer the shortcut to the Startup folder (under All Programs) on the
Start Menu.

Why do it that way?
In the Network connections folder there will be the icon for the LAN and as
long as the check box is checked/ticked then the connected icon will show on
the task bar anyway and when the pc boots up, the connection will already be
there.


"Anteaus" <Anteaus@discussions.microsoft.com> wrote in message
news:CC971899-7266-47EA-B188-FCE9CE957FAF@microsoft.com...
>
> Router is your best option, thought to automate the connection, go into
> Network Connections and right-click the 'connectoid' for the modem. Select
> "Create Shortcut" and answer OK to "Desktop"
>
> Transfer the shortcut to the Startup folder (under All Programs) on the
> Start Menu.
>
>

The ADSL internet connection requires username and password input in the
beginning of a connection. How to automate the username and password input?
Best regards,
Dima
"Fiddler" wrote:

> Why do it that way?
> In the Network connections folder there will be the icon for the LAN and as
> long as the check box is checked/ticked then the connected icon will show on
> the task bar anyway and when the pc boots up, the connection will already be
> there.
>
>
> "Anteaus" <Anteaus@discussions.microsoft.com> wrote in message
> news:CC971899-7266-47EA-B188-FCE9CE957FAF@microsoft.com...
> >
> > Router is your best option, thought to automate the connection, go into
> > Network Connections and right-click the 'connectoid' for the modem. Select
> > "Create Shortcut" and answer OK to "Desktop"
> >
> > Transfer the shortcut to the Startup folder (under All Programs) on the
> > Start Menu.
> >
> >
>
>
>

Like it has been said, get an ADSL router.
Then you enter ALL user information into the router.
Then you do NOT have to "log in/on".
A router is meant to stay on all the time.
That means even when the pc is turned off, the internet connection still
there.
When you turn the pc on then the internet connection will be there ready.
You do NOT need to"automate"anything with a router.
Modem maybe, router NO.
ADSL modem =log on manually
Router=all set in the router.


"Dima" <Dima@discussions.microsoft.com> wrote in message
news:112BA692-E939-427D-94DC-BE80054AFEED@microsoft.com...
> The ADSL internet connection requires username and password input in the
> beginning of a connection. How to automate the username and password
> input?
> Best regards,
> Dima
> "Fiddler" wrote:
>
>> Why do it that way?
>> In the Network connections folder there will be the icon for the LAN and
>> as
>> long as the check box is checked/ticked then the connected icon will show
>> on
>> the task bar anyway and when the pc boots up, the connection will already
>> be
>> there.
>>
>>
>> "Anteaus" <Anteaus@discussions.microsoft.com> wrote in message
>> news:CC971899-7266-47EA-B188-FCE9CE957FAF@microsoft.com...
>> >
>> > Router is your best option, thought to automate the connection, go
>> > into
>> > Network Connections and right-click the 'connectoid' for the modem.
>> > Select
>> > "Create Shortcut" and answer OK to "Desktop"
>> >
>> > Transfer the shortcut to the Startup folder (under All Programs) on the
>> > Start Menu.
>> >
>> >
>>
>>
>>
>