
From: gordonf@vcn.bc.ca (Gordon Fecyk)
Newsgroups: comp.os.ms-windows.win95.misc,comp.os.ms-windows.setup.win95,comp.os.ms-windows.networking.win95,comp.os.ms-windows.apps.compatibility.win95,comp.answers,news.answers
Subject: Windows 95 Frequently Asked Questions and Answers Part 8 of 14
Followup-To: comp.os.ms-windows.win95.misc,comp.os.ms-windows.setup.win95,comp.os.ms-windows.networking.win95,comp.os.ms-windows.apps.compatibility.win95
Date: 14 May 1996 01:45:14 GMT
Organization: Vancouver Regional FreeNet
Lines: 546
Approved: news-answers-request@MIT.EDU
Message-ID: <4n8oja$4r@milo.vcn.bc.ca>
NNTP-Posting-Host: opus.vcn.bc.ca
Summary: These postings list many questions asked in said newsgroups,
         and answers them as best as I can.  I make references to other
         Web sites and FAQs when appropriate.  Visit the WWW home of
         this FAQ (http://www.intouch.bc.ca/win95) for the appropriate
         links.  This section is the 8th one: Internet/Dial-up networking
X-Newsreader: TIN [version 1.2 PL2]
Xref: news.eunet.fi comp.os.ms-windows.win95.misc:144558 comp.os.ms-windows.setup.win95:12807 comp.os.ms-windows.networking.win95:8828 comp.os.ms-windows.apps.compatibility.win95:4351 comp.answers:17465 news.answers:61861

Archive-name: windows/win95/faq/part08
Last-Modified: 1996/04/29
URL: http://www.intouch.bc.ca/win95/faq8.htm

8) How do I connect to The Internet? 
And other dial-up networking questions 

