Search the FAQ Archives

3 - A - B - C - D - E - F - G - H - I - J - K - L - M
N - O - P - Q - R - S - T - U - V - W - X - Y - Z
faqs.org - Internet FAQ Archives

Win95 FAQ Part 8 of 14: Dial-up Networking

( Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Part8 - Part9 - Part10 - Part11 - Part12 - Part13 - Part14 - MultiPage )
[ Usenet FAQs | Web FAQs | Documents | RFC Index | Neighborhoods ]
Archive-name: windows/win95/faq/part08
Last-Modified: 1998/11/08
Posting-Frequency: Every two months
URL: http://www.orca.bc.ca/win95/faq8.htm

See reader questions & answers on this topic! - Help others by sharing your knowledge
Subject: 8. How do I connect to The Internet? And other dial-up networking
questions

     * 8.1. TCP/IP under Windows 95 in a nutshell
          + 8.1.1. How do I set up TCP/IP through a network card?
          + 8.1.2. How do I set up TCP/IP through a modem? (Follow
            exactly to the letter, or else!)
               o 8.1.2.1. Should I get the ISDN/DUN 1.3 update if I
                 don't have ISDN?
               o 8.1.2.2. Can I use two modems at the same time to
                 speed up my connection?
               o 8.1.2.3. How come TCP/IP routing doesn't work if I
                 have a net card AND dial-up connection?
          + 8.1.3. How can I share one dial-up connection over my
            network?
     * 8.2. How come I have to dis-connect from my NetWare server when
       just dialing to The Internet?
     * 8.3. How do I run my Winsock program?
     * 8.4. Using Trumpet (tm) and other TCP/IP stacks (Just don't!)
          + 8.4.1. WARNING: Netscape 32 Personal Edition's Setup
            Wizard screws up TCP/IP
          + 8.4.2. Obtaining Winsock 2.0 for Win95
     * 8.5. How do I get dial up networking to work with other stuff
       besides The Internet?
          + 8.5.1. How do I connect two Win95 computers together with
            dial-up networking?
               o 8.5.1.1. How do I connect two Win95 computers
                 together with Direct Cable Connection?
          + 8.5.2. I'm using DUN to connect to a NetWare server and
            the IPX address for me keeps changing!
     * 8.6. How do I get auto-dial to work?
     * 8.7. How do I set up auto-disconnect?
          + 8.7.1. How do I DISABLE auto-disconnect?
     * 8.8. My provider only has SLIP. Can I use that? (yes.)
     * 8.9. Dial-up networking won't save my password! How do I fix
       it?
     * 8.10. My computer hangs in the task "RNAAPP". How can I fix
       it?
     * 8.11. How can I track my time and costs on my connections?
     * 8.12. How do I use dial-up networking on a null modem cable?
     * 8.13. How do I write a dial-up script?
          + 8.13.1. How can I send a "modem break" in a dial-up
            script?
     * 8.14. How do I set up a dial-up server?
          + 8.14.1. ...for NetWare dial-in?
          + 8.14.2. Top five reasons to use Win95 as a dial-up server
          + 8.14.3. Top ten Dial-up Server mis-conceptions 
     * 8.15. Top ten Internet/Dial-up mistakes 
       

Subject: 8.1. TCP/IP under Windows 95 (Next five section fer Experten only; ist nicht fuer gerverken bei 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. * 8.1.1. 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: Thanks to MS short-sightedness again, Win95's TCP/IP won't auto-configure from a BOOTP server. Get the BOOTP addon desceibed below. * 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, probably 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. * 4.00.950B users only: NetBIOS: If you don't use Client for MS networks over TCP/IP, you have the option of disabling NetBIOS over this protocol, which saves some bandwidth and avoids the dreaded RNAAPP bug. If you use Client for MS over any other protocol, you must disable the binding between TCP/IP and Client for MS networks before it will allow you to turn off NetBIOS over TCP/IP. perin@onyx.interactive.net spent a considerable amount of time developing a BOOTP add-on for Win95. If you want to use BOOTP instead of DHCP, install his add-in software. You can find it at http://www.interactive.net/~perin/ * 8.1.2. 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 address, and you put 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. * 8.1.2.1. Should I get the ISDN DUN 1.3 update if I don't have ISDN? Dial-up Networking 1.3 fixes a few problems in the original DUN, but I haven't run into enough of them to suggest that everyone should upgrade. Microsoft makes DUN 1.3 available at http://www.microsoft.com/windows/downloads/contents/Communication s/dun13win95/default.asp You should get DUN 1.3 if: * You use Point to Point Tunnelling Protocol (PPTP) at all * You need to connect to multiple TCP/IP networks at the same time (such as two ISPs, or an ISP and a local LAN where the LAN has a router or two) * You need to get all the TCP/IP bugfixes with minimal fuss * You want to run a dial-up server and don't have MS Plus * 8.1.2.2. Can I use two modems at the same time to speed up my connection? Depending on your ISP's policies for such things, yes you can. Get the DUN 1.3 update to install Multilink capability. To enable Multilink in DUN 1.3: * Bring up your dial-up connection's properties (right-click on the connection icon, hit "properties") * Select the Multilink tab * Hit Add to add modems and phone numbers to the list. NOTE: Your ISP may have policies against multiple connections. Phone lines are not cheap. Also note that you may be billed at twice your normal connection rate. * 8.1.2.3. How come TCP/IP routing past my router doesn't work if I have a net card AND dial-up? This is actually a classic bug in Microsoft's implementation of TCP/IP that existed since MS introduced PPP into NT Workstation 3.5. What happens is, you have one gateway (Your LAN's router) and you have a "Hop count" of 1 to the rest of your inter-network. When you establish a dial-up connection, the dial-up connection's gateway (the dial-up server) has a hop count of 1 and your LAN's gateway will have a hop count of 2, so when your machine needs to access a machine past your local subnet it'll try to reach it through the dial-up gateway instead of your LAN's gateway. (phew! How's that for an explanation?) This, of course, won't work. You can actually view this with: ROUTE PRINT from a DOS session. Try it before and after you dial up. You have three fixes you can try: 1. Don't use TCP/IP on your LAN connection. Use NetBEUI or IPX instead, and disable bindings between TCP/IP and your net card (by deleting that particular entry in the Network control panel). 2. Install the Winsock 2 update or the Dial-up Networking 1.3 update (DUN 1.3 includes Winsock 2). Winsock 2 allows for name lookups and sessions over more than one TCP/IP connection. 3. Edit the routing table after you establish the connection. Say, for example, your machine lives in a subnet of 192.1.1.0 and you need to access a machine in the 192.1.2.0 subnet while you're simultaneously connected to the Internet via a dial-up. Type this at a DOS prompt: route -f add 192.1.2.0 MASK 255.255.255.0 192.1.1.1 This example describes the target subnet (192.1.2.0), the subnet mask of the target subnet (255.255.255.0), and the router with which to access that subnet (192.1.1.1). Thanks to Mike Ziemann for actually getting this to work. Please send me corrections if this is wrong! NOTE: Win95 doesn't save routing tables between reboots. You'll need to execute this after you establish a dial-up TCP/IP connection. * 8.1.3. How can I share one dial-up connection over my network? We all heard of Wingate and how you could use an NT workstation as a dial-up router, but Wingate takes a LOT of TCP/IP knowledge, and NTWS routing requires some co-operation from your ISP, both of which are scarce. I suggest I-Way One, because it only requires ONE computer (albeit a Windows NT Workstation) running TCP/IP, and only one dial-up account. I-Way One replaces WINSOCK.DLL and WSOCK32.DLL and routes requests to these libraries to the one NT machine connected to The Internet, via NetBIOS or IPX. UPDATE 11 DEC 96: I-Way One isn't available from Workgroup Communications anymore, but I have copies. I've asked for permission from IXCHANGE (http://www.ixchange.com) to keep a copy on my server if it's legal I'll do so. This software is just far too useful to lose! In the meantime you can obtain it from ixchange.com. The only catch to using I-Way One vs Wingate is you end up replacing Win95 system components (The Winsock libraries) and it can't co-exist with any TCP/IP protocol on the client. It includes a library switcher which watchdogs the system and swaps these libraries as needed, but it makes more sense just to use I-Way One and no other version of Winsock on the machines. So, the quick instructions on using it: first set up one NTWS and make sure you can connect to your ISP using its included RAS software. Then, install the I-Way One server on it and the clients on the stations. The NTWS will dial out whenever a client needs any Winsock access, and hang up after some moment of inactivity. You don't need anything else special on the NTWS or on the clients. Another TCP/IP proxy exists from Technocratix. I have yet to try it, but you can help yourself to it at http://www.technocratix.com/webetc/ Still another TCP/IP proxy to try is Microsoft's own Proxy Server, or the "re-released" Routing and Remote Access Service (previously code-named "Steelhead"). This allows an NT server to perform dial-on-demand routing.
Subject: 8.2. How come I have to disconnect from my NetWare server when just dialing to The Internet? The worst complication that rises over Win95 dial-up networking, 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. Client32 Warning: Many people wrote me to share their grief of trying to get Client32 computers to dial-up to the Internet without having to disconnect from their NetWare servers. While turning off "Log on to network" in Server Type works great with Client for NetWare and Services for NDS, it doesn't work with Client32! I'm sure Novell is hard at work (NOT) on this problem...
Subject: 8.3. 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 accommodate 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.
Subject: 8.4. 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. It's somewhere on www.windows95.com but I forgot where. You could also check out Trumpet's own 32-bit TCPMAN or TGV's replacement TCP/IP stack. * 8.4.1. Netscape 32 Personal Edition's Setup Wizard screws up TCP/IP If you install Netscape Personal Edition for Windows 95 (whatever version) it presents you with a connection setup wizard similar to Microsoft's Internet Setup Wizard. DON'T USE IT. Known problems: * It will gladly install a second instance of TCP/IP without checking first * It skips components of Win95 dial-up networking * It goofs up your TAPI location properties, so that whenever you try to connect, Win95 presents you with "There was an error in your configuration. It has been fixed." without actually FIXING IT. You can only correct this goofup by removing and re-installing Dial-up Networking, and any instances of TCP/IP from Network Properties. You will also need to make sure you configure your modem and location properties in the Modems control panel. See the steps in section 8.1.2 above. * 8.4.2. Obtaining Winsock 2.0 for Win95 To allow for multiple TCP/IP connections or to support Winsock 2 apps, MS released Winsock 2.0 for Win95 at http://www.microsoft.com/windows/downloads/contents/Updates/W95So ckets2/default.asp. This update resolves a few nasty bugs (mostly revolving around Denial of Service attacks). This works with any net card or release of Dial-up Networking before DUN 1.3; DUN 1.3 includes Winsock 2.
Subject: 8.5. How do I get dial-up networking to work with other stuff besides The Internet? 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 provided they support NDIS 3.1 PnP (So it can unload when you disconnect, for example). 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. * 8.5.1. How do I connect two Win95 computers together with dial-up networking? You can start by reading the beginning of FAQ page 7. This covers setting up two Win95 machines so they talk to each other. The only real difference is you use the Dial-up Adapter instead of a regular net card to connect the machines together with. To add the dial-up adapter, run Add/Remove Programs/Windows Setup, double-click on Communications, and turn on Dial-up Networking. Next, install MS Plus or DUN 1.3 on the machine that will answer the phone, and include Dial-up Server in the list of components. In FPS for MS networks properties, set this machine's Browse Master setting to "Enabled" instead of "Automatic". Once you finish this, turn on the dial-up server in Dial-up networking options. Specify a password if you want. Note that, if you use other Win95 apps to send faxes or to dial-out to other locations, you can leave the dial-up server turned on! Yes you can! Finally, on the machine dialing in, set its Browse Master preferences to "Disabled". Create a connection that uses only NetBEUI (This is the fastest protocol for slow links), meaning turn IPX and TCP/IP OFF in Server Type. Then try dialing the machine with the dial-up server running. Use the username and password you specified on the server. Once you connect, you should be able to browse the other machine. * 8.5.1.1. How do I connect two Win95 computers together with Direct Cable Connection? Direct Cable Connection is basically Dial-up Networking without modems. This is why you need to install DUN at the same time as DCC. DCC lets you connect two Win95 computers together with the same kind of cables you would use for LapLink or Interlink, but once connected you treat the two systems as though you connected them through DUN (Meaning you need a common client, service, and protocol). First, install DCC from Add/Remove Programs / Windows Setup. Bring up Communications details and add DCC. If you haven't already installed Dial-up Networking it will offer to do so. After it loads the needed components, and before you restart the computer, open the Network control panel and install the same components you would use to hook two Win95 machines together. These should be: * Client for MS Networks * Dial-up Adapter * NetBEUI * File & Print Sharing for MS Networks If you have other components, like TCP/IP, they should coexist nicely. Now restart the computer. Do the same thing to the other machine. Now, connect the two machines together using a Null Modem Cable (if you use a serial port) or a LapLink cable (if you use a printer port). One sample pinout for a parallel cable lives at http://oacosf.na.astro.it/rossi/hwb/ca_InterLink.html. The big advantage of parallel over serial null modem cables is you can transmit information four bits at a time instead of one, and it's supposedly four times as fast (115 200 bps * 4 = 460 800 bps, just under half the speed of Ethernet). Establish the connection by launching DCC (Start / Programs / Accessories / Drect Cable Connection) and telling each machine wether it's the host or the client. Start the host first, then the client. Once done, the client will bring up any network shares that the host has. Of course you should make some network shares on the host before connecting. You can use any devices available on the host, including printers (provided you have another printer port for the printer, that is), just like you could if these machines used a network cable. One side effect of using DCC is you will see some new "modem" devices in Device Manager (Parallel cable on LPT1 for example). If you remove these, DCC will re-create them when you launch it again. NOTE: Supposedly, you can use other protocols besides NetBEUI over DCC. While IPX games might be possible over DCC, I haven't tried, and I'm suspicious of the speed of IPX over even a parallel cable. It is also very unlikely that IPX routing would work over DCC as well. I would like feedback on DCC experiments and results. * 8.5.2. I'm using DUN to connect to a NetWare server and my IPX address keeps changing! The Dial-up Adapter generates a "fake" MAC address (a 48-bit number representing an Ethernet address) so that protocols designed for Ethernet will work on it, such as IPX. It will generate a random number for the MAC address each time you dial in. This happens REGARDLESS of what protocol you dial in with. IPX addresses look like this: NNNN-AAAAAAAA where "NNNN" is a Network Number and "AAAAAAAA" is the adapter's MAC address. Typically, a dial-up server (like NT RAS) can assign a network number for this two-station "network", but the MAC address comes from the client. It's up to the dial-up server to route to this new network number. However, programs that depend on the MAC address being fixed (such as remote backup agents) won't work. I haven't found a practical reason to use a fixed address on a dial-up line, and as such I don't have a solution.
Subject: 8.6. How do I set up auto-dial when I run my Winsock program? To set up auto-dial, install 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. There's a new Internet control panel when you install either of those, and you can control auto-dial and auto-disconnect from there.
Subject: 8.7. 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 disconnect after some amount of in-activity (20 minutes by default). * 8.7.1. 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 disconnect 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.
Subject: 8.8. My Internet provider only has SLIP. Can I use that? (yes.) Install DUN 1.3 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 scripting 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. 4.00.950B users have a better scripting interface which is part of the dial-up connection's properties.
Subject: 8.9. 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 independent 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".
Subject: 8.10. Why does my computer hang in task "RNAAPP" when I dial out to The Internet? Before I rip into this speech, jmckone@excalibur-group says that you only have to install DUN 1.3 to fix this hanging RNAAPP bug. A Message from William Hunt (E-MAIL address unknown) says that sometimes the computer hangs with "RNAAPP (Not Responding)" when you press CTRL-ALT-DEL to bring up the task list. His fix was to hide the file named VNBT.386 which is not needed for an Internet session. Well this is correct; VNBT is a virtual device for NetBIOS over TCP/IP, not needed for connecting to The Internet and using Winsock apps. You will need this file back, however, if you run Client for MS networks over TCP/IP or otherwise want to use NetBIOS apps over it. It also appears, according to Eric Mitchell, that deleting VNBT.386 doesn't work. A better solution, which would prevent this VxD from being invoked, is to set "Disable DNS" and "Disable WINS Resolution" in TCP/IP properties, and specify the DNS address in the dial-up connection's properties directly. However, this bug seems to still creep up. One thing I've noticed is this bug never seems to happen to me. At least not anymore. So I figure I'm doing something different... here's what I do when I set up a connection on a Win95 machine in order to prevent this bug: 1. Remove any traces of non-standard comm drivers, TCP/IP stacks, etc that aren't designed for Win95 2. Remove and re-install Dial-up Networking from Add/Remove Programs / Windows Setup (to replace the related files). Add TCP/IP. 3. Remove any unneeded protocols, clients, etc, and disable any Client or Service bindings to TCP/IP not needed (such as Client for MS Networks) 4. Disable WINS resolution and set "Disable DNS". Finally, OK everything without re-starting. 5. Install Service Pack 1 and the KERNEL32 update, and any other update related to the software you use (Netscape users should get the OLE2 update as well, because I believe it uses OLE) and re-boot 6. When you make your dial-up connection, specify the name servers yourself, and turn off all server type options EXCEPT TCP/IP. I don't know why, but doing the connection up this way seems to prevent this RNAAPP lockup.
Subject: 8.11. 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. There are much simpler programs for free from TUCOWS.
Subject: 8.12. 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. NOTE: Windows 98 and NT 4.0 include descriptors for null modem cables already.
Subject: 8.13. How do I write a dial-up script? Download DUN 1.3 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. 4.00.950B users already have far better scripting options, and older versions can take advantage of them with the Dial-up networking update. 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 and DUN 1.3 include 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. * 8.13.1. How can I issue a "modem break" in a dial-up script? Some terminal servers require that you switch the server's pass through options (so 8-bit ASCII codes don't get mistaken for terminal control codes, for example.) Users of SLiRP will need to do this depending on how their dial-up server works. Here's a piece of script that Jeff Lawson uses to issue the break, then set his local options and then resume. I gather he'd then run SLiRP on the remote terminal and then continue SLIP processing in Win95. waitfor "jzl>" transmit "+++" waitfor "0" transmit "AT\\B0O0^M^M" (This part actually issues the break with AT\B0) waitfor "Local>" transmit "set session passall^M" waitfor "Local>" transmit "resume^M^M" waitfor "jzl>" (Resume normal processing, such as run SLiRP)
Subject: 8.14. How do I set up a dial-up server? Install MS Plus or DUN 1.3. 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. It does appear that you CAN select more than one modem to let the Dial-up Server answer, but when it answers one it refuses to answer on the other. This is the limit of Win95's dial-up server capabilities. 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. * 8.14.1. ...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 * 8.14.2. 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) * 8.14.3. Top ten misconceptions 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...) 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. It doesn't work. (I think this was a vicious rumor spread by some OS/2 advocates.)
Subject: 8.15. 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. Installing the Dial-up Networking update for no particular reason 5. Buying Microsoft Plus! JUST for dial up scripting, before trying DUN 1.3 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 -- ============================================================================== = I am Gordon of Winterpeg. Junk mail is futile. Post MakeMoneyFast = = Find out why: http://spam.abuse.net/spam/ Or eat pink meat from a can = = World's best computer: http://www.amiga.de/ they're both the same = = Windows 95 FAQ: http://www.orca.bc.ca/win95/ http://ga.to/mmf/ = ==============================================================================

User Contributions:

Comment about this article, ask questions, or add new information about this topic:

CAPTCHA




Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Part8 - Part9 - Part10 - Part11 - Part12 - Part13 - Part14 - MultiPage

[ Usenet FAQs | Web FAQs | Documents | RFC Index ]

Send corrections/additions to the FAQ Maintainer:
gordonf@intouch.bc.ca





Last Update March 27 2014 @ 02:12 PM