PDA

View Full Version : Anyone figure out how to get W2Kpro to auto dialup?


jbslow
12-20-01, 12:31 PM
I'm still manualy connecting both of my machines to send and recieve WU and its getting to be a bother plus I'm loosing a decent amount of folding time in between WU. Sometimes I'm not home sometimes I'm a sleep not to mention when I go on a trip or vacation all those wasted WU.

muddocktor
12-20-01, 03:23 PM
I finally got mine to auto-dial, but it's a bit different than Win98. Basically I looked in the Win2k help files(:eek: ) and looked up dialup connections and under it there is an entry for automating. Click on it and in the right hand pane is a link to autodial, click on it. It then shows a couple of links to configure autodial and to start the remote access auto connection manager. You will have to go into both of them and follow the steps, which are fairly easy. After you've done this it will be configured and close out the help files. However, the next time that you finish a WU, you will still have to be around because it will open a box asking if you want to connect. It will then ask you which connection to use and also if you want to be asked all that cr** again later. Be sure that you tell it not to ask again. I hope this explanation is clear enough for you; it was a pain to figure it all out. Good luck and if you run into a problem, post back here and we'll try to figure what's going wrong. Now, it's time for a :beer:

Ploaf
12-20-01, 04:04 PM
I've seen this come up a few times and It seems to be the first time it's been answered, although I could have missed it. Anyway, it would be great if we could get a small instructional write up on it in the faq thread. Please. :)

jbslow
12-20-01, 04:37 PM
Originally posted by muddocktor
I finally got mine to auto-dial, but it's a bit different than Win98. Basically I looked in the Win2k help files(:eek: ) and looked up dialup connections and under it there is an entry for automating. Click on it and in the right hand pane is a link to autodial, click on it. It then shows a couple of links to configure autodial and to start the remote access auto connection manager. You will have to go into both of them and follow the steps, which are fairly easy. After you've done this it will be configured and close out the help files. However, the next time that you finish a WU, you will still have to be around because it will open a box asking if you want to connect. It will then ask you which connection to use and also if you want to be asked all that cr** again later. Be sure that you tell it not to ask again. I hope this explanation is clear enough for you; it was a pain to figure it all out. Good luck and if you run into a problem, post back here and we'll try to figure what's going wrong. Now, it's time for a :beer:

Nice thanks!

I've done it and the "autodial" was already configured but had to start "remote access auto connection manager" , but I do have a few questions.

What else do I need to do to ensure the system will autodial when the WU's are finished? I mean I didnt enter anything to specify when and where I need to connect how is it going to know that when I finish a WU I need to get connected? This is going to solve the sucurity password issue right?

muddocktor
12-20-01, 04:54 PM
Ploaf,
I was planning to do that very thing as soon as I was sure that someone besides me will understand my directions.:D I'll try to clean it up and make it all pretty for the FAQ. Also, we need a mod or someone to capitalize the thread title; it looks too much like someone advertizing for an alternate sexual lifestyle.:D :D

jbslow,
The first time that it goes to connect, after starting the remote access auto connection manager and enabling auto dialup, it will ask if you want to connect. Then, it will ask you which connection to use, even if you only have 1 dialup account on the computer. Then it will ask if you want to be asked all this again before dialing the next time. Be sure to tell it not to ask again or the next time it finishes a WU, it will come up with this same dialogue again. The only problem that I've run into since enabling all 3 of my boxes to automatically dialup is that one time I had 2 computers finish a WU at nearly the same time and the second one was stuck until I came and checked and found a little box asking if I wanted to try redialing the number:mad: instead of just trying to dial in again by itself. Also, be sure to set the dialup to automatically disconnect after 5-10 minutes instead of relying on your ISP to knock you off for inactivity. As far as the password goes, I have my password automatically "remembered". I don't think that you can automate unless you tell your dialup to remember your password.

Ploaf
12-20-01, 05:27 PM
Originally posted by muddocktor
Ploaf,
I was planning to do that very thing as soon as I was sure that someone besides me will understand my directions.:D I'll try to clean it up and make it all pretty for the FAQ. Also, we need a mod or someone to capitalize the thread title; it looks too much like someone advertizing for an alternate sexual lifestyle.:D :D