TCP/IP under Windows 95 in a nutshell 
How do I set up TCP/IP through a network card? 
How do I set up TCP/IP through a modem? (Follow exactly to 
the letter, or else!) 
How come I have to dis-connect from my NetWare server when 
just dialing to The Internet? 
How do I run my Winsock program? 
Using Trumpet (tm) and other TCP/IP stacks (Just don't!) 
How do I get dial up networking to work with other stuff besides 
The Internet? 
How do I get auto-dial to work? 
How do I set up auto-disconnect? 
How do I DISABLE auto-disconnect? 
My provider only has SLIP. Can I use that? (yes.) 
Dial-up networking won't save my password! How do I fix it? 
How can I track my time and costs on my connections? 
How do I use dial-up networking on a null modem cable? 
How do I write a dial-up script? 
How do I set up a dial-up server? 
Top five reasons to use Win95 as a dial-up server 
Top ten Dial-up Server mis-conceptions 
Top ten Internet/Dial-up mistakes 
----------------------------------------------------------------------

TCP/IP under Windows 95 (Next five section fer Experten 
only; is nicht fer gerverken by das dumbkoffen) 

So you don't trust the Internet Setup Wizard, eh? OK, here's TCP/IP 
in a nutshell. 

Transmission Control Protocol/Internet Protocol (TCP/IP) comes 
with Win95 as an NDIS 3.1 protocol. So, aside from connecting to 
The Internet, you can use any other Win95 clients or services over 
TCP/IP as well, or at least, those that don't depend on a particular 
protocol. Now that's pretty cool, but we want to connect to The 
Internet, right? 

Win95's network setup also copies the Windows Sockets libraries, 
based on Berkeley University's UNIX Sockets interface. Winsock 
works over any protocol really, which is why Win95 Setup must 
replace any other WINSOCK.DLL with its own, but for The Internet 
we're primarily concerned with Winsock over TCP/IP. All Windows 
Internet apps use the Winsock interface, in one form or another. 
----------------------------------------------------------------------

How do I set up TCP/IP through a network card? 

If you don't already have a network card installed, install it and load 
its Win95 driver. Then add TCP/IP protocol. TCP/IP has six 
property sheets, some of which affect all of TCP/IP, and others only 
affect the net card they're bound to: 

IP address: Either have it select an IP address automatically, or 
give it an IP address and subnet mask directly. To perform 
automatic IP selection you need a BOOTP server or DHCP 
server operating within your local network. This is unique for each 
card using TCP/IP. NOTE: While I haven't seen a BOOTP 
server assign addresses to Win95 clients yet, it is theoretically 
possible. BOOTP only assigns IP addresses and Subnet masks; 
you need a DHCP server to auto-configure other Win95 
TCP/IP settings. 
WINS configuration: To use Client for MS networks or any 
other NetBIOS apps over TCP/IP, you should have a Windows 
Internet Name Service (WINS) server accessible to you. Feed its 
IP address here, or if you have a DHCP server you can let it fetch 
WINS information from there. For regular Internet connections, 
select "Disable WINS Resolution". These settings affect all net 
cards using TCP/IP. 
Gateway: To get to the rest of the Net, feed your router's IP 
address here. I don't believe Win95 will grab Gateway info from a 
DHCP server so ask your administrator for this value. This is 
unique for each card using TCP/IP. 
DNS Config: This tab not only enables Domain Name Service for 
Winsock apps, it also enables NetBIOS name resolution over 
DNS. Select "Enable DNS" and feed it up to three addresses of 
DNS servers. If you have a local DNS and an Internet provider's 
DNS, you can enter both of them here. Yes, it does work. Also, if 
you wish, enter the domains you wish to enable NetBIOS naming 
for. For example, if you want to look for a server named \\JOE in 
the domain my-domain.com, insert my-domain.com into the 
domain search order list. For regular Internet access you can leave 
the search order fields blank. This tab affects all net cards using 
TCP/IP. NOTE: Supposedly, if you provide DNS info on a 
DHCP server and you leave DNS disabled here, Win95 will 
grab DNS info from the DHCP server. 
Advanced: This is a useless tab, proably inserted to provide 
controls like TTL and hop count limits and such, but Microsoft 
chose to omit it. Too bad, because enough people complain about 
not being able to control them. Here are the settings I'm talking 
about. 
Bindings: Very important tab if you don't want someone on The 
Internet poking in your computer. If you have File & Print Sharing 
for MS networks installed, turn off the checkmark to that service 
in this Bindings tab. This way, FPS won't work over TCP/IP, and 
no one on The Internet can get to your computer. This is unique 
for each net card using TCP/IP. 
----------------------------------------------------------------------

How do I set up TCP/IP through a modem? (Follow exactly to 
the letter, or else!) 

Make sure you installed Dial-up Networking from Add/Remove 
Programs/Windows Setup. Then make sure you have the Dial-up 
Adapter installed in your Network setup. Then add TCP/IP. Follow 
the guidelines for net cards, except use these settings: 

IP address: Obtain IP address automatically 
WINS Resolution: Disable WINS resolution 
Gateway: leave blank unless your provider gave you a Gateway 
address, if so put it here 
DNS: Disable DNS Resolution (We insert DNS addresses later!) 
Advanced: Nothing, but turn off "Use this as default protocol". 
Bindings: Definitely turn off the FPS for MS networks binding if 
you have it. 

Then re-boot, double-click on your Dial-up Networking folder and 
make a new connection. The modem configuration may be whatever 
you like, but your Server type must have these settings: 

Server type: PPP (Win95, Win NT 3.5, Internet) (You can do 
SLIP too, contrary to popular belief) 
Log on to network: OFF (This prevents disconnects if you're 
logged into a NetWare network) 
Enable Software Compression: OFF (Unless you're dialing into 
an NT dial up server, in which case this will really speed things 
up!) 
Require Encrypted password: OFF (Again, only useful if you're 
dialing into an NT dial up server) 
Protocols supported: Only have TCP/IP turned on and the others 
OFF! 

Then in TCP/IP Settings: 

Server assigned IP address: turned on unless your provider 
handed you one, in which case feed it here. It will automatically 
use Subnet mask 255.255.255.0. 
Specify Name server addresses: Here's where you feed the DNS 
server addresses! Leave the WINS server addresses at 0.0.0.0 to 
disable WINS over the dial-up connection. 
IP header compression: Turn ON unless your provider tells you 
not to. 
Use Default Gateway: Turn ON unless your provider gave you a 
specific gateway adddress, and you put in in your TCP/IP 
properties back in Network Setup. 
Finally hit OK. 

The above settings work with 99% of all UNIX and NT dial up 
servers known to me. By hard-coding the DNS addresses here and 
specifying only TCP/IP, you prevent Win95 from sending unusual 
PPP requests to the dial up server, some of which can CRASH some 
UNIX dial-up servers. The Internet Setup Wizard automatically 
prepares a dial-up connection with all the proper switches set, except 
it turns on "Enable Software Compression", which you can turn off if 
you have troubles connecting. The next thing to turn off would be 
"Enable IP header compression" if you still have troubles connecting. 

If your provider requires a special login procedure, bring up 
properties for the dial up connection again, select "Configure...", and 
in the Options tab, turn on "Bring up terminal window after dialing". 
This will let you manually login to the dial up server. When you 
connect, log in manually, and activate PPP, however you're supposed 
to do it, then hit "Continue" or press F7, which continues the PPP 
negotiation. Learn your provider's login procedure, then read on to 
learn how to write an automated dial up script. 
----------------------------------------------------------------------

How come I have to dis-connect from my NetWare server when 
just dialing to The Internet? 

Win95's dial up networking uses a generic (OK, so Shiva wrote it, 
whatever) Point-to-Point Protocol (PPP) that works with pretty much 
any network transport. In particular, Microsoft directly supports 
NetBEUI, IPX, and TCP/IP over PPP. 

