| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 50811 | 2004-11-02 07:45:00 | Dialup starts automatically | jferg (3232) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 287180 | 2004-11-04 09:18:00 | It's a standalone Once dialed up it doesn't connect to anything that I can see and I'll check out those 3 update files Thanks It is a real pain thou I've started uninstalling programs that I think might be the cause |
jferg (3232) | ||
| 287181 | 2004-11-04 09:33:00 | > It's a standalone > Once dialed up it doesn't connect to anything that I > can see > and I'll check out those 3 update files > Thanks > > It is a real pain thou > I've started uninstalling programs that I think might > be the cause Stop rihgt there,Its obviously a program running in the background,Dont go uninstalling everything,just disable everything under startup and reboot,if it doesn't dial up(99 percent chance it wont)then start re-enabling the items one by one untill it tries to dial up,then u have your culprit,should only take a few minutes.... |
metla (154) | ||
| 287182 | 2004-11-05 03:19:00 | Ok...Opened msconfig Disabled all startup programs, rebooted but dial up still started Back to msconfig and reenabled programs Disabled allprograms under the services tab Rebooted and it had stopped AHA! By Process of illimination..Telephony had to be enabled to track down culprit. Turns out that all but "Remote access auto conection manager" by microsoft can be enabled in the services tab, stops the dialup starting on bootup. In otherwords "Remote access auto conection manager" program in the services Tab in msconfig starts the Dialup. Is this file necessary? How can I get rid of it? and Are my conclusions plusable? Jeff |
jferg (3232) | ||
| 1 2 3 4 | |||||