This is to help users of Windows NT 3.5x WS to use RAS to connect to
an Internet Service Provider, (ISP).
1. TCP/IP Setup
a. Open your main folder, then control panel. Then, open
network. check you list of Installed Network Software. You
should see a list with Computer Browser, NetBIOS Interface,
RPC Configuration, Server & Workstation. You may have
additional software, depending on any previous installs. If
TCP/IP Protocol is not already listed, click on Add Software
and scroll till you see TCP/IP and Other Related Components,
and add it.
b. Next, highlight TCP/IP and click on configure in your Network
Settings window. Your next window is TCP/IP Configuration.
Click on the DNS button. Under the part of the next window
that says Domain Name Service (DNS) Search Order, add the DNS
number 207.176.80.80. Then click ADD. Add a backup DNS number
of 207.176.80.88 and click ADD. Then click OK. Now,
click OK again. TCP/IP configuration is done.
2. Switch.inf Editing
a. (TCP/IP and your other services should be updated by now and
you can re-boot now or wait till we are finished.) Now exit
out of control panel and open Notepad. Open the file
winnt35/system32/ras/switch.inf. This is the RAS dialing
script file. Here is an example to follow:
------------------------------------------------------
[SCRIPT NAME]
; Wait until we get the "name:" prompt
COMMAND=
OK="name:"
; Give the account and wait for "password:" prompt
COMMAND=username
OK="word:"
; Give the password and wait for the annex: prompt
COMMAND=password
OK="annex:"
; Give the menu command and ignore response (we're done)
COMMAND=2
OK=
------------------------------------------------------
b. The bracketed text is the name of this script. Name it
anything you want. The 2nd segment is the starting place to
edit. "username" is where your put your username. Edit
"username" out and replace with your user name. Next, edit
"password" out and replace with your password.
c. Now save as switch.inf and exit. Important to save as
switch.inf in your ras sub-directory. Now exit notepad.
3. RAS Setup
a. Now, assuming RAS is installed, open the RAS folder. (If RAS
is not yet setup, go to control panel. In Control Panel ,
click on Network, then add software and choose Remote Access
Service and add RAS.) The click on RAS. If you haven't
already added your ISP's info to your dialing directory, do
so now.
b. After your dialing info is done, click on the providers's
name if it is not already highlighted. The click on edit. If
there is a button showing Advanced, click on it. You will see
buttons now on the bottom of the window. Click on Security.
The only circle with a dot in it should be "Accept any
authentication including clear text". Now click on the down
arrow on the "After dialing" Add the file named in the
brackets we saved in switch.inf, by highlighting it. Click on
OK.
c. Now click on the Network button. SLIP or PPP can be set up
here. As this text is covering a PPP setup, I will continue
here. PPP should be darkened in the circle. TCP/IP should
have an "X" in it. To clarify many questions, NetBEUI DOES
NOT NEED TO BE USED! I found it to cause problems and I
removed it. IF, you plan on dialing into your office network
via at NetBEUI file access, then obviously you will need this
service. (Enough........)
Request LCP extensions (RFC 1570) should have an "X" in the
adjacent box also. (At least on my sys..) Now click OK.
Re-Boot if you haven't already.
4. You are Ready
a. Open the Remote Access Service folder. Click on the RAS icon
and open it. Then click on "Launch Monitor at Startup". I
also have the modem silenced from these options. Now double
click on your ISP's name in the dialing directory and RAS
should dial and your switch.inf file info will be used.
b. Your monitor should have the CD block lighted with green. If
you experienced any errors, the ERR would have been red.
Typically errors occur from script info. Re-check all
segments of updating your switch.inf editing. Then try it
again. If this fails, START OVER completely and double-check
everything. If after you have done this twice, try again at
an early time in the day ;-)
c. Now test your connection by opening up MSDOS or 4DOSNT or
something. type "ping" and press enter. You should see :
D:\>ping
Usage: ping [-t] [-a] [-n count] [-l size] [-f] [-i TTL] [-v TOS]
[-r count] [-s count] [[-j host-list] | [-k host-list]]
[-w timeout] destination-list
Options:
-t Ping the specifed host until interrupted.
-a Resolve addresses to hostnames.
-n count Number of echo requests to send.
-l size Send buffer size.
-f Set Don't Fragment flag in packet.
-i TTL Time To Live.
-v TOS Type Of Service.
-r count Record route for count hops.
-s count Timestamp for count hops.
-j host-list Loose source route along host-list.
-k host-list Strict source route along host-list.
-w timeout Timeout in milliseconds to wait for each reply.
Now you can type ping your provider.net. (Mine would be "ping
alaska.net".) Or type "ping 204.17.139.1" , which does the
same function. My response is :
D:\>ping alaska.net
Pinging alaska.net [204.17.139.1] with 32 bytes of data:
Reply from 204.17.139.1: bytes=32 time=170ms TTL=254
Reply from 204.17.139.1: bytes=32 time=170ms TTL=254
Reply from 204.17.139.1: bytes=32 time=160ms TTL=254
Reply from 204.17.139.1: bytes=32 time=170ms TTL=254
Your response should be similiar. If you receive this type of
response..you are connected OK. Proceed with updating
WS_FTP32, NetScape32, and all your other needed programs.
Hoping to hear this has helped, how about sending me a note
and saying Hi !
"I assume that no person shall hold me liable of anything that I have
not communicated" Or Only the experienced walk with a
limp...............
Technical Support: support@smart.net
Billing: billing@smart.net
Webmaster: webmaster@smart.net