The one complication that rises over this, is when you try to dial out to 
The Internet while logged into a NetWare network, it will warn you 
that it must disconnect from the NetWare server, since the Client for 
NetWare can only log in to one NetWare server at a time. To avoid 
this, have "Log on to network" turned off in your dial up connection's 
Server Type. 

Rich Graves claims this is because of Microsoft's PPP "Extensions", 
but I think it's just because Client for NetWare can't log in to more 
than one server. LOGIN and ATTACH are two different actions; you 
can ATTACH to a NetWare server remotely after you logged in to a 
LAN NetWare server. Client for MS networks does not have this 
limitation. 
----------------------------------------------------------------------

How do I run my Winsock program? 

Make your connection, however you do it, then run your apps. 
Simple. 

Win95's WINSOCK.DLL and WSOCK32.DLL include a 
"standard" Windows Sockets API that works with ANY properly 
written Winsock program. All of the Public Domain, Freeware, 
Shareware, and a surprisingly large number of Commercial apps, run 
with these libraries. 

If you installed Internet Explorer, you'll find that your dial-up 
connection requester will pop up when you run a Winsock app, if you 
aren't already connected. This is pretty nifty, and you can control this 
auto-dialer from the new Internet control panel that shows up. Of 
course, Auto-dial is pretty useless if you use TCP/IP over a network 
card. 

Be VERY VERY CAREFUL if you install any one-shot packages 
which include their own dialers. These will often replace the OS 
standard WINSOCK.DLL with their own to accomodate their dialer. 
When you shop for such programs, make sure they have an option to 
use any existing TCP/IP and dialer you already installed. One such 
evil program is Netscape Navigator Personal Edition. Make sure you 
tell this program to "Use existing Winsock and dialer". 

A really good tip, regardless of whose TCP/IP stack you use, is to 
write-protect WINSOCK.DLL and WSOCK32.DLL. Bring up a 
DOS prompt, type 

CD \
DIR WINSOCK.DLL /S

and note what directory the file is in. You'll probably find multiple 
WINSOCK.DLL files if you installed any "All in one" apps. Change 
to that directory then type 

ATTRIB +R WINSOCK.DLL

Do this for WSOCK32.DLL as well. 
----------------------------------------------------------------------