Thanks Muddocktor,
It looks good. :D I asked SpeeDj if he could fix the title of the FAQ thread so it looked a little less offensive. I think the mods can do that, hope so :)

jbslow
12-20-01, 05:41 PM
Originally posted by muddocktor

jbslow,
............................As far as the password goes, I have my password automatically "remembered". I don't think that you can automate unless you tell your dialup to remember your password.

Well thats the problem when I select "save the password" it always saves some long other wrong password. I've reinstalled the ISP software didnt help , I've used the IE dialup software didnt help so I guess I'm stuck...any ideas?

muddocktor
12-20-01, 06:03 PM
So Win2K will also do the old Micro$oft "screwed up password" routine, just like 95 and 98 would do? I thought they had fixed that. I read about fixing it on 95 or 98 a long time ago but forgot what to do. You might try posting over in the OS section and see if you can get someone who knows Win2K better to help you.

jbslow
12-20-01, 06:54 PM
Originally posted by muddocktor
I finally got mine to auto-dial, but it's a bit different than Win98. Basically I looked in the Win2k help files(:eek: ) and looked up dialup connections and under it there is an entry for automating. Click on it and in the right hand pane is a link to autodial, click on it. It then shows a couple of links to configure autodial and to start the remote access auto connection manager. You will have to go into both of them and follow the steps, which are fairly easy. After you've done this it will be configured and close out the help files. However, the next time that you finish a WU, you will still have to be around because it will open a box asking if you want to connect. It will then ask you which connection to use and also if you want to be asked all that cr** again later. Be sure that you tell it not to ask again. I hope this explanation is clear enough for you; it was a pain to figure it all out. Good luck and if you run into a problem, post back here and we'll try to figure what's going wrong. Now, it's time for a :beer:

Well cr** I just finished a WU and the only box that opened up was the folding@home client asking if I was ready to connect to the network. So what could be wrong as far as I can tell I did exactly what you told me is there something left out?

Ploaf
12-20-01, 07:11 PM
Originally posted by jbslow


Well cr** I just finished a WU and the only box that opened up was the folding@home client asking if I was ready to connect to the network. So what could be wrong as far as I can tell I did exactly what you told me is there something left out?

Did you tell the client to ask before connecting?
It may need to be reconfigured.

It's a good time to do it since you just sent in the protein and can't lose several hours worth of work. Try deleting the client.cfg and start over.

belorsch
12-20-01, 07:19 PM
I think this would have already been covered somewhere but I'll ask anyway. Is your client config set to ask before connecting to network? If you have graphical version its easy enough to check. Just right click icon in systray and make sure that box is unchecked. If you have the console client you'll have to stop it with ctrl+c and then use the -config command I think. If you know about all this already just ignore this post:) G'night:beer:

Durn ploaf your just to fast for me:beer:

jbslow
12-20-01, 07:58 PM
Originally posted by Ploaf


Did you tell the client to ask before connecting?
It may need to be reconfigured.

It's a good time to do it since you just sent in the protein and can't lose several hours worth of work. Try deleting the client.cfg and start over.

Ok I deleted the config file and work folder then restarted and the configuration opened on its own so I put in my name and my team number and made sure it wasnt set to ask before connecting. After I pressed ok the configuration prompt stayed open and the graphical prompt opened it read loading.....benchmarking , I let it sit for maybe 5 min but I never got any promt asking if I wanted to connect or anything so I logged on manually and the work file was then uploaded and here I am. I guess I must have set up the autodial wrong:confused: :confused: are you sure I dont need to have some outside program installed for this to work properly?

Ploaf
12-20-01, 08:14 PM
That I don't know. Reboot? Win2k can usually set networking info up without a reboot, especially dial up, but it never hurts. I don't even have a way to test it out to see what will work and won't or I'd have probably spent half the night trying this out, just to find an answer.

Is everything else connecting automatically now? IE, email clients, etc.?

muddocktor
12-20-01, 08:50 PM
These are all the settings that I have on my 2 Win2K machines:

remote access auto connection manager service - started

Network and Dialup Connections:
preferences(under advanced) - enable autodial by location is checked, nothing else is checked

