|
NOTE: If you already have DUN installed, or have W98
with DUN built in, and just need help creating a dialer
"Connectoid", go HERE now. If not, read on.
W95 DUN does the following things. It
communicates with your modem, causing it to dial your
Internet Provider's POP (Point of Presence) node or
phone number, and then establishes a tcp/ip PPP (Point
to Point) link with you and the Internet. There are
two basic components to the DUN. The dialer software
and the network protocols; all together they represent
a STACK or pile of things needed to communicate.
Your modem must be installed first. Most
modems today are plug and play (meaning they contain a
Legacy bios chip which interfaces with the PC's bios).
This makes installation rather easy. Most of these
modems are configured by an INF file that controls many
important features of the modem, such as its ability to
correctly report the DCC or "Connect" speed rather than
the DCE or port "locked" speed. Most all modem
irregularities can be corrected by making sure you have
the latest driver (modem.INF) file installed for your
model.
All recent versions of Windows 95 have
DUN pre installed such a version B or OSR1 or OSR2. If
you are running an older version, you will need to
obtain several upgrade files as well as have your
original W95 installation disks handy.
To see
which DUN version you have installed (if any), go to
Windows/System and see if you have a copy of
RASAPI32.DLL. If so, right click on it, then select
"Properties". If version "4.10.1903" does not display
on the "version" tab, you DO NOT have the most recent
release of MS's Dial Up Networking (DUN 1.3).
If you still are not sure what DUN you have installed,
download this
UTILITY.
Double click to run. The window
that pops up will inform you what dun you are running.
The files you will need for the upgrade are
MSDUN13.EXE and W95WS22U.EXE Version 1.3 is the most
recent release of the DUN. The Winsock (that supplies
the tcp/ip protocol) is up to release 2.2
Get
the winsock HERE
Get the DUN13 HERE
Get any of Microsoft's free upgrades, patches etc HERE
Both upgrades come in self
installing archives. It is only necessary to double
click on the appropriate file, from within Windows
Explorer, to start the upgrade. Or, you can go to the
Windows Start button, then Run, then Browse until you
locate the upgrade file. NOTE:
Install the DUN first, THEN the Winsock. Ok, we
will now assume that the DUN and Winsock was there
originally or is now successfully installed. So it is
now time to test the modem and then "setup" the DUN to
dial your provider and establish a tcp/ip PPP
connection.
A great way to test the modem is
to install a dumb terminal program. I recommend one
called Hyper Terminal by Hillgrave.
Get
HyperTerm HERE
With DUN installed, you
can create a test connectoid that will perform like a
dumb terminal too. More on that later.
To
successfully operate, the modem and terminal software
must be correctly configured. In most cases, the modem
will be set by "default" to COM1 at IRQ4 (the comm port
and interrupt that services it). The software must be
set accordingly. In addition, the terminal software
sets the DCE baud rate (the speed that the modem will
communicate with the computers UART chip - the
universal asynchronous receiver transmitter chip).
Finally, the terminal software can also initialize the
modem with a set of "AT" instructions called a
"string". Typically "AT&F" sets all modem
registers to their factory defaults. In some
instances, data bits, parity and stop bits can be set.
8N1 is standard.
Your ISP should supply the
following information:
Your user ID (which
may require a prefix like ELN/ or CIS)
Your
password
The domain address of their SMTP
server (so your e-mail client can "send" e-
mail.(example: mail.earthlink.net)
The domain
address of their POP3 server (so your e-mail client can
"receive" e-mail. (sometimes the same as SMTP domain)
The domain name of their NNTP Newsgroup
server. Example: mail.earthlink.net
The IP
(dot quad) of their primary and secondary DNS servers.
(the servers that resolve verbose URL's to IP's)
READ EVERYTHING FROM HERE DOWN BEFORE
PROCEEDING. ALSO PRINT A HARD COPY FOR QUICK AND EASY
REFERENCE.
After the DUN and winsock are
installed, you can go to the "My Computer" Icon in the
top left corner of your w95 desktop. Double click.
This will open a window where you should find the Dial
Up Networking folder. Double click on it. You should
then see another window open with a "Make New
Connection" Icon. Double click on that.
This
will start the DUN Wizard or setup utility.
You will need to give a name to the dial icon that will
be created. The dialog box will show "my connection"
by default. If your modem was installed correctly, its
name/type should appear in another dialog box. If
another, older modem shows, use the down diamond on the
rt side of the pick box to select the correct modem.
Proceed with the Next button. Enter your ISP's phone
number in the phone dialog box.
NOTE: If you
are going to be using a line with call waiting, its
best to also enter a temporary one call disable code
before the phone number. *70, is the disable code.
Therefore the entire string should look like "*70,525-
1120". Proceed to Finish. This creates the dial Icon.
If this was a first creation, you might be asked for
additional technical data. If not, you will have to
manually enter this information. Right click on the
newly created Icon and choose "Properties".
Pick the "Server Types" tab.
The ONLY two
check marks should be:
Enable Software
compression AND Tcp/Ip
Now click on the
Tcp/Ip Setting Button.
Bullet the "Server
assigned IP" AND "Specify the name server ip"
Now enter the primary and secondary DNS server IP
numbers your ISP provided.
Hot TIP: If you
later find you get the message "Unable to resolve"
rather often from your Web Browser, this is an
indication the ISP's DNS server (typically an orphan
child when it comes to maintenance) is un reliable. If
this turns out to be the case, there is no requirement
that you use your ISP's DNS servers. I have found from
years of experience that the major players have the
best and most reliable DNS's servers. I recommend
AT&T's at 204.127.129.1 for a primary. Use your
ISP's primary DNS as the secondary.
Make sure
the following two items are check marked:
"Use
IP Header Compression" AND "Use default Gateway...."
IF setup did not previously ask for your
userid and password you will have to manually add
these. Go to Start/Settings/ Control Panel/Passwords
and follow instructions.
Finally, you can
create a Shortcut to your Dialer Icon on your desktop
or in any folder.
Double clicking on your
Dialer Icon should dial your ISP, make the connection
and log you on.
SPECIAL LOGIN CIRCUMSTANCES:
Under normal circumstances the DUN software
will detect when the ISP's logon server asks for the
only two "normal" pieces of information to establish
your identity and connection, your user id and your
password; and DUN sends each at the appropriate time.
This is called PAP or Password Authentication Protocol
which allows logging onto the Internet without a
connect script.
But, what if your provider's
logon procedure requirs more info?
The way to
handle this is with a logon script. A logon script is
an ordinary text file that uses the extension .scp and
contains special text lines to pass whatever info is
necessary. As simple example follows:
proc
main
waitfor "login:"
transmit
"myname^M"
waitfor "password:"
transmit "mypass^M"
endproc
This working
sample script is fairly self explanatory. All that may
be needed to mention now is the purpose of the caret
followed by the capitol M (^M). This tells DUN to
append a carriage return or ascii 13 to the string
(the equivalent of hitting the Enter key).
To
load your script (and or create one too), right click
the Dial Icon, click Properties, then the Script Tab.
From here you can either write your script from
scratch, edit an existing script or enter the
drive/path/ name.scp to one previously created.
NOTE: using a script, preempts the DUN from
passing your userid and password in the conventional
manner, so it must be done in the script itself when
required.
Here is an example of a more
complicated script used to logon to compuserves old X.1
network:
;use a leading semicolon to make
notes
proc main
set port databits
7
set port parity even
transmit
"^M"
waitfor "name:"
transmit
"SPRY01^M"
waitfor "UIC:"
transmit $USERID, raw
waitfor
"password:"
transmit $PASSWORD, raw
delay 1
set port databits 8
set port parity none
endproc
Of
noteworthy mention is the commands that can be used to
configure the modem itself; such as changing data bits
or parity. Also notice the variables $USERID and
$PASSWORD that pick up your info from Windows and pass
it raw to the provider. This in theory eliminates
someone from browsing your PC folders and obtaining
your secure user information.
For a complete
list of script commands, syntax and examples of code,
written by Microsoft, order "MSDUNSCP" from my
listserv.
Here is a site that may offer more
insights on
SCRIPTING techniques.
Finally, here is a
web site with lots of GUI for those who need "pictures"
along with text explanations for setting up MS's DUN;
go
HERE.
Here is a neat method to start the
DUN from either the Start/Run command line or
automatically vi a shortcut.
Type
"c:\windows\rundll.exe rnaui.dll,RnaDial "connectoid"
in the RUN dialog box or place the statement into the
command line of a newly created desktop shortcut.
(connectoid is Microsoft jargon for the name
of your dial-up networking target that you have already
created, e.g., msn, aol, PacBell
Example:
"c:\windows\rundll.exe rnaui.dll,RnaDial PacBell"
My Dialer comes up as soon as W95 loads. How
can I stop this?
Check the following key in
your registry and make sure yours agrees with this one.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\OLE
EnableDCOM="Y"
EnableRemoteConnect="N"
My DUN is not saving passwords. What is the fix?
Typically this is due to not having "Client
for Microsoft Networks installed. Go to Start/Settings/
ControlPanel/Networking and enable it.
There
was also a problem with an early version of W95 OSR1
relative to saving passwords. There is an MS patch for
this problem that should fix it.
Download the
patch HERE
Sometimes your DUN stops Auto
dialing when launching your browser, even though you
didn't change any of the settings. There are many
reports of this happening after installing Quicken
98/99 and other third party products.
You have
to edit the registry to correct this problem (Windows
95 with Internet Explorer 4 or 4.01): Start the
Registry Editor
Go to:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Wi
nsock\Autodial
You should find these values
there:
Name
Value
AutodialDllName32
wininet.dll
AutodialFcnName32
InternetAutodialCallback
And also:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Wi
nsock\Parameters
Where you should find:
Name MSTCP
Value ""
Correct
all as required.
|