Using Trumpet (tm) and other TCP/IP stacks (Just don't!) 

Yes they do work, as long as you don't have any Win95 networking 
components installed. Problem is, when you make a networking 
change, Setup might decide to re-copy the files over, and when it 
does it will happily over-write WINSOCK.DLL. Remember: 
Winsock was designed for other protocols too, not just TCP/IP, and 
it's a standard OS component now! So, either use Win95's 
networking and Win95's dialer, or use no Win95 networking and 
someone else's dialer. 

And yes, you can make 32-bit Winsock apps work with older stacks. 
There's a _WSOCK32 "thunk"_ available that works with an existing 
Win 3.1 dialer and their own WINSOCK.DLL. 

You could also check out Trumpet's own 32-bit TCPMAN or TGV's 
replacement TCP/IP stack. 
----------------------------------------------------------------------

How do I get dial-up networking to work with other stuff 
besides The Internet? Like a NetWare server? 

The one really cool feature that allowed Win95 to devastate OS/2 
Warp Connect; general dial-up networking. MS included a 
Shiva-written PPP/RAS dial-up stack that works with pretty much 
any transport protocol, though there's only direct support for 
NetBEUI, IPX, and TCP/IP. Clients can bind to these protocols to 
work over a dial-up connection. 

Install Dial-up Networking in Add/Remove Programs/Windows 
Setup. Then re-boot. A Dial-up Networking folder appears in "My 
Computer". You will also find a Dial-up Adapter in your Network 
control panel; you will have to add protocols for this adapter as 
needed. 

If you're connecting to a Win95, Windows NT, or WFWG dial-up 
server, you can make a connection right from the "Make new 
connection" wizard. This will also work if you're connecting to a 
NetWare network through a Win95 or Windows NT dial-up server. 
If you log into an NT domain this way, you need "Log on to network" 
turned on, otherwise you can leave it turned off to save some time. 
Old WFWG or NT 3.1 dial-up servers only work with the RAS 
server type; NT 3.5 and Win95 servers work with the PPP server 
type. 

If you're connecting to a NetWare network using NetWare Connect 
(NRN), Install IPX/SPX Protocol, bring up properties for your 
connection, and change the Server Type to NRN: NetWare Connect. 
This disables all other protocols but IPX over that connection. You 
will need "Log on to network" turned on; this will have Win95 search 
for a NetWare server (Or the preferred server) and bring up the 
NetWare log in requester. 

NOTE: You can also use PPP to connect to a NetWare server 
remotely, if your NetWare network has a Windows NT or Win95 
dial-up server running. This is a less expensive option than Novell's 
NetWare Connect software. 
----------------------------------------------------------------------

How do I set up auto-dial when I run my Winsock program? 

Auto-dial only works if you installed Microsoft Plus! or Internet 
Explorer. Once installed, your computer will bring up the dial-up 
requester when any program accesses WSOCK32.DLL. Pretty cool. 
For some reason this won't work with 16-bit Winsock programs 
though. Dumb. 

There's a new Internet control panel when you install either of those, 
and you can control auto-dial and auto-disconnect from there. 
----------------------------------------------------------------------

How do I set up auto-disconnect? 

As per auto-dial; install MS Plus! or Internet Explorer, and check out 
the Internet control panel. You then tell it to dis-connect after some 
amount of in-activity (20 minutes by default). 
----------------------------------------------------------------------

How do I DISABLE auto-disconnect? 

Auto-disconnect does have one dumb bug; unless you're performing 
active surfing in Internet Explorer (Other apps it just ignores), the 
dis-connect timer will activate. This includes when you're downloading 
large files via FTP, and not doing any other mouse clicking. Pretty 
dumb. 

Turn it off in the new Internet control panel, that shows up when you 
install Internet Explorer, or MS Plus. 
----------------------------------------------------------------------

My Internet provider only has SLIP. Can I use that? (yes.) 

Install DSCRPT.EXE or install MS Plus. The dial-up scripter includes 
a SLIP server type for dial-up networking. When you select SLIP: 
Unix Connection, or CSLIP: Unix Connection, from the server type 
options, you will only be able to use TCP/IP. 

There are additional scritping commands for using SLIP; be sure to 
check out dial-up scripting help for the details. You may need to use 
the script to obtain an IP address. 
----------------------------------------------------------------------

Why can't the dial up connection save my password? 

Password caching only happens if you install a Win95 network client, 
or enable User Profiles on a stand alone computer. By default, the 
Internet Setup Wizard only installs TCP/IP protocol and the dial-up 
networking components, which is all you really need. 

However, MS Exchange will do login password caching independant 
of the dial-up settings. In the Internet Mail properties, select 
"Connection" and "Login As...", then type the username and 
password. If you leave these blank, it will use the defaults for the 
dial-up connection. Other utilities like RoboDUN and DUNCE will 
not only save your password, but instantly dial-up without asking you 
for an "OK". 
----------------------------------------------------------------------

How can I track time and costs for my dial-up connection? 

Many providers have different costing schemes, so MS didn't bother. 
However, check out RAS Plus 95 which monitors dial-up connection 
times, and lets you define your billing scheme. 
----------------------------------------------------------------------

How can I get dial-up networking to work with a null modem 
cable? 

MS didn't include a null modem driver for the Telephony Interface 
(TAPI). However, check out this bogus MODEM.INF file, which 
serves the purpose. One installed, you can treat the null modem like 
any other modem in Win95. 
----------------------------------------------------------------------

How do I write a dial-up script? 

Download DSCRPT.EXE from Microsoft's Win95 site, or grab it off 
your CD-ROM in ADMIN\APPTOOLS\DSCRIPT, and install it 
from Add/Remove Programs/Windows Setup/Have Disk. Or install 
Microsoft Plus! This adds a Dial-up scripting tool to your Accessories 
group. If you re-install Win95, you will have to re-install this tool; 
Setup will over-write the Registry keys that hook DSCRPT into 
dial-up networking. 

NOTE: This will also add SLIP and CSLIP to the list of dial up server 
choices! However, you can only use TCP/IP over SLIP and no other 
protocol. 

Run the tool to list all of your dial up connections. Select your 
connection, then type a path/filename to a script. The script doesn't 
have to exist yet. Then hit "Edit", and you'll see Notepad. It'll ask you 
if you want to create a new file; do so. Here's a sample script: 

proc main
       waitfor "Username:"
       transmit $USERID
       transmit "<cr>"
       waitfor "Password:"
       transmit $PASSWORD
       transmit "<cr>"
       delay 1
       transmit "ppp default<cr>"
       delay 1
endproc

The $USERID and $PASSWORD come from whatever you fed the 
dial-up connection. I feed "ppp default" to the provider because a 
successful log in only gives me a Unix prompt. "ppp default" runs a 
program at the dial-up server which starts a PPP session, but it isn't 
necessary for all dial-up servers. I even know of one public dial-up 
server in Taiwan that doesn't even ask for a username and password! 
This is why you should perform one manual login ("Bring up terminal 
window after dialing") and learn how your provider prompts you for 
this info, and then write the script based on that. 

Microsoft Plus! includes an improved scripter which allows some 
branching and IF/THEN programming, but it isn't necessary for all 
providers. The above example works with both Plus! scripting and the 
basic scripter on MS's web site. 

And finally, save this script and hit "Apply" to attach the script to the 
dial-up connection. You can turn on "Step through script" to test and 
debug the script, then turn it off when you know it works. Hit "Apply" 
to save any changes you make to a script attachment or settings. 
----------------------------------------------------------------------

How do I set up a dial-up server? 

Install MS Plus. If you chose the Dial-up networking server, it will 
add a new Dial-up server... menu to the Dial-up networking window. 
The Win95 dial-up server is really a NetBIOS router, meaning it 
doesn't actually perform WAN routing of a low level protocol (though 
they did hack IPX routing in there for NetWare clients). 

In Dial-up Networking, you have a new menu: Connections/Dial-Up 
Server. You can choose ONE modem to receive calls on (Not more 
than one, sorry), and you can pick what kind of dial up server it is 
(either PPP, WFWG RAS, or Default, which allows for both). You 
can also enter a dial up password, or pick users from a user list if you 
have User Level security enabled. 

Now I wrote above that it's a NetBIOS router. That means it's 
designed to route MS Network style traffic to a network. Normally, a 
dial-up client will have Client for MS networks and NetBEUI installed 
(or for WFWG clients, they just use the Remote Access software 
included), because NetBEUI's the fastest NetBIOS compatible 
protocol for slow links. NetBEUI isn't route-able, but that doesn't 
matter; the network itself could use IPX or TCP/IP instead, as long as 
it's an MS Windows style network. 

...for NetWare dial-in? 

NetWare dial-in works too, because Microsoft hacked a simple IPX 
router in there. To do NetWare dial-up access, make sure you install 
IPX protocol and bind it to the Dial-up Adapter in Network Control 
Panel. The clients can be Win95 or Windows NT clients, but they 
need to have IPX protocol and Client for NetWare installed. When 
the user dials in, a NetWare login prompt will come up, login scripts 
will execute, and connections will appear. 

WARNING: IPX over PPP is quite slow! Some tips for the client, to 
speed up performance: 

Allow only IPX protocol for dial-out to the dial-up server (turn 
NetBEUI and TCP/IP OFF in Server Type) 
Keep local copies of MAP.EXE and CAPTURE.EXE on the 
remote computer, in the WINDOWS\COMMAND directory 
Turn Software Compression ON 
Pick a frame type in IPX properties (Don't use Auto-Detect) 
Don't run NetBIOS apps over the dial-up connection through IPX 
----------------------------------------------------------------------

Top five reasons to use a Win95 machine as a dial-up server 

5) Cheap NetWare dial-in access (A LOT cheaper than NetWare 
Connect!) 

4) Cheap Windows Network dial-in access 