Dialup properties:
display progress while connecting is checked
prompt for name and password, certificates, etc. is checked
redial attempts is set to 5
time between redial attempts is set to 1 minute
idle time before hanging up is set to 10 minutes
redial if line is dropped is checked

Client config:
Use proxy server is checked
Use internet explorer proxy settings is checked.

Both of my Win2K computers will autodial with these settings

sifu quoc
12-20-01, 09:10 PM
i usta ask this question...

goto config

then administrative tools

then services

then i think its remote access auto connection manager...

then set it to automatic instead of manual....

dont forget to set stuff in internet options

to test it, open up ie without dialing....

jbslow
12-20-01, 09:40 PM
Ploaf , yes the IE auto connects , the mail will auto connect and the Windows update will auto connect the comp but it hasn't been connecting the folding program. It's not auto dialing when I use my ISP dialup connector though I also need to enter the password manually using the ISP's dialup.

muddoctor and sifu quoc , I made some of the changes so I would match your setting but its still not connecting when the folding program needs to.

There has got to be a way to link the folding client to open the IE when it needs to get WU right?

jbslow
12-20-01, 10:13 PM
Haha well the duron system just finished a WU and it did ask me a few things and then it auto dialed so now I just need to get the main rig up and running correctly.

Ploaf
12-20-01, 10:23 PM
Well that's good news. :) One down one to go. :D
Good Luck with the main rig.

jbslow
12-20-01, 11:00 PM
Argg...well after I got a new WU ith the duron system I looked at some of the setting and the one that caught my eye was the fold client was set to "ask before connecting".

Dialup properties:
display progress while connecting was not checked
prompt for name and password, certificates, etc. was not checked
redial attempts is set to 5
time between redial attempts is set to 1 minute
idle time before hanging up is set to 10 minutes
redial if line is dropped was not checked

Then I rebooted cause when I went back after my previous post the system was froze or at least I didn't have mouse or keyboard control then I watched expecting the system auto connect on its own and well nothing happened the prompt just came up asking if I was ready to connect to the network *shrug*. Well I'm officially ticked off I cant believe it only worked once then froze and I didn't check all the setting so I'm not sure if anything changed.

jbslow
12-21-01, 02:59 PM
Ok I have it working I'm not sure what my malfunction was ast night or maybe I do :beer: :beer: ....lol.

This morning before leaving I went into "services" and founf I had only started the "remote access connection manager" but I forgot to start the "remote access auto connection manager" so after starting bot services correctly I've now got it auto dialing...sweet. I did come home today to find both comps stuck at diap up with a prompt saying connection has failed invalid user id or password. Now all I need to do is fix the password issue I think if I remove the second hand diapup software I will beable to save the correct password and have true auto connecting comps...I hope.

jbslow
12-21-01, 05:50 PM
Ok it works now I can leave the comps on and they will automatically send and recieve with out any help. The only possible problems are if the OS needs to be rebooted or the two comps go to dialup at the same time so I can pretty much count on a constent production whether I am home or not.

Thank you muddoctor, ploaf , sifu quoc and belorsch!

P.S.

I feel like I'm talking to myself now the last three posts are all mine :( .

Ploaf
12-21-01, 05:52 PM
:D :D :D Great news!
Glad you got it worked out now. and another one.... :D

belorsch
12-21-01, 06:44 PM
Originally posted by jbslow
Ok it works now I can leave the comps on and they will automatically send and recieve with out any help. The only possible problems are if the OS needs to be rebooted or the two comps go to dialup at the same time so I can pretty much count on a constent production whether I am home or not.

Thank you muddoctor, ploaf , sifu quoc and belorsch!

P.S.

I feel like I'm talking to myself now the last three posts are all mine :( .

Sorry, I've been reading but I only contribute if I think I have something that might help :) I have good news too. I finally got my second 98 machine autodialing. Guess what did it for me?? Netscape was my default browser:eek: I changed to IE and its worked once so far.

muddocktor
12-21-01, 08:56 PM
jbslow,
I'm glad you finally got it working! The only time I've had a problem with my 3 machines is that once I had 2 of them try to dial in at almost the same time and the second 1 was stuck untill I told it to redial.