Setup Dreamcast to use Win2k connection by mc Gonzalez (Win2k Tips & Tricks)
You're reading a tutorial located at Kinox - The Emu Scene Dump, one of the most reliable source for news about the scene (pay us a visit, you won't regret!). This is a graphic tutorial on configuring Windows 2000 so your Dreamcast can use the connection to play games. All rights reserved to mc Gonzalez, its author.
STEP 1:
The first thing you want to do is bring up routing and remote access, I do most things in Windows 2k from the computer management window. You need to make certain it is set for WAN and Lan routing, along with functioning as a remote access server. When you right click on R&R and choose properties, the general tab should look as it does in this example.
STEP 2:
After that is set, for this to work it needs a static address pool. I was
using DHCP relaying, using my Linksys Hardware firewall to control the dial
access clients as well, but the routing did not work. So, I set the static pool,
on the same requester's IP tab, to a subset of the IP's that the linksys
furnishes, but high enough as to not interfere with the hardware clients.
STEP 3:
On the same dialog again, now we need the security tab. I am not really
concerned with accounting for this purpose, so I have that set to none. But the
second pop up box there, if you push the Authentication methods button, you can
select what type of log in is to be used. You can have more than one. I chose
Chap, as I knew, since the Dreamcast was using Worldnet for it's primary ISP, it
had to be able to use this auth method.
STEP 4:
On to a different page finally. A Static route is needed. Just remember 0's.
Plus open IP routing, and highlight Static routes.
STEP 5:
make a new static route (right click, all task) and set it thusly:
STEP 6:
Now at this point, I was able to log in with another PC, well I also had
MSCHAP active in the methods, but not from the Dreamcast. There were a couple of
things stopping me, any guesses what they were?
The first one was relatively easy to figure out, event viewer told me that there was no reversible encryption password stored for this account. I can fix that I said. So, to my user to edit it, note if you do not have active directory installed, you can just use the local users and groups tool in computer management for this. It is simple, check the box on the account tab to store the password for the account in reversible encryption. Also, Make certain that the account is allowed to dial in on the dial in tab.
STEP 7:
Ok, now I am all excited, this is going to work I said to myself. Of course
it didn't. At this point, the pain killer I was imbibing for a toothache was
starting to get to me. Readers who have worked with NT security will know, I am
certain, what I have forgotten, but it puzzled me for a bit. Event viewer was no
help. It told me chap failed, before I stored the password in reversible
encryption, but now it was telling me it was failing because it attempted to use
an unauthorized authentication method.
Man, do I feel dumb...
STEP 8:
Back to Routing and remote access. Hmmm, I wonder what this policy action is
all about... Get the properties, well this is no help:
I wonder what is under the edit profile button
STEP 9:
Bingo! Chap was not checked, as it is now.
It now functions properly. The Dreamcast can log into my server, and has full access to the Road Runner account. Granted, as we are dealing with V90 modems, the connect is V34, but for it's intended purpose, the boy is quite happy with it. Who knows, I may take a turn or two surfing on the 32" screen.