Win2K SP4 - Problem setting up an Internet (dialup) Connection

  • Thread starter Thread starter RF
  • Start date Start date
R

RF

While trying to setup an Internet Connection (dialup) on Box 1 a few weeks
ago I came across an odd situation.

Everything went well from "Make New Connection" - via the Wizard. First
there were only 2 choices : Dialup Internet and Accept incoming connections.
The other two choices were greyed out. I set Dialup Internet up manually -
connect thru phone line..., gave phone number, clicked next. Next up was
Username and Pword. and finally the Connection name needed to be specified.
No matter what I entered into that box I got the message

"The entry must contain at least one character that is not a space and
cannot begin with a period. Choose a different name."

I tried a dozen names and all were rejected. Has anyone ever seen this
before? Could it be that I have a bug? I am using a very recent Ad-Aware
program.

TIA
 
philo said:
If this does not do the trick then your system is corrupted


http://www.ontimeservices.com/Default.aspx?tabid=73


Thanks Philo for your response. I have had more computer problems in the
past 6 weeks than in my whole computer life and that goes back to 1984.
I am now deeply suspicious of allowing anything to enter my computer
unless I know that the provider has a good reputation. I know nothing
about this Ontimeservices. Is it reputable? and does it actually probe
my computer? or just do a slide show or what?

I'll be posting some of my recent woes soon and hope that we all can
learn from them.
 
philo said:
Well you need flash player to full all the contents...
however without flash, you can still read the text.

all the link did was list the steps for creating a connection
there are plenty of other tutorial to be found by just doing a Google
search

Thanks again Philo,

I did some more research today and came across the following link:

http://support.microsoft.com/kb/319162

M$ gave two possible reasons for this problem - mine did not include
these, so that puts M$ back at square 1 :-).

This was their guess:
"This issue may occur in the following situation:

* You upgrade the computer from a previous operating system to
Windows 2000.

-and-
* Some of the Windows 2000 Routing and Remote Access components
were not installed correctly."
 
RF said:
Thanks again Philo,

I did some more research today and came across the following link:

http://support.microsoft.com/kb/319162

M$ gave two possible reasons for this problem - mine did not include
these, so that puts M$ back at square 1 :-).

This was their guess:
"This issue may occur in the following situation:

* You upgrade the computer from a previous operating system to
Windows 2000.

-and-
* Some of the Windows 2000 Routing and Remote Access components were
not installed correctly."

I finally found a "solution" that was claimed by some to solve the
problem. This was the gist of the story:

"Solution
by lseefeld - 6/24/06 9:56 AM In reply to: Won't connect bc of error 6
and 50 - request not supported by lseefeld

This issue can occur if the RAS or NDISWAN component is corrupted. The
problem can occur after removing some 3rd party program such as AT&T
dial up program because the uninstallation program may not be designed
very well. To troubleshoot this issue, please perform the following
steps.

1. Remove Modem driver from the Device Manager.
- Right click My Computer and select Properties.
- Click on Hardware, Device Manager. Click on + sign by modem, right
click and uninstall modem.
2. Delete the dial up connections and remove 3rd party RAS related
program if any.
3. Run the attached file to install RArepair.exe, then run RArepair.exe
to reinstall RAS components. Reboot.
4. Reinstall Modem driver and the 3rd party dial up program if it is
required by your ISP.
5. Recreate the dial up connection and check if the problem is resolved."

I removed those items mentioned above - the network cards, modem,
drivers, tcp/ip, network programs, etc and visited Device Manager which
showed no trace of modems or network cards. Next I ran rarepair.exe It
indicated it was removing some programs, took about 15 secs to run and
then it suggested rebooting. After that the prog opened again and
started the reinstallation. I rebooted again and then I went back to
check if it was possible to setup dialup networking. As before 3 of the
5 selections Dialup a private network, Dialup the internet, etc were
greyed out. So obviously the problem was not solved.

There was a suggestion that this problem was probably caused by removing
badly written DSL programs, like those of AT&T - maybe its kiss of
death. I am beginning to believe that now. I had two computers with its
DSL and both are barely usable now. I may have to completely reinstall them.

Comments appreciated.
 
Back
Top