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
Section - 8.10. Why does my computer hang in task "RNAAPP" when I dial out to The Internet?

( Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Part8 - Part9 - Part10 - Part11 - Part12 - Part13 - Part14 - Single Page )
[ Usenet FAQs | Web FAQs | Documents | RFC Index | Business Photos and Profiles ]


Top Document: Win95 FAQ Part 8 of 14: Dial-up Networking
Previous Document: 8.9. Why can't the dial up connection save my password?
Next Document: 8.11. How can I track time and costs for my dial-up connection?
See reader questions & answers on this topic! - Help others by sharing your knowledge
   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.
   

User Contributions:

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

CAPTCHA




Top Document: Win95 FAQ Part 8 of 14: Dial-up Networking
Previous Document: 8.9. Why can't the dial up connection save my password?
Next Document: 8.11. How can I track time and costs for my dial-up connection?

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

[ 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