3) Effortless (almost) connection to your network from home 

2) Works with non-Win95 MS Network clients (like an Amiga using 
SAMBA!) 

1) User-Level security works here (Not like NT RAS Server) 
----------------------------------------------------------------------

Top ten mis-conceptions about Win95 dial-up servers 

10) Fast connection speeds (NOT!) 

9) It routes TCP/IP (This is a Resource Kit error.) 

8) It does MS-Mail Remote (Sorry, it doesn't) 

7) It routes NetBEUI (It's a NetBIOS router; NetBEUI isn't 
route-able) 

6) You need NetBEUI on the net card to route (It's a NetBIOS 
router; it doesn't matter) 

5) You need NetBEUI on the Dial-up Adapter to use it (It's faster, 
but it doesn't matter) 

4) It won't work with non-Win95 dial-up clients (Bull... I've used my 
Amiga to dial in! Couldn't transfer any files though... heh heh) 

3) It doesn't work with null modem cables (check out this bogus 
modem.inf file if you want to use a null modem) 

2) It's a security risk to my network! (Geez, you can disable the 
dial-up server in system policies for the default computer, then enable 
it for the computers you want it to work on.) 

1) 
----------------------------------------------------------------------

Top ten Internet/dial-up mistakes 

10) Using a Win 3.1 TCP/IP protocol 

9) Installing Netscape Navigator Personal Edition and using its dialer 
instead of Win95's 

8) Buying lots of Winsock software before checking out 
www.windows95.com 

7) Using default dial-up connection settings and crashing your 
provider's server 

6) Telling your provider you have Win95 (Many of them cringe upon 
hearing that) 

5) Buying Microsoft Plus! JUST for dial up scripting, before trying the 
free DSCRPT tool 

4) Installing a provider's setup disk for Win 3.1 (dumb mistake; many 
providers do that!) 

3) Leaving "File & Print Sharing for MS networks" turned on over 
TCP/IP 

2) Not getting connection and server information from your provider 

1) Not reading the Modem section of this FAQ page 
----------------------------------------------------------------------

[Back to Table of Contents]

