Home directory of win95net.txt.gz
From owner-win95netbugs@lists.stanford.edu Mon Jan 22 11:55:14 EST 1996
Article: 992 of comp.os.ms-windows.networking.win95
Path: quantum!revcan!cunews!nott!torn!howland.reston.ans.net!newsfeed.internetmci.com!nntp-hub2.barrnet.net!news.Stanford.EDU!not-for-mail
From: llurch@Networking.Stanford.EDU (Richard Charles Graves)
Newsgroups: comp.os.ms-windows.networking.misc,comp.os.ms-windows.networking.windows,comp.os.ms-windows.win95.setup,comp.os.ms-windows.win95.misc,comp.os.ms-windows.networking.win95,comp.os.ms-windows.setup.win95,alt.os.windows95.crash.crash.crash,uk.comp.os.win95,comp.answers,news.answers
Subject: [*] Windows 95 Networking FAQ, 0/7
Followup-To: comp.os.ms-windows.networking.win95
Date: 18 Jan 1996 22:05:16 -0800
Organization: Stanford University
Lines: 266
Approved: news-answers-request@MIT.EDU
Expires: 16 Feb 1996 12:34:56 GMT
Message-ID:
Reply-To: owner-win95netbugs@lists.stanford.edu
NNTP-Posting-Host: networking.stanford.edu
Mime-Version: 1.0
Content-Type: MULTIPART/DIGEST; BOUNDARY="----------------------------"
Summary: This is the index to the win95netbugs Frequently Asked Questions file. Please read this FAQ before posting a networking problem to the newsgroups.
Keywords: Windows 95 Networking Master Index and Intro FAQ
X-PGP-Key: 0xCCE7B49D, 1024 bits, for llurch@networking.stanford.edu
X-PGP-Print: ED CA 67 98 AD 2A 62 2A 01 17 78 A8 33 F2 6D E0
Xref: quantum comp.os.ms-windows.networking.misc:10408 comp.os.ms-windows.networking.windows:12566 comp.os.ms-windows.win95.setup:46477 comp.os.ms-windows.win95.misc:93976 comp.os.ms-windows.networking.win95:992 comp.os.ms-windows.setup.win95:1095 comp.answers:14050 news.answers:53505
Archive-name: ms-windows/win95netbugs/part0
Posting-Frequency: twice monthly
FAQ-Maintainer: Rich Graves
Last-Change: 18 Jan 1996 by Rich Graves
Version: 4.00.963
URL: http://www-leland.stanford.edu/~llurch/win95netbugs/faq.html
--------------------------
Content-Description: Welcome
This FAQ concerns problems you might encounter with Win95's networking
features after you have set everything up according to the directions, such
as they are. You might want to jump to iii. Index. Please note that I have
not had time for any additions to the FAQ, but there should have been
several. You can help by cleaning up and submitting things mentioned in
section ii. I have made several minor corrections, though.
--------------------------
Content-Description: i. Format of this FAQ
Date: Thu, 18 Jan 96 19:00:00 -0800
From: Rich Graves
The HTML version of this FAQ is lynx 2.3-enhanced for maximum compatibility
with all browsers. Please let me know of any egregious departures from
strict HTML.
The FAQ is maintained entirely by hand, mostly with BBEdit Lite on a
PowerBook for major changes plus vi, emacs, and perl for updates. We don't
need no steenking HTML editor.
This particular text posting was generated by Netscape and Alan Phillips'
excellent Programmer's File Editor.
--------------------------
Content-Description: ii. Unindexed Recent Arrivals
Date: Sat, 30 Dec 95 13:13:13 -0800
From: Rich Graves
My real work does not allow me to keep this FAQ up-to-the-minute. For
breaking information on Windows 95 networking issues, you can browse the
list archive at gopher://quixote.stanford.edu/1m/win95netbugs. To download
the entire list archive, the URL is
gopher://quixote.stanford.edu/00/win95netbugs. Some other stuff is at
http://www-leland.stanford.edu/~llurch/win95netbugs/new.txt. Download these
files to a UNIX system and point a mail reader at them, e.g. mail -f or
pine -f new.txt. I believe Eudora will read the format too.
Another very useful site with information on security bugs in various
Microsoft products is http://www.c2.org/hackmsoft/.
--------------------------
Content-Description: iii. Index
Date: Sat, 30 Dec 95 13:13:13 -0800
From: Rich Graves
A. Administrivia
1. Where is the latest FAQ?
2. What's this about a Win95NetBugs email list?
3. What related resources are available?
4. Copyright 1996 The Board of Trustees of Stanford University.
Noncommercial redistribution encouraged.
5. To do's and cries for help.
6. What's this about a "Hack Microsoft" page?
7. I have a trade secret (or somesuch) that I'd like to contribute
anonymously. How?
8. Acknowledgements
9. What have other people, publications, and world governments had to say
about the win95netbugs effort?
10. What's with this PGP signature thingy?
B. IPX/SPX (NetWare) Issues
1. SAP advertisement kills IPX routing, poses security problems
2. Automatic frame type detection doesn't always work.
3. Where can I get [info on] Novell's Client32?
4. Why do Win95 clients crash my NetWare 3.x servers?
5. How do I enable Long File Name support on a NetWare server?
6. How do I disable Long File Names on a Win95 client so I can use a
server without LFN support?
7. Can I get NetWare broadcast messages (like "low on disk space") on
Win95?
8. Can I send NetWare messages with Win95?
9. Should I use NETX, VLMs, Microsoft's Client, or Novell's Client32?
10. Where can I get Microsoft's NDS Client for NetWare 4.x and bug fixes?
11. User-level access control doesn't work over IPX NWServer.
12. DISPLAY Command in Login Script Displays Incorrect Characters.
13. INCLUDE/DISPLAY Login Script Commands Do Not Accept UNC Paths.
14. NetWare login script processor (NWLSPROC) can't handle lower-case
drive letters.
15. Cannot load TSRs in NetWare login scripts.
16. Cannot Connect to NCP Server Without SAP Advertising Enabled.
17. Commas Not Recognized in NetWare Logon Scripts.
18. How to Configure Windows 95 for Use with NASI.
19. NetWare login might not work if machine name=login name.
20. How do I make RPRINTER work?
21. How to prevent anyone from accessing my entire hard drive?
22. What new (July 1992) login script commands are not recognized by
Win95?
23. Bug storing NetWare passwords unencrypted?
24. What about Personal NetWare and NetWare Lite?
25. MS Client for NetWare Does Not Synchronize Time with Server
26. Can Win95 log on to password-protected NetWare accounts without user
intervention or knowledge?
27. How come I lose mapped drives after a while, and how can I stop it?
28. Can't rename files/directories using NETX under Win95.
29. How can I boot Win95 from a NetWare server on a machine sans hard
drive?
C. TCP/IP (Internet) Issues
1. How do I configure MTU and RWIN?
2. Netscape packet storm bugs.
3. Why are some remote sites unreachable (TTL bug)?
4. Why don't I get DNS resolution for 32-bit applications?
5. Interoperability with BootP servers.
6. Can't mount servers by IP address.
7. How do I set up a HOSTS file?
8. Default hostname resolution order (broadcast-WINS-DNS-LMHOSTS) is
non-ideal for my site; how can I change it?
9. DNS lookup timeout is ridiculously long.
10. Why can't I send mail/news or upload with FTP (MTU path discovery
problem)?
11. What good commercial TCP/IP packages are available for Windows 95?
12. I can't get PC/NFS working under Windows 95.
13. Will Trumpet and other Win3 TCP/IP stacks work under Win95?
14. I'm using some 16-bit TCP/IP stack like Trumpet and 32-bit apps like
Netscape and Exchange don't work.
15. Assorted DNS resolution problems.
16. What arcane TCP/IP parameters can be configured?
17. Nobody seems to be able to get routing to work.
18. Sockets get "eaten up" and WinSmtp dies.
19. Can I disable DNS for WINS resolution?
20. TCP/IP Requires Ethernet_II Frame Type for ODI Driver.
21. Does Win95 support IP Multicast?
22. How to obtain DNS hostname via DHCP?
23. How to prevent anyone from accessing my entire hard drive?
24. How can Win95 and UNIX computers share files and printers?
25. Is there any way to run Win95 from a UNIX server running Samba?
26. How can I prioritize multiple default routers?
27. Why won't the Plus Pack install properly on a machine with Internet
Explorer installed?
28. What do I do if Win95 won't wait long enough for my DHCP server to
assign an address?
29. Why does my winsock.dll disappear or get renamed to winsock.old?
30. Bug in NetBIOS name resolution stops LMHOSTS from working.
D. Dialup Networking (SLIP/PPP) Issues
1. Nonstandard PPP implementation causes problems with BSDI and other
servers.
2. Degraded SLIP/PPP performance versus Trumpet.
3. Killed applications/disconnects cause total system freezes.
4. Minor changes to TCP/IP or modem parameters cause dialup properties to
reset to defaults without warning.
5. Win95 creates fictional COM ports on some plug-and-pray machines.
6. DSCRIPT might exit before getting all dynamically assigned
information.
7. Modem on COM4 incompatible with S3 video cards.
8. PPP compression won't work on at least some Xyplex terminal server
configs.
9. What are some tips for better dialin performance?
10. IPX (NetWare) compression bug.
11. Can't log on to Sun PPP server, or cause Sun PPP server to crash.
12. What's the difference between the Plus Pack and normal dialup
scripters?
13. Where is the SLIP and scripting support?
14. Why do I get "host unreachable" on most remote hosts, though I can get
to my ISP's servers?
15. If my connection drops, why don't my TCP sessions reconnect?
16. How do I change my modem init string?
17. Will Twinsock work in Win95?
18. Will TIA work with Win95?
19. How do you start dialup networking from the command line?
20. Why does Win95 fail to negotiate with a Xylogics TIP if NetBEUI is
enabled?
21. How can multiple machines share one dialup TCP/IP connection?
22. How do I avoid losing all my LAN (i.e., NetWare) connections when I
dial up the Internet?
23. Bug in CHAP (password) negotiation.
24. How can I use SLIP/PPP through a direct connection (i.e., no modem)?
25. Modem locks up with an SMC 666 UART.
E. Miscellaneous Issues
1. No way to specify protocol to use for a specific service.
2. IPX must be set as the default protocol to use a Lotus Notes server.
3. Win95 does not honor LAN Manager security, other incompatibilities.
4. With ODI drivers, adding an NDIS 3.1 protocol does not add frame type
to NET.CFG.
5. How can I hide the Network Neighborhood icon?
6. How can I hide the Inbox icon?
7. How can I get rid of the Microsoft Network icon?
8. How can I get Exchange to work like a normal Internet mail client?
9. I increased the scrollback buffer size in telnet and now it doesn't
work -- no menus even.
10. 10. Microsoft Office 4.3 leaves a file open, preventing proper Windows
shutdown.
11. Why does Microsoft Access crash my server?
12. How do I set up a two-computer twisted pair network?
13. How can I share faxes on Win95?
14. How can I use LAN Manager 2.x services?
15. Why do I get VSHARE and NDIS2SUP failures in BOOTLOG.TXT?
16. What can I try if network support crashes at startup?
17. Why do I sometimes not get a chance to log in on some machines?
18. Where can I get a partial list of errors in the Windows 95 Resource
Kit?
19. The Resource Kit is also wrong about IBM LAN Server, right?
20. Who makes AppleTalk for Windows 95?
21. SysMon and SNMP might conflict with DPMS
22. How can I "browse" with WINPOPUP like you could in Windows 3.11?
23. How do I recover desktop icons like Recycler and Inbox that have
"disappeared"?
24. How do I address "VNETSUP error 6107"?
25. Why should I probably turn all of Win95's power management features
off?
26. Does Win95 support broadcast RPC over TCP/IP or IPX?
27. How to kill Windows' dubious "password caching feature"?
F. Windows Networks (NT, WFW) Issues
1. If your Windows NT client is unable to connect to a Windows 95 server.
2. Incomplete Domain Listing on Large Networks.
3. No Support for "Connect As" Option Like in Windows NT.
4. How do I get Win95 to honor NT %USERNAME%?
5. WFW machines can't log on to Win95 machines with access list from
another domain.
6. Troubleshooting Browsing with Client for Microsoft Networks.
7. Can I log on to multiple NT domains?
8. Error Message: "VNETSUP: Error 6102" (WORKGROUP corruption)
9. Changing NT permissions w/Win95 mgmt tool doesn't work?
G. Hardware-Specific Issues
1. NE4100 and EFA PCMCIA Incompatibility.
2. Eagle NE200T PCMCIA NE200.COM ODI Driver Does Not Work.
3. IBMODISH.COM Causes Windows 95 to Exit at Startup.
4. 3Com 3C5x9 EtherLink III "Plug and Play" problems.
5. MS Client and PC/NFS conflict on some Xircom/IBM/Cabletron adapters.
6. Errors and retransmissions with a SoundBlaster installed.
7. What voodoo is required to get a Xircom Token Ring adapter to work on
a Toshiba laptop?
8. WINIPCFG returns incorrect hardware address on Dell PCs
9. MS Mouse Intellipoint driver/network incompatibility.
10. MsgSvr32 crashes when PC Card NICs are inserted, but network isn't
active.
--------------------------
Content-Description: iv. Trademark and other notices
Date: Sat, 30 Dec 95 13:13:13 -0800
From: Rich Graves
Microsoft, MS, MS-DOS, Windoze, Windows NT, Windows 95, and the Windows
logo are either registered trademarks, trademarks, or parodies of Microsoft
Corporation in the United States and/or other countries. Microsoft
Corporation in no way endorses or is affiliated with The Windows 95
Networking Bugs FAQ. Other trademarks are the property of their respective
lawyers. No animals were harmed in the production of this FAQ. Warning:
downloading this FAQ may hasten the heat death of the Universe. Please also
read these disclaimers.
--------------------------
Rich Graves , friends, and enemies.
Copyright 1996 Rich Graves, Stanford University, and Friends.
Redistribution and mirroring are encouraged provided the source is credited
From owner-win95netbugs@lists.stanford.edu Mon Jan 22 11:55:16 EST 1996
Article: 993 of comp.os.ms-windows.networking.win95
Path: quantum!revcan!cunews!nott!torn!howland.reston.ans.net!newsfeed.internetmci.com!nntp-hub2.barrnet.net!news.Stanford.EDU!not-for-mail
From: llurch@Networking.Stanford.EDU (Richard Charles Graves)
Newsgroups: comp.os.ms-windows.networking.misc,comp.os.ms-windows.networking.windows,comp.os.ms-windows.win95.setup,comp.os.ms-windows.win95.misc,comp.os.ms-windows.networking.win95,comp.os.ms-windows.setup.win95,alt.os.windows95.crash.crash.crash,uk.comp.os.win95,comp.answers,news.answers
Subject: [*] Windows 95 Networking FAQ, 1/7
Followup-To: comp.os.ms-windows.networking.win95
Date: 18 Jan 1996 22:06:10 -0800
Organization: Stanford University
Lines: 278
Approved: news-answers-request@MIT.EDU
Expires: 16 Feb 1996 12:34:56 GMT
Message-ID:
Reply-To: owner-win95netbugs@lists.stanford.edu
NNTP-Posting-Host: networking.stanford.edu
Mime-Version: 1.0
Content-Type: MULTIPART/DIGEST; BOUNDARY="----------------------------"
Summary: Windows 95 Networking FAQ
Keywords: Section A, Administrivia
X-PGP-Key: 0xCCE7B49D, 1024 bits, for llurch@networking.stanford.edu
X-PGP-Print: ED CA 67 98 AD 2A 62 2A 01 17 78 A8 33 F2 6D E0
Xref: quantum comp.os.ms-windows.networking.misc:10409 comp.os.ms-windows.networking.windows:12567 comp.os.ms-windows.win95.setup:46478 comp.os.ms-windows.win95.misc:93977 comp.os.ms-windows.networking.win95:993 comp.os.ms-windows.setup.win95:1096 comp.answers:14051 news.answers:53506
Archive-name: ms-windows/win95netbugs/part1
Posting-Frequency: twice monthly
FAQ-Maintainer: Rich Graves
Last-Change: 18 Jan 1996 by Rich Graves
Version: 4.00.963
URL: http://www-leland.stanford.edu/~llurch/win95netbugs/faq.html
--------------------------
Content-Description: Welcome and Index
This FAQ concerns problems you might encounter with Win95's networking
features after you have set everything up according to the directions, such
as they are. This is section A, Administrivia.
A. Administrivia
1. Where is the latest FAQ?
2. What's this about a Win95NetBugs email list?
3. What related resources are available?
4. Copyright 1996 The Board of Trustees of Stanford University.
Noncommercial redistribution encouraged.
5. To do's and cries for help.
6. What's this about a "Hack Microsoft" page?
7. I have a trade secret (or somesuch) that I'd like to contribute
anonymously. How?
8. Acknowledgements
9. What have other people, publications, and world governments had to say
about the win95netbugs effort?
10. What's with this PGP signature thingy?
--------------------------
Content-Description: A.1. Where is the latest FAQ?
Date: Wed, 27 Dec 95 23:00:00 -0800
From: Rich Graves
The most recent version of this FAQ can be found at:
* http://www-leland.stanford.edu/~llurch/win95netbugs/faq.html
(preferred)
* http://www-dccs.stanford.edu/NetConsult/Win95Net/faq.html (alternate
for old DNS servers)
* ftp://ftp.stanford.edu/pub/mailing-lists/win95netbugs/ (for the
Web-deprived; also has text versions)
Mirror sites in other countries include:
* ftp://ftp.demon.co.uk/pub/mirrors/win95netfaq/
* http://willow.canberra.edu.au/win95netbugs/faq.html
* ftp://oak.canberra.edu.au/win95netbugs
* http://www.mari.su/guide/win95/
* http://www3.uniovi.es/~rivero/win95netbugs/faq.html
Recent but not necessarily up-to-the-minute versions of the FAQ can be
found on your local news server in the newsgroup comp.answers and on the
RTFM FAQ repository and its mirrors.
If the news postings have expired on your site, and you have no Web/FTP
access, you can obtain FAQs through the decwrl ftp mail server. For
instructions, send an email message to ftpmail@decwrl.dec.com with a body
containing simply:
help
You will receive a full set of instructions by return mail.
--------------------------
Content-Description: A.2. What's this about a Win95NetBugs email list?
Date: Wed, 27 Dec 95 14:44:00 -0800
From: Rich Graves
win95netbugs@lists.stanford.edu is an unmoderated electronic mail
discussion list for the purpose of sharing information and, hopefully,
solutions to the networking bugs and "missing features" in Microsoft
Windows 4.x.
It is intended as a relatively low-traffic list for network managers who
know from whence they speak. I don't want any basic setup questions. We are
cooperatively maintaing this FAQ.
If you don't need any more mail littering your inbox, perhaps we could
interest you in the archive of all messages posted to win95netbugs on
gopher://quixote.stanford.edu. Currently the path is 1m/win95netbugs, but
this is likely to change to separate directories for each month Real Soon
Now.
Currently, there is no digest option, but this is expected to become
available "soon." See above for a suggested workaround.
The list is managed automatically by a majordomo list server. To subscribe
to the list, send the command "subscribe win95netbugs" in the body of an
electronic mail message to majordomo@lists.stanford.edu. Do not include
your real name or email in the body of the message; it will be extracted
from the From: header. This is important because if the From: header of
subsequent messages don't match, they will be bounced to the list
moderator.
For more information, email win95netbugs-request@lists.stanford.edu.
Please read the preceding four paragraphs again before inquiring about or
asking to join the list.
Messages sent to the list by non-subscribers will be discarded.
All messages to the list are archived, redistributed on a gopher server,
and physically become the property of Stanford University and other
recipients, though you retain other rights associated with copyright.
Subscriptions from anonymous remailers are very welcome. The majordomo
we're using does not honor the "who" command. Subscriptions from local
mailing lists are not welcome, because of the feedback errors this can
generate.
--------------------------
Content-Description: A.3. What related resources are available?
Date: Mon, 01 Jan 96 23:12:00 -0800
From: Rich Graves
The "official" Microsoft Windows FAQ suite is maintained by
tomh@metrics.com (Tom Haapanen). Information on getting the various Windows
FAQs is posted to comp.os.ms-windows.announce on a weekly basis. The
offical FTP archives for the Windows FAQs are:
ftp://ftp.nimh.nih.gov/pub/win3/FAQ/
ftp://wuarchive.wustl.edu/usenet/comp.binaries.ms-windows/faqs/
ftp://ftp.metrics.com/faq/
More pertinent, up-to-date, and useful resources are also available on the
Net. There's far too many to list. Just see Yahoo's Windows Page. Of
special interest might be the official www.windows.microsoft.com.
Unfortunately, at this writing, all of the Win95 networking resources
listed in Yahoo, with the exception of this one :-), are SLIP/PPP guides
written by nontechnical people. If you have a good guide, please list it in
Yahoo and other directories and send me a note.
For technical information on PC TCP/IP networking, notably some
free/shareware SLIP/PPP servers and IP gateways, see Bernard Aboba's
excellent FAQ for the comp.protocols.tcp-ip newsgroup, which you can get
from:
ftp://ftp.netcom.com/pub/ma/mailcom/IBMTCP/ibmtcp.zip
http://www.zilker.net/users/internaut/update.html
Another useful page from the loyal opposition (David really likes Win95) is
Windows95 Annoyances, http://www.creativelement.com/win95ann/.
Microsoft publishes selected known problems and workarounds in the
Microsoft Knowledge Base, http://www.microsoft.com/kb/. The keywords
"kbnetwork," "3rdPartyNet," and "win95" are useful to know. Another useful
search is "network not kbnetwork," which returns several interesting files.
Shows attention to detail in indexing.
I have recently (December 20th, 1995) become involved with c2.org's "Hack
Microsoft" promotion, which publicizes security bugs in Microsoft's
products. Please see the hackmsoft page, http://www.c2.org/hackmsoft/. You
can read Microsoft's mendacious spin control regarding some of these
security bugs (and other problems too well-known to simply deny) at
http://www.microsoft.com/windows/pr/clarifications.htm.
Finally, those with a technical bent should take a look at Kent Daniel
Bentkowski's Registry FAQ, so that you can help him fix it up and find a
real (non-AOL) home for it. This potentially useful document is,
unfortunatey, homeless at this time, but anyone with sufficient interest
should have no trouble finding it.
--------------------------
Content-Description: A.4. Copyright blah blah blah.
Date: Thu, 07 Dec 95 10:15:00 -0800
From: Rich Graves
Due to Stanford's silly and probably Unconstitutional policy, this FAQ is
Copyright 1996 The Board of Trustees of the Leland Stanford Junior
University. The contents of this document may not be used for any
commercial purpose. Sorry, because parts of this work were done on
Stanford's dime, this work is not covered by the GNU Public License. The
contents of this document may be used in weekly PC magazines, but only with
proper attribution.
--------------------------
Content-Description: A.5. To Do's and cries for help.
Date: Wed, 27 Dec 95 14:51:00 -0800
From: Rich Graves
Except as noted, I'm happy with version 4.00.960 of the FAQ. Please mail me
with corrections and additions.
Oh, one thing I'd like would be searchable hypermail or, even better, nntp
reflectors of the win95netbugs email list. More than one, for
load-balancing and fault tolerance. Please, please mail me if you can host
one. I know how to run one; I'm just not going to, since I've got plenty of
other things to do.
--------------------------
Content-Description: A.6. What's this about a "Hack Microsoft" page?
Date: Wed, 27 Dec 95 17:05:00 -0800
From: Rich Graves
Community ConneXion, a small, privacy-oriented, cypherpunk-owned and
operated ISP in Berkeley, promises fame and fortune (well, a free T-Shirt)
to people who publicly expose security bugs in Microsoft products. The
impetus for this promotion was a high Microsoft official's crowing over
some very minor (in comparison to Microsoft's bugs) problems with Netscape
that were disclosed in September 1995.
The URL for the site is http://www.c2.org/hackmsoft/. Please take a look,
and take steps to avoid these problems; you're kidding yourself if you
believe that "the bad guys" didn't know about all of these problems before
we did.
As of December 20th, 1995, I share responsibility for maintaining the
hackmsoft page.
--------------------------
Content-Description: A.7. I have a trade secret (or somesuch) that I'd like to contribute anonymously. How?
Date: Fri, 29 Dec 95 10:18:00 -0800
From: Rich Graves
If you're serious, send a brief email message describing what you have to
an274074@anon.penet.fi. As appropriate, we will provide instructions for
secure communications with all due blinding. Please allow 72 hours for a
response. Please do not send files to this address. Messages can be
encrypted in PGP key CCE7B49D for llurch@networking.stanford.edu, available
by finger, key server, or in A.10. below.
--------------------------
Content-Description: A.8. Hacknowledgements
Date: Fri, 29 Dec 95 01:05:00 -0800
From: Rich Graves
Everyone who contributed directly to the FAQ and consented to be named is
directly credited. I would also like to single out Eric Hughes, Joe Morris,
Raymond Chen, and Bob Dobbs for special recognition.
--------------------------
Content-Description: A.9. What have other people, publications, and world governments had to say about the win95netbugs effort?
Date: Fri, 29 Dec 95 01:05:00 -0800
From: Rich Graves
There's a separate Web page for that. See
http://www-leland.stanford.edu/~llurch/win95netbugs/rnr.html
--------------------------
Content-Description: A.10. What's with this PGP signature thingy?
Date: Fri, 29 Dec 95 01:25:00 -0800
From: Rich Graves
A separate PGP signature is sent with official text renderings of the FAQ
(i.e., news postings, FTP archive postings). My PGP signature authenticates
authorship and file integrity. Here's my key:
1024/CCE7B49D 1995/10/18 Richard Charles Graves
Key fingerprint = ED CA 67 98 AD 2A 62 2A 01 17 78 A8 33 F2 6D E0
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: 2.6.2
mQCNAzCFUi4AAAEEAN/ubnqjGw3s2lNatp3UIqsMarHA9GyZQijm5kgSMaSrsp6M
u43nYmUvcfEAffDv4bH2uH6D1KnSx5DlNoC7uxzjD2jJjAcIiEo/5wkGrBPUBjA+
C9hHsVXIrzDvXWcz/iHAJhyljgqGl9NkvGAy6PNLcJk/ljmixI3DXUbM57SdAAUR
tDdSaWNoYXJkIENoYXJsZXMgR3JhdmVzIDxsbHVyY2hAbmV0d29ya2luZy5zdGFu
Zm9yZC5lZHU+iQCVAwUQMIVSTo3DXUbM57SdAQGoPQP/bs7uE5T4N6E/i9PVJvl1
5gj9sUeg6SxOuUaLEL6UCxgyKCzPcIXMTxdM3OiFVCbWJp47/jdgeuvtws5N+F6n
jW7gCDSJJSbPMO/SJDICKiWzKlxnj3AFzybdWwlUelRUwbSqZ/fjFTFe41RPgHGA
a9cRiMRXx5AzffnQ5Pm72L4=
=7+9/
-----END PGP PUBLIC KEY BLOCK-----
You can also get my public key via finger or on any MIT keyserver mirror.
If PGP is just another TLA to you, see http://www.eskimo.com/~joelm/ for
some handy Windows tools or http://www.netresponse.com/zldf/ for the
politics.
--------------------------
Rich Graves , friends, and enemies.
Copyright 1996 Rich Graves, Stanford University, and Friends.
Redistribution and mirroring are encouraged provided the source is credited
From owner-win95netbugs@lists.stanford.edu Mon Jan 22 11:55:18 EST 1996
Article: 994 of comp.os.ms-windows.networking.win95
Path: quantum!revcan!cunews!nott!torn!howland.reston.ans.net!newsfeed.internetmci.com!nntp-hub2.barrnet.net!news.Stanford.EDU!not-for-mail
From: llurch@Networking.Stanford.EDU (Richard Charles Graves)
Newsgroups: comp.os.ms-windows.networking.misc,comp.os.ms-windows.networking.windows,comp.os.ms-windows.win95.setup,comp.os.ms-windows.win95.misc,comp.os.ms-windows.networking.win95,comp.os.ms-windows.setup.win95,alt.os.windows95.crash.crash.crash,uk.comp.os.win95,comp.answers,news.answers
Subject: [*] Windows 95 Networking FAQ, 2/7
Followup-To: comp.os.ms-windows.networking.win95
Date: 18 Jan 1996 22:06:58 -0800
Organization: Stanford University
Lines: 589
Approved: news-answers-request@MIT.EDU
Expires: 16 Feb 1996 12:34:56 GMT
Message-ID:
Reply-To: owner-win95netbugs@lists.stanford.edu
NNTP-Posting-Host: networking.stanford.edu
Mime-Version: 1.0
Content-Type: MULTIPART/DIGEST; BOUNDARY="----------------------------"
Summary: Windows 95 Networking FAQ
Keywords: Section B, NetWare
X-PGP-Key: 0xCCE7B49D, 1024 bits, for llurch@networking.stanford.edu
X-PGP-Print: ED CA 67 98 AD 2A 62 2A 01 17 78 A8 33 F2 6D E0
Xref: quantum comp.os.ms-windows.networking.misc:10410 comp.os.ms-windows.networking.windows:12568 comp.os.ms-windows.win95.setup:46479 comp.os.ms-windows.win95.misc:93978 comp.os.ms-windows.networking.win95:994 comp.os.ms-windows.setup.win95:1097 comp.answers:14052 news.answers:53507
Archive-name: ms-windows/win95netbugs/part2
Posting-Frequency: twice monthly
FAQ-Maintainer: Rich Graves
Last-Change: 18 Jan 1996 by Rich Graves
Version: 4.00.963
URL: http://www-leland.stanford.edu/~llurch/win95netbugs/faq.html
--------------------------
Content-Description: Welcome and Index
This FAQ concerns problems you might encounter with Win95's networking
features after you have set everything up according to the directions, such
as they are. This is section B, NetWare.
B. IPX/SPX (NetWare) Issues
1. SAP advertisement kills IPX routing, poses security problems
2. Automatic frame type detection doesn't always work.
3. Where can I get [info on] Novell's Client32?
4. Why do Win95 clients crash my NetWare 3.x servers?
5. How do I enable Long File Name support on a NetWare server?
6. How do I disable Long File Names on a Win95 client so I can use a
server without LFN support?
7. Can I get NetWare broadcast messages (like "low on disk space") on
Win95?
8. Can I send NetWare messages with Win95?
9. Should I use NETX, VLMs, Microsoft's Client, or Novell's Client32?
10. Where can I get Microsoft's NDS Client for NetWare 4.x and bug fixes?
11. User-level access control doesn't work over IPX NWServer.
12. DISPLAY Command in Login Script Displays Incorrect Characters.
13. INCLUDE/DISPLAY Login Script Commands Do Not Accept UNC Paths.
14. NetWare login script processor (NWLSPROC) can't handle lower-case
drive letters.
15. Cannot load TSRs in NetWare login scripts.
16. Cannot Connect to NCP Server Without SAP Advertising Enabled.
17. Commas Not Recognized in NetWare Logon Scripts.
18. How to Configure Windows 95 for Use with NASI.
19. NetWare login might not work if machine name=login name.
20. How do I make RPRINTER work?
21. How to prevent anyone from accessing my entire hard drive?
22. What new (July 1992) login script commands are not recognized by
Win95?
23. Bug storing NetWare passwords unencrypted?
24. What about Personal NetWare and NetWare Lite?
25. MS Client for NetWare Does Not Synchronize Time with Server
26. Can Win95 log on to password-protected NetWare accounts without user
intervention or knowledge?
27. How come I lose mapped drives after a while, and how can I stop it?
28. Can't rename files/directories using NETX under Win95.
29. How can I boot Win95 from a NetWare server on a machine sans hard
drive?
--------------------------
Content-Description: B.1. SAP advertisement kills IPX routing, poses security problems
Date: Wed, 10 Jan 96 15:12:00 -0800
From: Rich Graves
Win95 can be configured to masquerade as a NetWare server/router. This will
cause rather severe problems in many situations. See the brief description
of the problem at http://rcr.csun.edu/ntg/win95.html#novell. The CSUN page
does not detail the steps to steal NetWare passwords with Win95, but it's
not hard to imagine. I believe InfoWorld, Communications Week, PC Week, and
most other trade publications covered the issue as long as nine months ago,
but Microsoft has not fixed the problem.
Another good explanation of the problem is at
http://www-leland.stanford.edu/~llurch/win95netbugs/IPX-SAP-Bug.txt.
One of Microsoft's developers wrote a rather lengthy and only somewhat
misleading response to this issue. It is saved at
http://www-leland.stanford.edu/~llurch/win95netbugs/MS-SAP-Response.txt.
The Windows 95 product manager told me on November 9th that this should be
considered the official Microsoft position on the SAP problem.
Unfortunately, in public, Microsoft only acknowledges, by way of a highly
misleading press release, a "Server Name Conflict Issue." By this they mean
that if someone accidentally or intentionally names a Win95 box
masquerading as a NetWare server (which Novell considers a copyright
violation, by the way) the same as a real NetWare server, the server won't
work. This is actually but a small subset of a larger problem.
Update 01/10/96 thanks to Scott McArthur: Microsoft Knowledge Base article
Q130943 partially addresses this problem in a long footnote. They might
improve the documentation further in the future. I suggest searching the
Microsoft Knowledge Base for the latest "clarifications" from Microsoft.
--------------------------
Content-Description: B.2. Automatic frame type detection doesn't always work.
Date: Thu, 07 Dec 95 10:15:00 -0800
From: Rich Graves
Microsoft acknowledges that the frame type used for IPX/SPX packets must be
set manually because the default "Automatic" frame type detection does not
always work. Most commonly this happens on very quiet or very busy
multiprotocol networks.
You need to open IPX/SPX Compatible Protocol/Properties/Advanced and select
it manually. There is a picture at
http://www-dccs.stanford.edu/NetConsult/Win95Net/ipxprops.GIF.
--------------------------
Content-Description: B.3. Where can I get [info on] Novell's Client32?
Date: Wed, 27 Dec 95 14:56:00 -0800
From: Rich Graves
Official information on Novell's Client32 NetWare Client for Windows 95,
which replaces Microsoft's client, is available at
http://netwire.novell.com/home/client/client32/. At this writing, the last
update to the publicly available software was posted in early December.
Officially registered beta sites probably receive incremental updates.
Unlike some other computer companies, Novell has posted a reasonably open
and honest FAQ. The only publicly discussed problem I don't see is that
Client32 appears to be incompatible with Microsoft's NET command when run
in a DOS box. This can be a major bummer if you use multiple network
protocols.
--------------------------
Content-Description: B.4. Why do Win95 clients crash my NetWare 3.x servers?
Date: Wed, 27 Dec 95 14:59:00 -0800
From: zim@grayfox.svs.com (Jason Zimberoff)
There have been many reports of Win95 clients causing NetWare servers to
crash. Florent.Cretiaux@wavinbv.nl says computer magazines in the
Netherlands are urging people not to install Win95 for this reason. Several
things can cause this problem:
1. Packet Bursts. The problem often isn't Win95, per se, but the packet
burst mode that it supports by default. Older servers can't handle
packet bursts, a late 3.12/4.0 performance enhancement.
There are two ways to resolve the problem of packet bursts:
1. Get the file pburst.exe from Novell's BBS or Internet servers and
install the patch on your server.
2. Disable packet burst on the Win95 clients by adding the following
to system.ini:
[nwredir]
supportburst=0
2. Old .LAN Driver. I have been told that an old network interface card
driver (.LAN) on the server might also cause this problem. As could a
386/486 server that's just too, well, old to handle the demands of
your fancy new Pentiums running Win95. Loading NetWare's VLMs on a hot
new Pentium would cause the same problem. (If you ignored Novell's
documentation of this problem, that is; Novell is pretty quick to
document and patch known problems with its products.)
3. VM Swapfile on Server. By default, server installations of Win95 put
the virtual memory swap file on the server, which strikes me as
monumentally stupid. The University of Arkansas banned Win95 machines
from their network for some time because this feature caused several
NetWare servers to get overloaded and crash.
4. Record Lock Overflow. Certain very poorly written applications, such
as Microsoft Access, can lock up any kind of server with record locks.
Please see question E.11. for information on this bug in Microsoft
Access.
--------------------------
Content-Description: B.5. How do I enable Long File Name support on a NetWare server?
Date: Tue, 10 Oct 1995 20:00:00 GMT
From: ClubWin dude Ramesh and Rich Graves
Just install the OS/2 namespace. This requires NetWare 3.12 or a patched
3.11. Most of the time, it seems to work. If Win95 clients crash your
server or something, remove the OS/2 namespace and see the next question. I
am not a CNE! Don't ask me!.
Because of a little bug, Win95 will not use long file names on 3.11 servers
when you use Policy Editor to tell it to do so. The easier workaround is to
add the following to system.ini:
[nwredir]
SupportLFN=2
For more information on this problem, see article Q137275 in the Microsoft
Knowledge Base.
Because of another bug, you will probably need to apply the os2opnfx.nlm
patch. One place to get it is
ftp://ftp.novell.com:/pub/netware/nwos/nw311/311ptd.exe. The ReadMe for
this patch says:
OS2OPNFX NLM
1409 02-02-93 7:10a
This patch allows a user to use the "TYPE" command to view a file even
though SCAN file rights have not been granted. Without this patch, if the
user is granted all rights but the SUPERVISOR and SCAN file rights
(including Read) the file still cannot be "TYPE"ed. This patch fixes this
problem.
[Um... yes. I'm sure it does. I don't think I want to know why Win95
cares.]
--------------------------
Content-Description: B.6. How do I disable Long File Names on a Win95 client so I can use a server without LFN support?
Date: Thu, 07 Dec 95 10:15:00 -0800
From: Rich Graves
Contributions by ramesh@scr.siemens.com (Ramesh Viswanathan) and
edwardd@finance.ci.seattle.wa.us.
If you run POLEDIT (it's on the CD in admin\apptools\poledit) and open the
registry, you can then go to Local Computer, Network, Microsoft Client for
Netware Networks, and turn off use of long names on the server.
Alternatively, add the following to system.ini:
[nwredir]
SupportLFN=0
--------------------------
Content-Description: B.7. Can I get NetWare broadcast messages (like "low on disk space") on Win95?
Date: Wed, 27 Dec 95 15:02:00 -0800
From: Rich Graves
Contributions by Don Zimmer (drzimmer@ionet.net) and "ClubWin" member
ramesh@scr.siemens.com (Ramesh Viswanathan)
By default, Win95 machines using Microsoft's 32-bit NetWare client do not
receive NetWare broadcast messages. Novell recommends using their software
instead.
You could also put WINPOPUP.EXE in your Startup folder. However, there's
apparently no way to remove WINPOPUP from the task list or to stop users
from quitting it.
Several people have also complained that WINPOPUP doesn't work for them,
though we haven't been able to determine why. Please mail me if you have
insight into this problem.
Novell's Client32 resolves this problem (and introduces some others).
--------------------------
Content-Description: B.8. Can I send NetWare messages with Win95?
Date: Tue, 10 Oct 1995 20:00:00 GMT
From: Rich Graves
Yes, you can, with WinPopup, provided that IPX/SPX is your default
protocol. However, messages are limited to 38 characters, and there are
other limits. See article Q120223 in the Microsoft Knowledge Base.
--------------------------
Content-Description: B.9. Should I use NETX, VLMs, Microsoft's Client, or Novell's Client32?
Date: Wed, 27 Dec 95 15:06:00 -0800
From: Rich Graves
Yes. Otherwise you won't be able to use NetWare servers. :-)
There is no authoritative answer to this question. It depends on which mix
of bugs and features works best in your environment.
In a loosely "controlled" environment like mine, I have to support
Microsoft's client, because it's the easiest to obtain and install, which
means that people are going to use it anyway. Microsoft's client also seems
to be the least likely to actually crash the Win95 machine. However, it is
the most likely to crash your server.
You must use Novell's Client32 if you need one or more of the following
features:
* Full NDS support
* Reliable execution of login scripts
* NETX/VLM emulation for legacy apps
* NetWare/IP support
--------------------------
Content-Description: B.10. Where can I get Microsoft's NDS Client for NetWare 4.x and bug fixes?
Date: Wed, 27 Dec 95 15:07:00 -0800
From: Rich Graves
All publicly available updates to Windows 95 are available at the URL
http://www.windows.microsoft.com/software/updates.htm. You'll want the NDS
service, the shell update bug fix, and the security bug fix, for starters.
Please note that Microsoft's politically correct term for these updates is
"functionality enhancement."
--------------------------
Content-Description: B.11. User-level access control doesn't work over IPX NWServer.
Date: Thu, 07 Dec 95 10:15:00 -0800
From: Rich Graves
Win95's built-in peer-to-peer sharing capabilities don't work over the
built-in IPX/SPX="compatible" protocol with share-level access control. You
need to enable user-level access control with an NT or NetWare server for
authentication. See article Q131354 in the Microsoft Knowledge Base.
In any case, you really shouldn't be sharing over IPX unless you really
know what you're doing, because of the SAP problem, B.1. Sharing over SMB
(NetBEUI or TCP/IP) is safer and faster.
--------------------------
Content-Description: B.12. DISPLAY Command in Login Script Displays Incorrect Characters.
Date: Tue, 10 Oct 1995 20:00:00 GMT
From: Rich Graves
If your Novell NetWare login script contains a DISPLAY command with a very
long path, or uses an environment variable containing a very long path,
some information may not be displayed correctly. An internal buffer is too
small. Use a shorter path or environment variable. See article Q132763 in
the Microsoft Knowledge Base.
Novell's Client32 resolves this problem (and introduces others).
--------------------------
Content-Description: B.13. INCLUDE/DISPLAY Login Script Commands Do Not Accept UNC Paths.
Date: Tue, 10 Oct 1995 20:00:00 GMT
From: Rich Graves
If you are using a NetWare login script, INCLUDE and DISPLAY commands in
the login script that contain Universal Naming Convention (UNC) paths do
not work. The named files are not run or displayed. See article Q135167 in
the Microsoft Knowledge Base.
Novell's Client32 resolves this problem (and introduces others).
--------------------------
Content-Description: B.14. NetWare login script processor (NWLSPROC) can't handle lower-case drive letters.
Date: Tue, 10 Oct 1995 20:00:00 GMT
From: Rich Graves
If you are using NetWare login scripts that use lower-case drive letters,
you need to capitalize them. See article Q132665 in the Microsoft Knowledge
Base.
Novell's Client32 resolves this problem (and introduces others).
--------------------------
Content-Description: B.15. Cannot load TSRs in NetWare login scripts.
Date: Wed, 27 Oct 1995 15:10:00 -0800
From: Rich Graves
If you need this functionality, use Novell's VLMs or NETX. See article
Q127794 in the Microsoft Knowledge Base.
--------------------------
Content-Description: B.16. Cannot Connect to NCP Server Without SAP Advertising Enabled.
Date: Thu, 07 Dec 95 10:15:00 -0800
From: Rich Graves
Microsoft acknowledges that this is a problem with Win95. See article
Q130943 in the Microsoft Knowledge Base.
Do not turn on SAP, as Microsoft tells you to do, without considering the
routing and security ramifications discussed in Section B.1.
--------------------------
Content-Description: B.17. Commas Not Recognized in NetWare Logon Scripts.
Date: Tue, 10 Oct 1995 23:00:00 GMT
From: Rich Graves
Microsoft recognizes this as a problem with Win95. You need to replace any
commas in your login scripts with ANDs, or use Novell's drivers rather than
Microsoft's. See article Q129145 in the Microsoft Knowledge Base.
Novell's Client32 resolves this problem (and introduces others).
--------------------------
Content-Description: B.18. How to Configure Windows 95 for Use with NASI.
Date: Tue, 10 Oct 1995 23:00:00 GMT
From: Rich Graves
You need to use ODI drivers. See article Q125425 in the Microsoft Knowledge
Base.
Novell's Client32 resolves this problem (and introduces others).
--------------------------
Content-Description: B.19. NetWare login might not work if machine name=login name.
Date: Mon, 2 Oct 1995 13:31:28 CST6CDT
From: Larry Field
l-field@tamu.edu (Larry Field) wrote:
>I'm using the Client for Netware as my primary logon client in Windows 95.
>However when I dial-up and login to my network I'm not getting the login
>script processed. I can go into Network Neighborhood and see my drives and
>directories on the network drive but I don't have any drive mappings, printer
>assignments, etc.
>
>Any ideas how I can get the logon procedure to execute the login script? I
>have the box checked that says "Process login script" so I'm at a loss as to
>why it's not processing.
Well I solved my own problem and here's the answer for anyone else
that experiences similar things.
My computer name in Control Panel | Network | Identification was the
same as my Netware logon name. Once I changed this it processes the
login script and maps all the drives just fine. I guess there's some
kind of conflict when the name of the machine and the logon id are the
same.
Larry Field
Sr. Systems Analyst
Texas A&M University
--------------------------
Content-Description: B.20. How do I make RPRINTER work?
Date: Wed, 27 Dec 95 15:12:00 -0800
From: gordonf@opus.freenet.vancouver.bc.ca (Gordon Fecyk)
I managed to get a WIn95 machine to act as RPRINTER using all 32-bit
services and clients! I only managed to get this working on a NetWare 3.11
environment so far, but the same applies to NetWare 3.12. 4.0 & 4.1 users
can wait for Novell to clean up their Client32...
First off... Win95's PRTAGENT (this is what it's called on the Win95 CD,
under ADMIN\NETTOOLS\PRTAGENT) requires exclusive access to a NetWare print
server object. This means you need to create one separate Print Server
object on the NetWare server for each Win95 station acting as RPRINTER.
Here's what each print server object looks like:
Each object has only ONE PRINTER, which is Printer 0, named "Printer 0".
Set this printer to be a "Remote Parallel" printer using LPT1. You can tell
it to use IRQ7 if you want.
Tell this one printer to service a particular print queue. A NW 3.1x server
handles 16 queues, so pick one of them for this printer, within this print
server object, to service.
OK now that you have a unique print server object for each Win95 machine
running PRTAGENT, go to the machine in question and install "Microsoft
Print Agent for NetWare", by adding it as a "service" in the network
control panel. Hit "Have disk" and go to ADMIN\NETTOOLS\PRTAGENT.
After installing it, reboot.
Then, go to the printers folder and select the printer driver you want to
service the Print Server object in the NW server. Select the Print Server
tab, select the NW server and the Print Server object to service.
[More details might also be available in the Resource Kit and in the
win95netbugs list archive]
--------------------------
Content-Description: B.21. How to prevent anyone from accessing my entire hard drive?
Date: Thu, 07 Dec 95 10:15:00 -0800
From: Rich Graves
If you have a non-English-language version of Windows 95, you can't, unless
you disable peer sharing and remote administration.
If you have the English-language version, get the patches from
http://www.windows.microsoft.com/software/w95fpup.htm. Microsoft's
clarification is incorrect (for starters, they didn't discover these
problems; we know who pointed them out to them), but the patches appear to
fix the problem.
--------------------------
Content-Description: B.22. What new (July 1992) login script commands are not recognized by Win95?
Date: Fri, 13 Oct 1995 09:42:47 GMT0BST
From: Phil Randal
[Just one of the liabilities of Microsoft refusing to participate in
NetWare interoperability testing.]
The Microsoft Windows 95 Netware Client does not recognize the
following two NetWare login script commands:
NO_DEFAULT and SET_TIME
They were introduced in version 3.65 of login.exe for NetWare 3.11 in
July 1992. I haven't checked the semicolons at end of strings, but
I'm almost willing to bet on it...
Here are the details from Novell's log365.doc dated July 20, 1992:
1) The current version of login does not recognize ;'s at the end
of a string in the login script. (The ; is used for string
concatenation.)
2) This version contains a NO_DEFAULT parameter to place in the
system login script. If a user login script does not exist, the
default login script will not be executed.
3) This utility also allows the user to specify if login.exe should
synchronize the workstation time with the file server time.
Currently, login always synchronizes the workstation time with the
file server time. This new LOGIN.EXE allows the user to specify
if this synchronization should occur by using a new command in the
login script. It is as follows:
SET_TIME [ON | OFF]
SET_TIME OFF will not synchronize workstation time with the file
server when logging in.
SET_TIME ON will cause the workstation time to synchronize with the
file server time when logging in. (default)
--------------------------
Content-Description: B.23. Bug storing NetWare passwords unencrypted?
Date: Fri, 06 Oct 1995 11:25:30 -0800
From: Rich Graves
Microsoft never acknowledged this bug, but they did fix it. The problem is
that under circumstances that have not been isolated, .PWL files can be
created that allow access to NetWare servers without even logging in. Among
the people who have seen this are Stephen R. Davis
and Gary Flynn .
--------------------------
Content-Description: B.24. What about Personal NetWare and NetWare Lite?
Date: Tue, 10 Oct 1995 07:20:58 GMT
From: ramesh@scr.siemens.com (Ramesh Viswanathan)
Just ask Novell: http://netwire.novell.com/ServSupp/client/win95/pnwfaq.htm
Tijs Coumans claims the same basic instructions work for NetWare Lite,
though Novell says they don't.
--------------------------
Content-Description: B.25. MS Client for NetWare Does Not Synchronize Time with Server
Date: Sun, 15 Oct 95 09:28:23 -0700
From: Microsoft
See Microsoft Knowledge Base article Q136591,
http://www.microsoft.com:80/KB/PEROPSYS/win95/Q136591.htm.
--------------------------
Content-Description: B.26. Can Win95 log on to password-protected NetWare accounts without user intervention or knowledge?
Date: Wed, 1 Nov 1995 22:40:15 -0600
From: Eric Helfgott
This is actually a very interesting bug in Win 95 which Microsoft denies
the existence of. Win 95 can actually be configured to cache both the
Windows and Netware passwords so that a user booting the system will
automatically be logged onto a netware network need not type any password
whatsoever - for Windows or Netware. If the .pwl files being generated are
~900 byes long versus the regular 600 bytes, your system is doing this.
Naturally this bypasses any and all security of netware networks.
My system behaves this way; and I can actually use it to create .pwl files
for other systems which bypass the netware security on those systems as
well. Microsoft claims this only works for "null" netware passwords - which
is simply not true, but the system must be tricked into generating these
.pwl files. As proof, if you wish to have such a .pwl file please request
so of me via Win 95 Netbugs and I'll generate one for you which does this.
To stop your system from generating these pwl files, just delete all of
those in your Windows directory, and change the primary network logon to
Windows and then back to Microsoft Client for Netware and your system will
stop generating these security killers. I actually find the bug useful for
PCs in secured areas which one may wish to remotely reboot using remote
access software like Stac Electronic's Reachout. :)
Eric Helfgott
Systems Engineer
Drug Intervention Services of America, Inc.
--------------------------
Content-Description: B.27. How come I lose mapped drives after a while, and how can I stop it?
Date: 7 Nov 1995 20:29:02 GMT
From: George Shaw
In the Control Panel,Power Icon, if you turn "Off" Power Management, the
mappings seem to quit going away. Damned if I can figure out why this
works, but it does.
--------------------------
Content-Description: B.28. Can't rename files/directories using NETX under Win95.
Date: 29 Dec 1995 20:30:00 PST
From: Rich Graves
Lloyd Williams and a dozen others have reported this. This is true. VLMs,
Microsoft's Client for NetWare Networks, and Novell's Client32 do not have
this problem. Novell doesn't really recommend using NETX nowadays anyway...
--------------------------
Content-Description: B.29. How can I boot Win95 from a NetWare server on a machine sans hard drive?
Date: 29 Dec 1995 20:43:00 PST
From: Rich Graves
It's not easy, but it can be done. See win95boo.txt and other files on
JoeD's machine, netlab2.usu.edu. Look in the misc (not pub/misc) directory.
netlab2 is running Novell's brain-dead FTP server that does not support
passive mode or many other modern niceties, so if your FTP client gives you
an error message, try the UNIX or DOS command-line FTP clients.
--------------------------
Rich Graves , friends, and enemies.
Copyright 1996 Rich Graves, Stanford University, and Friends.
Redistribution and mirroring are encouraged provided the source is credited
From owner-win95netbugs@lists.stanford.edu Mon Jan 22 11:55:20 EST 1996
Article: 995 of comp.os.ms-windows.networking.win95
Path: quantum!revcan!cunews!nott!torn!howland.reston.ans.net!newsfeed.internetmci.com!nntp-hub2.barrnet.net!news.Stanford.EDU!not-for-mail
From: llurch@Networking.Stanford.EDU (Richard Charles Graves)
Newsgroups: comp.os.ms-windows.networking.misc,comp.os.ms-windows.networking.windows,comp.os.ms-windows.win95.setup,comp.os.ms-windows.win95.misc,comp.os.ms-windows.networking.win95,comp.os.ms-windows.setup.win95,alt.os.windows95.crash.crash.crash,uk.comp.os.win95,comp.answers,news.answers
Subject: [*] Windows 95 Networking FAQ, 3/7
Followup-To: comp.os.ms-windows.networking.win95
Date: 18 Jan 1996 22:07:49 -0800
Organization: Stanford University
Lines: 1022
Approved: news-answers-request@MIT.EDU
Expires: 16 Feb 1996 12:34:56 GMT
Message-ID:
Reply-To: owner-win95netbugs@lists.stanford.edu
NNTP-Posting-Host: networking.stanford.edu
Mime-Version: 1.0
Content-Type: MULTIPART/DIGEST; BOUNDARY="----------------------------"
Summary: Windows 95 Networking FAQ
Keywords: Section C, Internet Protocols
X-PGP-Key: 0xCCE7B49D, 1024 bits, for llurch@networking.stanford.edu
X-PGP-Print: ED CA 67 98 AD 2A 62 2A 01 17 78 A8 33 F2 6D E0
Xref: quantum comp.os.ms-windows.networking.misc:10411 comp.os.ms-windows.networking.windows:12569 comp.os.ms-windows.win95.setup:46480 comp.os.ms-windows.win95.misc:93979 comp.os.ms-windows.networking.win95:995 comp.os.ms-windows.setup.win95:1098 comp.answers:14053 news.answers:53508
Archive-name: ms-windows/win95netbugs/part3
Posting-Frequency: twice monthly
FAQ-Maintainer: Rich Graves
Last-Change: 18 Jan 1996 by Rich Graves
Version: 4.00.963
URL: http://www-leland.stanford.edu/~llurch/win95netbugs/faq.html
--------------------------
Content-Description: Welcome and Index
This FAQ concerns problems you might encounter with Win95's networking
features after you have set everything up according to the directions, such
as they are. This is section C, TCP/IP.
C. TCP/IP (Internet) Issues
1. How do I configure MTU and RWIN?
2. Netscape packet storm bugs.
3. Why are some remote sites unreachable (TTL bug)?
4. Why don't I get DNS resolution for 32-bit applications?
5. Interoperability with BootP servers.
6. Can't mount servers by IP address.
7. How do I set up a HOSTS file?
8. Default hostname resolution order (broadcast-WINS-DNS-LMHOSTS) is
non-ideal for my site; how can I change it?
9. DNS lookup timeout is ridiculously long.
10. Why can't I send mail/news or upload with FTP (MTU path discovery
problem)?
11. What good commercial TCP/IP packages are available for Windows 95?
12. I can't get PC/NFS working under Windows 95.
13. Will Trumpet and other Win3 TCP/IP stacks work under Win95?
14. I'm using some 16-bit TCP/IP stack like Trumpet and 32-bit apps like
Netscape and Exchange don't work.
15. Assorted DNS resolution problems.
16. What arcane TCP/IP parameters can be configured?
17. Nobody seems to be able to get routing to work.
18. Sockets get "eaten up" and WinSmtp dies.
19. Can I disable DNS for WINS resolution?
20. TCP/IP Requires Ethernet_II Frame Type for ODI Driver.
21. Does Win95 support IP Multicast?
22. How to obtain DNS hostname via DHCP?
23. How to prevent anyone from accessing my entire hard drive?
24. How can Win95 and UNIX computers share files and printers?
25. Is there any way to run Win95 from a UNIX server running Samba?
26. How can I prioritize multiple default routers?
27. Why won't the Plus Pack install properly on a machine with Internet
Explorer installed?
28. What do I do if Win95 won't wait long enough for my DHCP server to
assign an address?
29. Why does my winsock.dll disappear or get renamed to winsock.old?
30. Bug in NetBIOS name resolution stops LMHOSTS from working.
--------------------------
Content-Description: C.1. How do I configure MTU and RWIN?
Date: Sat, 18 Nov 1995 12:50:07 -0800 (PST)
From: Rich Graves
By default, Win95 uses the largest value of MTU possible for the chosen
media type. Most people who used the excellent 16-bit Trumpet Winsock,
whose FAQ is at http://www.trumpet.com.au/wsk/faq/wskfaq.htm, configured
these parameters for optimum efficiency and response, and really miss
Trumpet's interface for setting them. This exchange should help:
>I would like to know how to customize PPP, if it's possible.
>I mean how to change MTU value, RWIN value, etc...
>(registration base ? ...)
>
>And if it's possible, what are the best values for a 28.8 connection ?
MTU and RWIN are hidden in two different places in the Registry. MTU can
be set for each protocol-adapter binding; RWIN is set globally.
For MTU, open the Registry to:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\NetTrans\
Figure out which 000n is the TCP/IP protocol for your DUN connection by
looking at the other values, then open up that 000n.
Inside that 000n, create a new string variable called "MaxMTU" and enter
your value. 1500 is the default; some terminal servers work better with
1002; lowest you should ever need is 552. In general, use the highest MTU
your machine can handle without overruns.
For RWIN, open the Registry to:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\MSTCP\
Create a new string variable called "DefaultRcvWindow" with a value 4
times (MTU + 24).
It might also help to turn off your modem compression features; consult
your modem manual, and enter an init string into DUN Modem Advanced
Properties\Extra Settings.
--------------------------
Content-Description: C.2. Netscape Packet Storm Bugs. c2
Date: Wed, 27 Dec 95 15:15:00 -0800
From: Rich Graves
This appears to be a bug specific to Netscape, but it's worth mentioning
here because so many people use it. Netscape 1.2N and 2.x, 32-bit versions,
do not back off from TCP RESETs and ICMP unreachable messages; instead,
they retransmits forever, with no timeout. On a dialup connection this will
only cause some annoying "hangs," inducing the user to hit the "Stop" and
"Reload" buttons a lot, but it can cause destructive packet storms on
Ethernet and other high-bandwidth links.
Please see the initial post about this set of bugs at
http://www-leland.stanford.edu/~llurch/win95netbugs/Readme-Netscape_Net_Bug.txt.
That tells where to get relevant packet traces.
Two URLs you can try to check for these bugs are http://ftp.netscape.com
(responds with a TCP RESET) and http://36.36.0.10 (nonexistent network,
responds with an ICMP unreachable).
The Netscape product manager posted a message claiming the problem was
irreproducible, to which I posted a response. Anyway, you can probably
reproduce the problem yourself with the URLs above. You need some technical
knowledge of the Internet Protocols to understand the problem.
Netscape 2.x attempts to avoid the problem by timing out, but this doesn't
always work.
Netscape 2.0b4 also still seems to lose track of multiple TCP connections.
E.g. local users usually can't load www-leland's root page all the way. If
a page seems to load halfway and then "hang," then try hitting reload or
stop. If this happens often, set maximum simultaneous TCP connections to 1
in network preferences. This will not really affect dialups, but it will
noticeably slow page loading if you have a high-speed LAN connection.
Information from other winsock programmers indicates that this last problem
is probably due to a bug in Win95's TCP/IP stack, not in Netscape. The
Microsoft Internet Explorer works around the problem, but non-Microsoft
programmers have not been given information that would allow them to do the
same.
Ian Samson reports that the same thing happens to him
in Johannesburg -- Hi! :-)
--------------------------
Content-Description: C.3. Why are some remote sites unreachable (TTL bug)?
Date: Wed, 27 Dec 95 10:15:00 -0800
From: Bob Cringely
Cringely's column in a recent InfoWorld said that Win95 couldn't connect to
some sites because its TTL was set to 30 hops.
As far as I can tell, his source was wrong. It's 32 (which really isn't
much of an improvement).
Because the Internet has grown to the point where routes including greater
than 32 hops are rather common, everyone should open RegEdit to:
Hkey_Local_Machine\System\CurrentControlSet\Services\VxD\MSTCP
Create a string variable named "DefaultTTL" with a value of, say, 128.
Another example of Microsoft's poor understanding of the Internet.
--------------------------
Content-Description: C.4. Why don't I get DNS resolution for 32-bit applications?
Date: Wed, 27 Dec 1995 15:22:00 -0700
From: Rich Graves
This is a more general form of Microsoft's Knowledge Base article Q139060,
which appears to have been posted on December 5, a month after I sent them
the following:
Problem:
1. You have Microsoft's TCP/IP protocol installed and properly configured.
2. 16-bit applications work by DNS name and IP address.
3. 32-bit applications work if you give an IP address.
4. 32-bit applications fail if you give a DNS hostname.
Most Likely Cause:
The file wsock32.dll is in your PATH, but is not correctly specified in
the following Registry key:
->Hkey_local_machine->system->currentcontrolset->services->vxd->
mstcp->serviceprovider
The normal value for this key is %WINDIR%\SYSTEM\WSOCK32.DLL
Most Likely Solution:
Make sure wsock32.dll is in your WINDOWS\SYSTEM directory. Run REGEDIT.EXE to
specify the correct location.
More information:
There is a bug in NETSETUP that will cause this problem most of the time.
(Thanks to Lee Gates of Microsoft for pointing this out).
There appears to be a bug in SETUP that will cause this problem if you
install Win95 in one directory, then later reinstall it into a different
directory.
You might also see this problem if you moved your various WinSock files
around in an attempt to get a third-party WinSock.DLL file working.
Microsoft has confirmed this to be a problem in Microsoft Windows 95. We
will post more information here in the Knowledge Base as it becomes
available.
I later got this reply, which is puzzling. He says his %WINDIR% variable is
set incorrectly to C:, even though it is set correctly to C:\WINDOWS in
MSDOS.SYS. remind me to follow up with this fella, or better, mail him
yourself.
From: parkerr@serv2.fwi.com
Newsgroups: comp.os.ms-windows.win95.misc,comp.os.ms-windows.win95.setup,comp.os.ms-windows.networking.tcp-ip
Subject: Re: Summary: 32-bit TCP/IP DNS problems on Win95
Date: 4 Nov 1995 04:59:32 GMT
Message-ID: <47ervk$e0v@news.ios.com>
>Okay, so it wasn't in my path. But it was specified correctly in the
>registry. Needless to say, it didn't fix the problem. Does anyone have
>a canonical list of "solutions" to this problem? There must be
>something I haven't tried.
I found my problem, though I still don't know why... The registry would
be right, if windir actually pointed to my windows directory. Instead it
is "C:". Not even "C:\". Unfortunately, I can't figure out who is
responsible for this. My MSDOS.SYS has it specified correctly, and I
don't find it anywhere in the registry (searching for windir).
I solved my problem, at least for now, by creating c:\system and putting
*sock* into it.
--------------------------
Content-Description: C.5. Interoperability with BootP servers.
Date: Wed, 27 Dec 95 15:28:00 -0800
From: Rich Graves
Microsoft's chose to implement DHCP in a way that is not interoperable with
BootP. One surmises they wanted to sell more NT DHCP servers.
John Wobus's DHCP FAQ, at
http://web.syr.edu/~jmwobus/comfaqs/dhcp.faq.html, might be of interest.
There are some hybrid BootP/DHCP servers out there, but they don't all
interoperate, and your routers might need to be upgraded to handle the kind
of DHCP replies Microsoft likes. Anyway, read John's FAQ. If you absolutely
can't get it from the Web, or from the periodic posts to the newsgroup
comp.protocols.tcp-ip.ibmpc, you can ping John at jmwobus@syr.edu.
We (various Stanford people) met with Microsoft officials about various
DHCP issues on December 8th. I summarized the meeting for the list.
Basically, they plan to support non-Microsoft BootP clients from NT Server
"soon," but do not plan to support a BootP client for any version of
Windows for the forseeable future.
Background:
1. Microsoft sells a DHCP server for NT, but no BootP server.
2. DHCP and BootP are 95% identical. DHCP is based on BootP. BootP is
simpler and more widely used.
3. The DHCP RFCs are at the "proposed" stage.
4. This stage is defined as "likely to change" and "experimental."
5. The DHCP RFCs suggest that BootP and DHCP should interoperate.
6. Most non-Microsoft DHCP servers support BootP.
7. Most newer non-Microsoft BootP clients support DHCP.
8. Apple's Open Transport supports BootP, DHCP, and RARP.
9. Microsoft supported BootP in earlier versions of TCP/IP for Windows.
10. Most BootP servers run on UNIX.
11. UNIX and NT are competitors.
12. Windows dominates the market for network clients.
13. Microsoft only supports DHCP in the current versions of Win95, WFW,
and NT.
I have been told that there is absolutely no causual relationship here.
--------------------------
Content-Description: C.6. Can't mount servers by IP address.
Date: Wed, 27 Dec 95 15:31:00 -0800
From: Rich Graves
This is just an annoyance, really. It should be possible to mount servers
by typing e.g. \\36.36.0.10, but it just isn't.
I suppose the workaround is to enter a bogus hostname into your
WINDOWS\HOSTS file. See WINDOWS\HOSTS.SAM for the format, but note that the
"live" version has no .SAM (or other) file type extension.
--------------------------
Content-Description: C.7. How do I set up a HOSTS file?
Date: Wed, 27 Dec 95 23:00:00 -0800
From: Rich Graves
Um, just set up a C:\WINDOWS\HOSTS file. The common mistake is to give this
file a .SAM or .TXT extension. That's wrong -- it gets no file type
extension. See HOSTS.SAM for the simple file format.
--------------------------
Content-Description: C.8. Default hostname resolution order (broadcast-WINS-DNS-LMHOSTS) is non-ideal for my site; how can I change it?
Date: Sun, 17 Sep 95 22:30:47 -0800
From: Rich Graves
I would think that the name resolution should work in precisely the
opposite direction. Check the local LMHOSTS mappings first, then DNS, then
WINS, and only as a last resort broadcast on the local subnet. Oh well.
This extract from the Resource Kit comes from Daniel M
Most apps will freeze the machine while doing a DNS lookup, which is really
annoying, especially since the timeout for DNS lookups is so long,
especially in those weird places like Cornell and Clemson where Win95
doesn't seem to like the local DNS server. The "NameSrvQueryTimeout" in the
Registry, which some people have pointed out, seems only to apply to
Microsoft's proprietary WINS service, not Internet standard DNS.
There's gotta be a way to set this; anybody?
--------------------------
Content-Description: C.10. Why can't I send mail/news or upload with FTP (MTU path discovery problem)?
Date: Wed, 27 Dec 95 15:33:00 -0800
From: Rich Graves
If you can't send mail or news longer than 10 lines or so, or if you can't
upload files with FTP or Microsoft networking, this is likely your problem.
Downloads (from the net to your PC) are not affected. This assumes that you
can upload files and send one-line messages fine; if not, you have a more
fundamental problem. If the technical and political details don't interest
you, skip them.
In late November, Microsoft finally documented this known problem in
Knowledge Base Article Q138025. However, they got it wrong, because the
Usenet article that Microsoft evidently copied,
<199509242223.PAA04539@Networking.Stanford.EDU>, was unclear (my fault). In
late December or early January, after reading this FAQ repeatedly through
the tide and jericho proxy servers, Microsoft removed this article and
every other mention of the PathMTU problem from the Knowledge Base.
Apparently it's just to embarrassing to leave documented. I would
appreciate it if Microsoft would please mail me when they have restored and
corrected the KB article, so that I can remove this paragraph from the FAQ.
Anyway, the problem, as originally diagnosed in article
<443n5c$ff9@aix1.segi.ulg.ac.be> by Andri Pirard pirard@vm1.ulg.ac.be, is
that Microsoft does MTU path discovery according to RFC 1191 (written in
1990 by folks from DEC and Stanford University), but many routers don't.
Since Microsoft jumped on the TCP/IP bandwagon so late, they apparently
don't understand that a standard only drafted in 1990 is an infant not
likely to be adopted Internet-wide.
To fix this problem, run RegEdit.EXE and open it to the following key:
Hkey_Local_Machine\System\CurrentControlSet\Services\VxD\MSTCP
Create the following binary variable with a value of 1:
PMTUBlackHoleDetect = 0 or 1
This should always fix the problem, unless there's a bug in their code, and
we know that couldn't happen. If this doesn't solve the problem, create
this variable in the same place:
PMTUDiscovery = 0 or 1
Now, this is where I believe Microsoft gets it wrong. Knowledge Base
Article Q138025 says to create this with a binary value of 1. This does
nothing. You really want to create it with a value of 0.
Setting MTU to some ridiculously low value is another effective way to fix
the problem, but it hurts performance -- except over dialup, where an MTU
of 576 or so might be a good idea anyway, especially if you have a cheap
modem whose buffering doesn't work well.
All other TCP/IP stacks available for DOS and Windows fragment properly
according to existing Internet standards. You'll only see this problem with
the stack that Microsoft includes "free."
--------------------------
Content-Description: C.11. What good commercial TCP/IP packages are available for Windows 95?
Date: Fri, 29 Dec 95 17:20:00 -0800
From: Rich Graves
You should probably just refer to Rawn Shah's excellent PC-Mac TCP/IP & NFS
FAQ, http://www.rtd.com/pcnfsfaq/faq.html and in comp.answers. It's
somewhat dated and has no Win95-specific information at this time, but it's
got a lot of good stuff, which I see no need to reproduce here. Some
Win95-specific addenda follow.
TGV (www.tgv.com), email sales@tgv.com (TGV stood for Two Guys and a Vax
many years ago before they got successful and went legit), is now shipping
MultiNet 1.2. Nice clients for Telnet, FTP, News, and WWW, plus NFS, are
included. However, according to John Casullo , though,
the current version of the TGV TCP/IP stack itself is not compatible with
Win95 -- it only runs on Windows 3.x. Their advertising is very deceiving
on this point. Some response from TGV would be nice.
Core Systems, http://www.win.net/~core/, email lvuong@cores.com, has
announced and is now shipping INTERNET-CONNECT for Windows 95. In addition
to the features of Win95's stack, it supports BootP and includes better
telnet and FTP clients. It does not support NetBIOS over TCP/IP, so you
can't use Windows file/print sharing over this protocol. Demos are
available. Be aware that Core appears to be a one-man virtual company...
FTP Software is now (started December 5?) shipping OnNet32, a stack and
applications suite. Win95 Logo certification (for what it's worth), NFS
client. Does support NetBIOS over TCP/IP.
--------------------------
Content-Description: C.12. I can't get PC/NFS working under Windows 95.
Date: Thu, 28 Dec 95 10:15:00 -0800
From: Rich Graves
At the polite request of Jody Jackson
"Usually." Trumpet will, and it's significantly faster than Win95's
SLIP/PPP support. On the downside, TCP/IP stacks designed for Windows 3.x,
even those based on 32-bit VxDs, will only support 16-bit TCP/IP clients.
So you can't run 32-bit Netscape or Microsoft Exchange. For Win95
instructions and the latest information on the 32-bit Trumpet beta, see the
Trumpet FAQ, http://www.trumpet.com.au/wsk/faq/wskfaq.htm.
There is also the issue that you must have exactly one WINSOCK.DLL in your
PATH at a time. Rename them or shuffle them around while experimenting.
And there's the issue of Microsoft disabling third-party WinSocks. It was
only designed to do this at installation time, but it actually does this on
whim. If you are using a non-Microsoft winsock.dll, and find that your
winsock.dll disappears or gets renamed at random, or if some applications
call the wrong winsock.dll, the best thing to do, contrary to Microsoft's
rear-end-covering advice, is to put your preferred winsock.dll into
c:\windows and to set its read-only attribute with Win95's Properties
dialog or the DOS attrib +r command.
--------------------------
Content-Description: C.14. I'm using some 16-bit TCP/IP stack like Trumpet and 32-bit apps like Netscape and Exchange don't work.
Date: Wed, 27 Dec 1995 15:44:00 -0800
From: Rich Graves
That's right, they don't. You need to "upgrade" to Windows 95's included
32-bit TCP/IP, or one of the competitive commercial stacks, section C.11.
For instructions, see A.3., related resources. If you use a modem, the
Microsoft/Shiva package will be slower. Note that the new 32-bit shim for
Trumpet WinSock (currently in open beta testing) will allow you to run
32-bit applications.
--------------------------
Content-Description: C.15. Assorted DNS resolution problems.
Date: Thu, 07 Dec 95 10:15:00 -0800
From: Rich Graves
At this time, I believe C.4. and various configuration follies explain away
most of the following. I am still puzzled by Juha Noro ,
the guy in Finland with the "personal" problem, i.e., he cannot resolve any
hostname that begins with "personal."
I also saw this weird thing once where the NetBIOS-over-TCP/IP client
(only) was spuriously appending the literal string "???" to DNS lookups for
some hostnames (only). I got packet traces. But it went away mysteriously.
If anyone else sees something similar, tell me.
I saved the old unresolved (if you'll pardon the pun) problems at
http://www-leland.stanford.edu/~llurch/win95netbugs/DNS-Probs.txt and in
some other files in that directory. Also see the email list, section A.2.
--------------------------
Content-Description: C.16. What arcane TCP/IP parameters can be configured?
Date: Mon, 18 Sep 1995 04:44:07 +0000
From: Daniel M
Message-Id: <19950918044454.00974ece.in@toast.dynamsol.com>
Open the Registry to:
Hkey_Local_Machine\System\CurrentControlSet\Services\VxD\MSTCP
BroadcastAddress = broadcast address in hexadecimal
Specifies the address to use for NetBIOS name query broadcasts. The default
is based on the IP address and the subnet mask.
BcastNameQueryCount = integer
Specifies the number of times the system will retry NetBIOS name query
broadcasts. The default is 3.
BcastQueryTimeout = milliseconds
Specifies the period of time the system will wait before timing out
broadcast name queries. The minimum value is 100. The default is 750.
BSDUrgent = 0 or 1
If this value is 1, specifies that Microsoft TCP/IP is to treat urgent data
the way some UNIX systems do (with a maximum of 1 byte of urgent data, for
example). If this value is 0, it specifies that the stack is to handle
urgent data as specified by RFC 1122. The
default is 1.
CacheTimeout = milliseconds
Specifies how long NetBIOS names are cached. The minimum is 60000
milliseconds (1 minute). The default is 360000 milliseconds (6 minutes).
DeadGWDetect = 0 or 1
Specifies whether Microsoft TCP/IP will use another gateway if the current
default gateway seems to be down. The default is 1.
DefaultRcvWindow = 16-bit number
Specifies the default receive window advertised by TCP. The default is
8192.
DefaultTOS = 8-bit number
Specifies the default type of service (TOS) for IP packets initiated by
Microsoft TCP/IP. The default is 0.
DefaultTTL = 8-bit number
Specifies the default time to live (TTL) for IP packets from Microsoft
TCP/IP. The default is 32.
DnsServerPort = port
Specifies which DNS server port to send queries to when resolving a name
using DNS. The default is 53.
EnableProxy = 0 or 1
If this value is 1, specifies that this computer is a WINS proxy agent. The
default is 0.
EnableRouting = 0 or 1
Specifies whether to enable static routing. Microsoft TCP/IP does not
supply a routing protocol, so all route table entries must be entered using
the route command. The default is 0.
IGMPLevel = 0, 1, or 2
Specifies the level of support allowed for IP multicast, corresponding to
the levels in RFC 1112. The default is 2.
InitialRefreshT.O. = milliseconds
Specifies the interval over which to contact WINS to refresh the name. The
minimum is 16 minutes, and the maximum is approximately 50 days
(0xFFFFFFFF). The default is 960000 milliseconds (16 minutes).
KeepAliveTime = 32-bit number
Specifies the connection idle time in milliseconds before TCP will begin
sending keepalives, if keepalives are enabled on a connection. The default
is 2 hours (7200000).
KeepAliveInterval = 32-bit number
Specifies the time in milliseconds between retransmissions of keepalives,
once the KeepAliveTime has expired. Once KeepAliveTime has expired,
keepalives are sent every KeepAliveInterval milliseconds until a response
is received, up to a maximum of MaxDat a Retries before the connection is
aborted. The default is 1 second (1000).
LmhostsTimeout = milliseconds
Specifies the period of time the system will wait before timing out when
seeking LMHOSTS for name resolution. The minimum value is 1000 (1 second).
The default is 10000 (10 seconds).
MaxConnections = 32-bit number
Specifies the maximum number of concurrent connections. The default is 100.
MaxConnectRetries = 32-bit number
Specifies the number of times a connection attempt (SYN) will be
retransmitted before giving up. The initial retransmission timeout is 3
seconds, and it is doubled each time up to a maximum of 2 minutes. The
default is 3.
MaxDataRetries = 32-bit number
Specifies the maximum number of times a segment carrying data or an FIN
will be retransmitted before the connection is aborted. The retransmission
timeout itself is adaptive and will vary according to link conditions. The
default is 5.
NameServerPort = port
Specifies the UDP port on the name server to which to send name queries or
registrations. The default is 137.
NameSrvQueryCount = integer
Specifies the number of times the system will try to contact the WINS
server for NetBIOS name resolution. The default is 3.
NameSrvQueryTimeout = milliseconds
Specifies how long the system waits before timing out a name server query.
The minimum is 100. The default is 750.
NameTableSize = integer
Specifies the maximum number of names in the NetBIOS name table. The
minimum allowable value is 1 and the maximum is 255. The default is 17.
NodeType = 1, 2, 4, or 8
Specifies the mode of NetBIOS name resolution used by NetBIOS over TCP/IP,
where 1 = b-node, 2 = p-node, 4 = m-node, and 8 = h-node. This value can be
configured using DHCP. The default is 1 (b-node), if no value is specified;
if WINS servers are specified and NodeType is not, then the default is 8
(h-node).
PMTUBlackHoleDetect = 0 or 1
Specifies whether the stack will attempt to detect Maximum Transmission
Unit (MTU) routers that do not send back ICMP fragmentation-needed
messages. Setting this parameter when it is not needed can cause
performance degradation. The default is 0.
PMTUDiscovery = 0 or 1
Specifies whether Microsoft TCP/IP will attempt to do path MTU discovery as
specified in RFC 1191. The default is 1.
RandomAdapter = 0 or 1
For a computer with multiple network adapters, specifies whether to respond
with an IP address selected randomly from the set of addresses on the
computer or whether to return the IP address of the adapter that the
request came in upon. The default is 0 ( not random; that is, return the
address of the adapter that the request came in on).
RoutingBufSize = 32-bit number
Specifies the total amount of buffer space to allocate for routing packets.
This parameter is ignored if EnableRouting=0. The default is 73216.
RoutingPackets = 32-bit number
Specifies the maximum number of packets that can be routed simultaneously.
This parameter is ignored if EnableRouting=0. The default is 50.
SessionKeepAlive = milliseconds
Specifies how often to send session keepalive packets on active sessions.
The minimum is 60 seconds. The default is 3600 seconds (1 hour).
SessionTableSize = integer
Specifies the maximum number of sessions in the NetBIOS session table. The
minimum allowable value is 1 and the maximum is 255. The default is 255.
SingleResponse = 0 or 1
For a computer with multiple network adapters, specifies whether to send
all IP addresses on a name query request from WINS. If this value is 1, the
system will send one address in a name query response; if 0, it will return
all the addresses of its adapters. The default is 0.
Size/Small/Medium/Large = 1, 2, or 3
Specifies how many buffers of various types to preallocate and the maximum
that can be allocated, where 1 = small, 2 = medium, and 3 = large. The
default is 1; the default is 3 if the WINS proxy is enabled.
--------------------------
Content-Description: C.17. Nobody seems to be able to get routing to work.
Date: Thu, 28 Dec 95 11:44:00 -0800
From: Vadim
Message-Id: <199509232144.XAA03624@mail.netvision.net.il>
It's a common belief that windows 95 can't do IP forwarding (There were
several postings about it in comp.os.ms-windows.win95) and you have to use
NT to do it.
Win95 resource kit help file contains the following information:
[----]
Hkey_Local_Machine\System\CurrentControlSet\Services\VxD\MSTCP\EnableRouting = 0
or 1
Specifies whether to enable static routing. Microsoft TCP/IP does not supply
a routing protocol, so all route table entries must be entered using the
route command. The default is 0.
[----]
I tried that on two machines (486DX2 and PENTIUM-75, both with ethernet card
and a RAS driver installed) and on both got a total system crash on boot (I
guess when loading vip.386).
Interesting enough, this whole routing issue has never been documented by
microsoft.
So, anybody "been there, done that" ?
Is it a bug, half-implemented feature or just wrong configuration ?
[Keith Davidson and Roger Pfister later reported that multiple TCP/IP
interfaces only seem to work if each interface is on a different Class A
net (because Win95 always creates a bogus route to 255.0.0.0 -- you can see
it with ROUTE.EXE or the SNMP Agent). There's also a typo in the options
screen -- "if" for "it." Very professional.]
--------------------------
Content-Description: C.18. Sockets get "eaten up" and WinSmtp dies.
Date: Fri, 29 Dec 95 20:00:00 -0800
From: Jack De Winter
Has anyone else seen a problem where continuous access to a server
application will cause that application to run out of sockets or buffers
after a long time of continuous use?
Using NT, I can run my WinSmtp mail daemon (if you want details, send me a
quick message) for weeks with no problems. But after 12 hours under the
same conditions under win95 and its stacks (winsmtp as server and Exchange
as a client, checking every 2-5 minutes), it refuses to connect up any
more.
any ideas?
[Update 9/25/95: Eric Thomas confirms the problem
on his machine, but says that the 16-bit version of WinSMTP works fine.]>
[Update 9/30/95: Jack says this only happens with SLIP. WinSMTP seems to
work fine over Ethernet and PPP. Also, the 16-bit version of WinSMTP
works.]
[Update 10/20/95: Jack says, and I sort of understand:]
okay... the following is what I am doing, in asynchronous mode:
case 1: client closes connection
- receive FD_CLOSE
- set to receive no more information
- make sure information currently in layer is retrieved using 'recv'
- send a lingering close (l_onoff set to FALSE and l_time set to 0)
- delete internal node when close succeeds and doesn't block
case 2: we initiate close
- set so we don't receive any more data
- lingering close, see above
- delete internal node
Just to reiterate, we are using Async mode and notifies (will be doing a
port to non-async in a week or two), I believe we might have the Debug
mode set on the protocol, and that is about it.
Symptoms:
- using NT's or almost any win16 stack, no problems
- using win95 stack, runs out of buffer space or reports that it cannot
connect after about 80 sessions
[A message from Jack to his user group concerning this problem is saved at
http://www-leland.stanford.edu/~llurch/win95netbugs/jackdw-closes.txt.]
[This bug has affected scores of shareware and commercial programs, but to date
only Jack has talked about it on the record.]
--------------------------
Content-Description: C.19. Can I disable DNS for WINS resolution?
Date: Tue, 10 Oct 95 23:30:00 -0800
From: Rich Graves
WFW and NT have an "enable DNS for WINS resolution" checkbox that is turned
off by default. In Win95 this feature is on by default, and there is no
check box to turn it off. It turns out that this is what the "EnableDNS"
switch in the Registry is for. If you turn it off, DNS is still enabled; it
just isn't used for WINS resolution. This is part of Win95's redefinition
of "intuitive." From article Q137368 in the Microsoft Knowledge Base:
How to disable NetBIOS name resolution on a domain-name system (DNS) while
retaining other DNS functionality.
To disable NetBIOS name resolution on a DNS server, change the string value
EnableDNS
in the registry key
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\MSTCP
from 1 to 0.
--------------------------
Content-Description: C.20. TCP/IP Requires Ethernet_II Frame Type for ODI Driver.
Date: Tue, 10 Oct 95 23:30:00 -0800
From: Rich Graves
If you're using ODI drivers (usually for NetWare or really obscure network
cards), you need to manually add the ETHERNET_II frame type to NET.CFG, or
Microsoft TCP/IP won't work. This is just a particular case of general
problem E.4. See article Q129726 in the Microsoft Knowledge Base:
--------------------------
Content-Description: C.21. Does Win95 support IP Multicast?
Date: Wed, 27 Oct 95 15:52:00 -0800
From: Rich Graves
According to Microsoft, yes; there is a Registry switch for determining the
level of support. However, at this time, I know of no applications that
take advantage of Win95's claimed multicast support.
According to Microsoft's Dave MacDonald, Microsoft's IP multicast support
(which is supposed to be the same for Win95 and WinNT) is detailed in
ftp://ftp.microsoft.com/bussys/winnt/winnt-docs/papers/tcpipimp.doc.
Bob Quinn has posted some other relevant technical information at
http://www.sockets.com/ch16.htm.
--------------------------
Content-Description: C.22. How to obtain DNS hostname via DHCP?
Date: Wed, 27 Oct 95 15:56:00 -0800
From: Rich Graves
Thanks to Rex Wheeler for posing this question.
What you have to do is configure TCP/IP properties to "Disable DNS." This
does not actually disable DNS; it merely tells Win95 to use the hostname,
DNS server(s), and domain returned by the DHCP response. Intuitive, huh?
This little bug has caused many a problem for people who innocently put the
name of a server they want to reach into the DNS hostname field. Because
Win95 thinks that it is that server, the real server becomes unreachable.
Also, the "Enable DNS" Registry switch is completely irrelevant; see
question C.19.
--------------------------
Content-Description: C.23. How to prevent anyone from accessing my entire hard drive?
Date: Thu, 07 Dec 95 10:15:00 -0800
From: Rich Graves
If you have a non-English-language version of Windows 95, you can't, unless
you disable peer sharing and remote administration.
If you have the English-language version, get the patches from
http://www.windows.microsoft.com/software/w95fpup.htm. Microsoft's
clarification is incorrect (for starters, they didn't discover these
problems; we know who pointed them out to them), but the patches appear to
fix the problem.
These same problems have always affected Windows for Workgroups. Despite
repeated warnings over the last nine months, Microsoft does not consider
these problems important enough to mention in the TCP32B (Wolverine)
distribution. The patch for WFW is called Wfwvsrvr.exe and is available on
ftp.microsoft.com, CompuServe, and on the Web at
http://www.microsoft.com:80/KB/PEROPSYS/windows/Q136418.htm.
--------------------------
Content-Description: C.24. How can Win95 and UNIX computers share files and printers?
Date: Sat, 30 Dec 95 10:00:00 -0800
From: Rich Graves
Microsoft chose not to make it easy for Win95 and UNIX machines to
interoperate, because Microsoft sells Windows NT. But as Spock instructs
us, there are always alternatives.
Freeware Samba file and print client and server for UNIX
The easiest way to get Windows (any version) to share files and
printers with UNIX (in either direction) is with Samba,
http://lake.canberra.edu.au/pub/samba/, a SMB implementation for UNIX
that allows your machine to masquerade as the NT Server that Microsoft
wants you to buy. Of course you need to be (good friends with) the
system administrator, but Samba is quite easy, reliable, and free. The
main thing to worry about is Windows' "password caching feature,"
which by default would sort of compromise the security of your UNIX
machines. See question E.27. for instructions on turning "password
caching" off.
Shareware for printing from Windows to UNIX
WSLPRS is the standard LPR (Internet standard client for printing to
UNIX and other machines) implementation for Windows. A recent version
should be available on all the PC software archives, for example,
ftp://mirrors.aol.com/pub/cica/pc/win3/winsock/.
Shareware for printing from UNIX to Windows
David L. Brooks , http://brooksnet.com/, offers a
shareware LPD (Internet standard print server) implementation for
Windows.
Pay-through-the-nose-ware
See C.11. for a few commercial packages that include NFS (standard for
file and print sharing) and LPR/LPD (standard for printing).
--------------------------
Content-Description: C.25. Is there any way to run Win95 from a UNIX server running Samba?
Date: Wed, 27 Dec 95 23:00:00 -0800
From: Rich Graves
In a word, no. Samba runs SMB over TCP/IP, which is a 32-bit-only protocol.
You are able to run Win95 off a NetWare or SMB (LAN Manager, OS/2, NT)
server because IPX/SPX and NetBEUI (only) are active in 16-bit DOS mode as
well. But TCP/IP, no. Well, in theory you could load a 16-bit TCP/IP stack
that supports SMB over TCP/IP, but then you wouldn't be able to run Win95's
built-in file sharing or run any 32-bit WinSock apps, and that sort of
defeats the purpose of running Win95.
--------------------------
Content-Description: C.26. How can I prioritize multiple default routers?
Date: Wed, 1 Nov 1995 15:08:53 -0500
From: PLINSPO1.MSCHMITT@eds.com
The Resource Kit (Network Technical Discussion - TCP/IP Protocol -
Configuring TCP/IP Settings Manually - Step 7) says that "Gateway addresses
can be prioritized by dragging the IP address in the list of installed
gateways." This is not true.
Does anybody have a method that works?
--------------------------
Content-Description: C.27. Why won't the Plus Pack install properly on a machine with Internet Explorer installed?
Date: Wed, 1 Nov 1995 15:08:53 -0500
From: Mike Johnston (by way of Bob Verrinder)
Message-ID: <47958p$mq6@maureen.teleport.com>
I did find the answer and it seems that if you loaded Explorer previously it
will not load through Plus because it sees that it has already been loaded
from reading the registry during setup. To rectify the problem do the
following:
1) Start up REGEDIT.EXE - The registry editor
2) Go to key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer
3) You will should see two lines displayed in the right pane of
regedit.
(Default) (value not set)
IVer "xxx"
4) delete the IVer key by right clicking on the word IVer and
selecting delete
5) Close up regedit. Reinstall Plus! (or just the Jumpstart Kit if
that's all you need).
For good measure you might as well reboot before you do that.
--------------------------
Content-Description: C.28. What do I do if Win95 won't wait long enough for my DHCP server to assign an address?
Date: Mon, 6 Nov 1995 10:55:17 -0600
From: David Devereaux-Weber
Message-ID: <199511061655.KAA73144@audumla.students.wisc.edu>
[Complain, I guess, until Microsoft fixes this.]
We have had difficulty with Microsoft's implementation of DHCP in WIN95.
the DHCP client is supposed to wait a reasonable period of time for the
server to check an address before it is given to the client. Microsoft's
client doesn't wait very long - it bails out early and reports no response.
The people at Sun hacked their client software for us to temporarily work
around the problem. Unfortunately, trying to get Microsoft to understand
and support the official protocol has been unsuccessful to date.
We call our Internet software collection WiscWorld. We don't recommend
using WiscWorld with WIN95, but we have a Web page with instructions on
doing it if you really want to:
http://axle.adp.wisc.edu/NST/wiscwrld/ww95/ww95.html
--------------------------
Content-Description: C.29. Why does my winsock.dll disappear or get renamed to winsock.old?
Date: Fri, 29 Dec 1995 21:18:00 -0800
From: Rich Graves
If you're using a non-Microsoft winsock.dll, then Win95 is working as
designed. See http://www.windows.microsoft.com/pr/clarifications.htm or
certain papers filed with the US Department of Justice, Anti-Trust
Division.
If you're using Microsoft's winsock.dll, as many people with this problem
are, then this is a bug.
In any case, the solution is to make sure that the only copy of winsock.dll
is in your %WINDIR% (i.e., C:\WINDOWS), and mark is read-only with Explorer
Properties or attrib +r.
Microsoft's claim that non-Microsoft DLLs don't belong in the Windows
directory is hogwash.
--------------------------
Content-Description: C.30. Bug in NetBIOS name resolution stops LMHOSTS from working.
Date: Wed, 20 Dec 1995 07:57:30 -0800
From: Rich Graves
A Microsoft Knowledge Base Article had said that LMHOSTS doesn't work when
DNS is enabled. This is incorrect.
Jeff Strain appears to have found the real
problem:
If you are running both IPX and TCP transports, and are using MS Network
client and client for Novell networks, *and* have unbound MS Net from the
IPX protocol settings, then LMHOSTS resolution will not work.
The workaround is to rebind MS Net over IPX, even if you do not use IPX for
MS Network. This will slow down login a bit, but your LMHOSTS resolution
should work.
Another workaround is to put the hosts to which you want to connect into a
HOSTS file rather than LMHOSTS.
--------------------------
Rich Graves , friends, and enemies.
Copyright 1996 Rich Graves, Stanford University, and Friends.
Redistribution and mirroring are encouraged provided the source is credited
From owner-win95netbugs@lists.stanford.edu Mon Jan 22 11:55:22 EST 1996
Article: 991 of comp.os.ms-windows.networking.win95
Path: quantum!revcan!cunews!nott!torn!howland.reston.ans.net!newsfeed.internetmci.com!nntp-hub2.barrnet.net!news.Stanford.EDU!not-for-mail
From: llurch@Networking.Stanford.EDU (Richard Charles Graves)
Newsgroups: comp.os.ms-windows.networking.misc,comp.os.ms-windows.networking.windows,comp.os.ms-windows.win95.setup,comp.os.ms-windows.win95.misc,comp.os.ms-windows.networking.win95,comp.os.ms-windows.setup.win95,alt.os.windows95.crash.crash.crash,uk.comp.os.win95,comp.answers,news.answers
Subject: [*] Windows 95 Networking FAQ, 4/7
Followup-To: comp.os.ms-windows.networking.win95
Date: 18 Jan 1996 22:08:33 -0800
Organization: Stanford University
Lines: 674
Approved: news-answers-request@MIT.EDU
Expires: 16 Feb 1996 12:34:56 GMT
Message-ID:
Reply-To: owner-win95netbugs@lists.stanford.edu
NNTP-Posting-Host: networking.stanford.edu
Mime-Version: 1.0
Content-Type: MULTIPART/DIGEST; BOUNDARY="----------------------------"
Summary: Windows 95 Networking FAQ
Keywords: Section D, Dialup Networking
X-PGP-Key: 0xCCE7B49D, 1024 bits, for llurch@networking.stanford.edu
X-PGP-Print: ED CA 67 98 AD 2A 62 2A 01 17 78 A8 33 F2 6D E0
Xref: quantum comp.os.ms-windows.networking.misc:10407 comp.os.ms-windows.networking.windows:12565 comp.os.ms-windows.win95.setup:46476 comp.os.ms-windows.win95.misc:93975 comp.os.ms-windows.networking.win95:991 comp.os.ms-windows.setup.win95:1094 comp.answers:14049 news.answers:53504
Archive-name: ms-windows/win95netbugs/part4
Posting-Frequency: twice monthly
FAQ-Maintainer: Rich Graves
Last-Change: 18 Jan 1996 by Rich Graves
Version: 4.00.963
URL: http://www-leland.stanford.edu/~llurch/win95netbugs/faq.html
--------------------------
Content-Description: Welcome and Index
This FAQ concerns problems you might encounter with Win95's networking
features after you have set everything up according to the directions, such
as they are. This is section D, Dialup Networking.
D. Dialup Networking (SLIP/PPP) Issues
1. Nonstandard PPP implementation causes problems with BSDI and other
servers.
2. Degraded SLIP/PPP performance versus Trumpet.
3. Killed applications/disconnects cause total system freezes.
4. Minor changes to TCP/IP or modem parameters cause dialup properties to
reset to defaults without warning.
5. Win95 creates fictional COM ports on some plug-and-pray machines.
6. DSCRIPT might exit before getting all dynamically assigned
information.
7. Modem on COM4 incompatible with S3 video cards.
8. PPP compression won't work on at least some Xyplex terminal server
configs.
9. What are some tips for better dialin performance?
10. IPX (NetWare) compression bug.
11. Can't log on to Sun PPP server, or cause Sun PPP server to crash.
12. What's the difference between the Plus Pack and normal dialup
scripters?
13. Where is the SLIP and scripting support?
14. Why do I get "host unreachable" on most remote hosts, though I can get
to my ISP's servers?
15. If my connection drops, why don't my TCP sessions reconnect?
16. How do I change my modem init string?
17. Will Twinsock work in Win95?
18. Will TIA work with Win95?
19. How do you start dialup networking from the command line?
20. Why does Win95 fail to negotiate with a Xylogics TIP if NetBEUI is
enabled?
21. How can multiple machines share one dialup TCP/IP connection?
22. How do I avoid losing all my LAN (i.e., NetWare) connections when I
dial up the Internet?
23. Bug in CHAP (password) negotiation.
24. How can I use SLIP/PPP through a direct connection (i.e., no modem)?
25. Modem locks up with an SMC 666 UART.
--------------------------
Content-Description: D.1. Nonstandard PPP implementation causes problems with BSDI and other servers.
Date: Wed, 27 Dec 95 16:03:00 -0800
From: Rich Graves
Thanks to Richard Ryan for calling this set of
problems to our attention. For more information on this problem, see the
searchable bsdi-users archive at http://www.nexial.nl/cgi-bin/bsdi.
Microsoft's RFC for their "extensions" to PPP, which were rejected by the
Internet Engineering Task Force (IETF), is at
ftp://ftp.microsoft.com/developr/rfc/ipcpexts.txt. Note 8-character
truncation to developr! Limited and incomplete information on Microsoft's
nonstandard CHAP implementation is available in that directory.
There has been some discussion of this on the comp.protocols.ppp newsgroup,
and here's an unofficial discussion of the problem from BSDI:
Date: Sat, 26 Aug 1995 11:46:58 -0500
Message-Id: <199508261646.LAA05931@krystal.com>
From: Paul Borman
Subject: Re: Pesky IPCP Messages
> Now that Windows 95 is beginning to appear, I am beginning to get more
> of these messages with the BSDI 2.0 ppp implementation. No real
> problems but a real drag on the messages log.
>
> ppp3: unknown IPCP option received (129)
> ppp3: unknown IPCP option received (130)
> ppp3: unknown IPCP option received (131)
> ppp3: unknown IPCP option received (132)
Microsoft proposed some extensions to IPCP to negotiate the DNS server
and the NetBUI server. The IETF rejected them as this was the wrong
level to do this. Microsoft decided to ignore the IETF and implement
them anyhow. Microsoft should provide a way to not use them (since
they are totally non-standard and are only supported by Microsoft
clients). Users of Microsoft networking products would need to
contact Microsoft to determine how to do this. [Rich's note: in fact
there is no way to turn them off, and I believe Paul knew it.]
This note is meant to be an explanation of what is happening and should
not be interpreted in any way as an official statement by BSDI on The
Microsoft IPCP Options.
-Paul Borman
prb@bsdi.com
[Update December 27th: there have been some posts on Usenet that
Microsoft's IPCP documentation is also wrong about what Win95 actually
does. See comp.protocols.ppp and a particularly informative article I've
saved at http://www-leland.stanford.edu/~llurch/win95netbugs/ipcp-huh.txt.]
--------------------------
Content-Description: D.2. Degraded SLIP/PPP performance versus Trumpet.
Date: Fri, 29 Dec 95 16:06:00 -0800
From: Rich Graves
There have been a heck of a lot of posts in comp.os.ms-windows.win95.setup
complaining that file transfers using Win95's native SLIP/PPP are slower
than they were using Trumpet WinSock. There have been lots of posts that
say performance is OK, but I don't recall any claiming that performance has
improved.
The problem is probably rooted in the fact that when you use Win95's
built-in SLIP/PPP, you're really using two protocol stacks, a TCP/IP stack
built by Microsoft, and a remote access stack developed by Shiva
Corporation, so you've got extra overhead to deal with.
aladin@scruznet.com (Leo Szumel) claims that he got better performance
turning IP header compression off, which makes no sense, but you can try
it.
Here are some general tips applicable to any dialin protocol:
Message-Id: <199509171252.IAA01886@panix.com>
Date: Sun, 17 Sep 95 08:51:33 -0400
From: richard
To: llurch@networking.stanford.edu
Subject: faq: dialup speed
Two things improved speed for me:
1) Turn off software compression (DialUpNetworking->Properties
->ServerType->EnableSoftwareCompression)
2) Turn off error correction for my modem - at AT&Q6 to the
init string. this may be a modem interoperability problem
of mine, rather than a general win95 issue.
3) A few people have said that fiddling with mtu, etc. settings
does not help. I haven't tried.
[See also the Windows Comm FAQ, http://www.malch.com/comfaq.html. Please
see also D.9.]
--------------------------
Content-Description: D.3. Killed applications/disconnects cause total system freezes.
Date: Tue, 12 Sep 1995 01:55:42 GMT
From: jewald@primenet.com (Jim Ewald)
Newsgroups: comp.os.ms-windows.win95.misc,comp.os.ms-windows.win95.setup
Message-Id: <432pb4$n3@nnrp3.primenet.com>
[There have been several followup posts in the Win95 newsgroups confirming
that the problem is not specific to any particular client software or ISP.]
Some of us in a local news group have discovered a nasty problem that
causes Win95 to lock up solid. Does anyone have a fix for this or can
anyone at least let MS know about it? The tech support lines are very
useless right now. An excerpt from the conversation follows. Thanks!
- Jim Ewald
MSG 1
----------
bigrex@primenet (Bob Nixon) wrote:
>I'm using Win 95 to connect up to Primenet and I keep encountering an
>infrequent but ANNOYING problem. Everything appears to work ok and
>every once in awhile(1 out of 25 times) when I click on disconnect, my
>computer freezes. The clock stops, the cursor won't move and the only
>remedy is to power off. At the time I click disconnect I have no other
>programs running...just the TCP/IP dial-up. I was wondering if anyone
>else is having this same problem?
MSG 2
----------
budster@primenet.com says...
>This has happened to me too but, it always happens after I force closure of
>some winsock app(example CTRL-ALT-DEl of Telnet, WS-FTP32 or one of the
>newsreaders that's slow to or not responding). I think it leaves a bad code
>somewhere in the system and causes a lockup when you close Win95's winsock.
MSG 3
----------
Claudio@primenet.com writes:
>This happens to me whenever I'm disconnecting and I happen to move the
>mouse at the same moment the modem is hanging up. My computer freezes,
>dnd there's nothing you can do except to turn the machine off and on
>again. I knew of this bug a long time ago, and I thought It was that I
>had something not configured right, but for what I can see here, it
>happens to other people too. By the way, I'm still using a beta
>version of win95, build 950r2. Are you guys using the commercial
>version?
Another person with this problem is Bob Werth .
--------------------------
Content-Description: D.4. Minor changes to TCP/IP or modem parameters cause dialup properties to reset to defaults without warning.
Date: Wed, 27 Dec 95 16:08:00 -0800
From: Neil Moodie
When making network config changes (often small, unimportant, insignificant
etc changes), the properties of the dial-up connection are reset back to
defaults. These defaults include PPP transport, with "server assigned" IP
address and "server assigned" name server address.
This caught me out a few times, as I have a locally assigned name server
address and have had to re-enter this information into the dial-up
connection properties TCP/IP Settings after making minor changes to the
dial-up config. Even configuring a new modem can reset these settings.
This problem is only compounded by the "Internet Setup Wizard" included
with the Plus Pack and the Microsoft Internet Explorer, which adds a third
confusing interface to TCP/IP settings.
--------------------------
Content-Description: D.5. Win95 creates fictional COM ports on some plug-and-pray machines.
Date: 23 Sep 1995 03:28:47 GMT
From: oturn@gulf.net (Oran Turner)
The "phantom" com port seems to be a common problem with PNP motherboards
and internal modems. I have a mouse on COM1 and an internal modem on COM2,
with my physical COM2 turned off in BIOS. This is the problem...in the
"Device Manager" in Windows 95, under "Ports (COM & LPT)", not only are my
standard COM1, COM2 & LPT1 ports listed, but also listed is another entry
labeled only "Communications Port." The settings for this extra entry
correspond to the settings for COM1 (IRQ 4, I/O 03F8-03FF). I simply
disable this extra entry to avoid the conflict the system detects, and
everything seems to work fine.
Probably 90% of the phantom port problems are related to the interaction
between an internal modem, a physical COM port, a PNP system and Windows
95. I've brought the problem to the attention of my motherboard
manufacturer, but they pretty much blew me off. (I've got an Asus
P55TP4XE.)
[Another hardware detection problem that might hit you is that on many
Pentium motherboards, Win95 insists on loading a driver for a nonexistent
bus mouse. Someone posted a technical explanation of how Microsoft made
this mistake, but I lost it.]
--------------------------
Content-Description: D.6. DSCRIPT might exit before getting all dynamically assigned information.
Date: Sat, 23 Sep 1995 00:49:16 GMT
From: peeler@peeler.com
Newsgroups: comp.os.ms-windows.win95.misc
References: <43edr8$rfd@grovel.iafrica.com> <43rofb$50u@sydney1.world.net>
In article nagamati@netcom.com
(Romklau Nagamati) writes:
>John McGhie (jmcghie@world.net) wrote:
>: markdm@iafrica.com (Mark Maunder) wrote:
>:
>: >I am at my wits end. I have been trying to get a 32 bit PPP connection with
>: >win95 for the past 2 weeks and have finally managed to get it to dial in and
>: >log on, but now it looks as though either the DNS is not working or my
>: >applications or just not talking to the win95 Dialup adapter.
(Much Deleted)
I had the same problem and was able to resolve it by putting a delay statement
immediately before the "endproc" line.
It appeared that the script routine was closing off before the server parsed
back the Dynamic Address.
I found a delay of anywhere between 2 and 5 seconds was sufficient.
--------------------------
Content-Description: D.7. Modem on COM4 incompatible with S3 video cards.
Date: 6 Oct 1995 07:43:12 GMT
From: tatosian@plough.enet.dec.com (Dave Tatosian)
If you have an S3-based video card (most 64-bit cards including Number 9
and Diamond), you cannot use COM4 because of a memory base address
conflict.
These cards use port addresses (46E8h, in the case of S3) for 8514/XGA
support, which will be *aliased* to address 2E8h by most COM port address
decoders - which tend to only decode the low order 10 bits of the address
field. Putting a modem on COM4 therefore ends up in conflict with the
graphics card - but it's usually only apparent when the graphics card is
running in a mode other than straight VGA (ie: in DOS, you won't see a
problem, but running in Windows/Win95 in say 800x600, you will).
The solution is to move the modem to some other port address, but of course
you have to avoid conflicts with your other COM ports. If your mouse is on
COM1, and COM2 is free, you should use COM2. But if you want to keep your
COM2 available for a serial port, you can't use the "standard" COM3 setup
for the modem, because COM3 normally uses IRQ4 (which will conflict with
COM1).
But you *can* set the modem up to use COM3 with *IRQ5* (most modems will
support this configuration). That way, you won't conflict with COM1's use
of IRQ4. If IRQ5 is already being used by a sound card, switch the sound
card to use IRQ7 instead.
After making the required changes to the modem (and sound card if required)
you'll have to make sure that Win95 does the right thing on startup. It
should detect the new configuration and make the appropriate changes to the
properties and resource allocations, but you should check under Control
Panel-System-Device Manager to be sure. If needed you might have to set
some of the resources manually.
Microsoft has also finally woken up to this problem, and has documented it
in Knowledge Base article Q127138,
http://www.microsoft.com:80/KB/PEROPSYS/win95/Q127138.htm.
--------------------------
Content-Description: D.8. PPP compression won't work on at least some Xyplex terminal server configs.
Date: Wed, 27 Dec 95 17:31:00 -0800
From: Rich Graves
waung@mprgate.mpr.ca (William Waung) and a dozen others report that they
can not establish a PPP connection to Xyplex, IOLAN, older Teleport, and
other terminal servers unless they disable IP compression. More
investigation is needed. You can see William's message and followups on the
win95netbugs list archive, gopher://quixote.stanford.edu/1m/win95netbugs,
under the subject "Internet connection failure: no network protocol
compatibility." Or look for his original newsgroup post to
comp.os.ms-windows.win95.* on the www.dejanews.com searchable USENET
archive. To help you recognize the symptoms, the error entries in his PPP
log referred to problems with CCP (protocol 80fd). If you also run into
problems with PPP-level compression (not modem-level compression), please
mail win95netbugs-owner@lists.stanford.edu.
--------------------------
Content-Description: D.9. What are some tips for better dialin performance?
Date: Wed, 27 Dec 1995 17:33:00 -0800
From: neal@postoffice.ptd.net (NR Haslam)
Newsgroups: comp.os.ms-windows.win95.misc
Here is some information that may help someone experiencing slower
than expected downloads. For the good of the order:
Start by ensuring that your machine is not doing extra work by
compressing data unnecessarily.
Double click on My Computer / Dial Up Networking
Right Click on Prolog Icon (or whatever you called it on your
machine)
Click on Properties / Server Type
Remove all checks from boxes except for the TCP/IP box.
Next, let's be sure that your modem is answering your computer
correctly:
Click Start / Settings / Control Panel
Double click on Modem
Click on Diagnostics
Click Com2 (or what ever port your modem is assigned)
Click More Info
Mine says:
Port COM2
Int 3
Addr 2F8
UART NS 16550AN
Highest Speed 115K Baud
Another trick you might try is to change your modem driver to the
Supra 288i. See if that makes any difference compared to the Hayes
288 settings. Don't know how you feel about those "standard"
selections, but I am not a fan of default settings.
[Also see C.1. for information on setting MTU and RWIN.]
--------------------------
Content-Description: D.10. IPX (NetWare) compression bug.
Date: Wed, 27 Dec 95 17:35:00 -0800
From: Rich Graves
A highly regarded source at a terminal server vendor told me, and we and
InfoWorld Magazine have verified, that Win95 sends the CIPX length field
backwards. As a result, properly behaved PPP servers will discard the bad
packets, and you get no IPX connectivity. The solution is either to disable
IPX compression on the Win95 client (there's a convenient checkbox for
this), or to disable CIPX length field verification at the PPP server (many
vendors are starting to do this by default because it's usually easier to
accommodate Microsoft's bugs than to get them fixed).
--------------------------
Content-Description: D.11. Can't log on to Sun PPP server, or cause Sun PPP server to crash.
Date: Wed, 27 Dec 95 17:49:00 -0800
From: Rich Graves
There is some controversy over who is at fault here. Since Sun's PPP
client/server works fine with non-Microsoft PPP clients and servers,
fingers tend to point towards Redmond. For some discussion of this issue,
see the Usenet threads saved at
http://www-leland.stanford.edu/~llurch/win95netbugs/ppp/ and the
win95netbugs list archive.
Currently, the fix is to run a third-party PPP server, such as dp. Sun
released a patch for this problem with Win95, but it solves the crashing
problem simply by shutting Win95 clients out.
--------------------------
Content-Description: D.12. What's the difference between the Plus Pack and normal dialup scripters?
Date: Wed, 27 Dec 95 20:07:00 -0800
From: Rich Graves
The dialup scripter that Microsoft sells as part of the Plus! Pack supports
useful features like branching, intelligent retries, and variables. The
dialup networking scripter included with Win95 (see D.13.) only supports
simple linear scripts. Because Microsoft never documented this difference,
some ISPs were distributing scripts that would only work with the Plus!
scripter, and scratching their heads when they didn't work. Don't make this
mistake.
--------------------------
Content-Description: D.13. Where is the SLIP and scripting support?
Date: Wed, 27 Dec 95 19:49:00 -0800
From: Rich Graves
SLIP and the scripter aren't included on the floppy or some OEM versions of
Win95, and there exists no Setup option to install them, but you can get
them free without buying the Plus Pack. If you have the CD, use Add/Remove
Programs\Windows Setup\Have Disk and navigate to Admin\Apptools\DSCRIPT. If
you don't have the CD, you can download DSCRPT.EXE (note missing "I") from
Microsoft's online services, such as www.windows.microsoft.com,
specifically on the CD Extras Page,
http://www.windows.microsoft.com/windows/software/cdextras.htm.
--------------------------
Content-Description: D.14. Why do I get "host unreachable" on most remote hosts, though I can get to my ISP's servers?
Date: Wed, 27 Dec 95 19:49:00 -0800
From: Rich Graves
Here's a bizarre one. If:
1. Dialup networking is being used without a scripter (i.e., pop up a
terminal window)
2. DNS servers are entered in TCP/IP Properties
3. You're getting a dynamically assigned IP address from a Cisco or
Xyplex terminal server (others too, probably)
Then you don't get a default router, and you can't reach remote sites.
However, because of some other odd Win95 behavior and the proxy arp
features of most terminal servers, you can usually get to hosts within your
Class A net (i.e., X.*.*.*).
It's not just me -- ask jpherron@indiana.edu (Jon-Paul Herron).
[Please see D.6. for a possible hint.]
--------------------------
Content-Description: D.15. If my connection drops, why don't my TCP sessions reconnect?
Date: Sat, 23 Sep 95 06:15:40 -1000
From: Richard Puga
I must be the only person on earth who has a statically assigned IP address
which stays the same each time I dial in... or at least I'm the only one
who is annoyed by the problem...
When I am dialed in PPP and have several telnet sessions open and say a
couple of FTP's going and maybe even IRC the PPP daemon will kill all those
sessions if the phone line drops!
And I mean KILL.. all my screens either completely Zap off my screen or
erase themselves.. all my ftp's stop and IRC dies..
In the other operating systems I have on my computer or use from time to
time (which include FreeBSD, NetBSD, NextStep, SunOS, OS/2, windows311(w/
trumpet)... (and Mac OS but I don't use it:)) will all allow me to simply
redial the ISP and continue where they left off.. Its not unreasonable for
the FTP sessions to keep going as well.. Heck even HTML transfers have
picked back up upon redialing...
It's my understanding that the original DOD purpose for TCP/IP protocol was
to withstand intermittent loss of signal or even to reroute traffic in case
of loss of that signal...
[Indeed, every PPP interface I know of save the Shiva/Microsoft package
will reconnect. This is how TCP/IP and PPP were designed. There is no
reason Win95 should do this.]
--------------------------
Content-Description: D.16. How do I change my modem init string?
Date: Mon, 2 Oct 1995 21:18:48 GMT
From: ramesh@scr.siemens.com (Ramesh Viswanathan)
Open My Computer -> Dial-Up Networking -> Right-click your ISP icon and
choose Properties -> Configure button -> Connection Tab -> Advanced Button
-> Enter desired modem initialization string in the Extra Settings box.
--------------------------
Content-Description: D.17. Will Twinsock work in Win95?
Date: Tue, 3 Oct 1995 03:49:57 GMT
From: "D.R."
[The Internet Adapter is a SLIP/PPP emulator that runs in UNIX to give
you a near complete Internet connection even if you only have a shell
account.]
Yes, though for older versions you might need to disable IP header
compression. There are some useful FAQs at:
http://marketplace.com/tia/docs.html
The freeware SLiRP will also work fine.
--------------------------
Content-Description: D.19. How do you start dialup networking from the command line?
Date: Mon, 09 Oct 1995 20:07:47 GMT
From: dolender@solutions.net (Doug Olender)
Message-ID: <45bruv$fet@Alpha.remcan.ca>
You can start up DialUp Networking as follows:
rundll32.exe rnaui.dll,RnaDial connection_name
--------------------------
Content-Description: D.20. Why does Win95 fail to negotiate with a Xylogics TIP if NetBEUI is enabled?
Date: 13 Oct 1995 18:22:45 GMT
From: jcmorris@mwunix.mitre.org (Joe Morris)
Message-ID: <45mapl$lsk@reuters2.mitre.org>
A couple of points:
Access ports that use challenge/response authentication (for example the
SecurID card from Security Dynamics) require a post-connect window in order
to deliver the challenge and receive the response.
Also, on our dial-in interface systems (Xylogics Annex boxes) I've found
that WIN95 will fail to complete the initial PPP handshaking if the dialup
conn