Windows 95tmNetworking FAQ

Extra! Microsoft Finally Acknowledges SMB Security Bug, After Several Months of Public Disclosure!

Extra! Novell Releases Client32 for Win95! Full NDS, NetWare/IP support!

------------------------------
Archive-name: ms-windows/win95netbugs
Posting-Frequency: twice monthly
Changes-posted-to: news.answers,comp.answers
FAQ-Maintainer: Rich Graves <llurch@networking.stanford.edu>
Last-Change: 10 Oct 1995 by Rich Graves <llurch@networking.stanford.edu>
Version: 4.00.490
URL: http://www-dccs.stanford.edu/NetConsult/Win95Net/faq.html

------------------------------
Content-Description: Unindexed Recent Arrivals

------------------------------
Content-Description: Index
Date: Sun, 24 Sep 95 22:30:47 -0800
From: Rich Graves <llurch@networking.stanford.edu>

A.Admin|B.IPX/SPX|C.TCP/IP|D.Dialin|E.Misc|F.Windows|G.Hardware

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 © 1995 The Board of Trustees of Stanford University. Noncommercial redistribution encouraged.

5. To do's and cries for help.

B. IPX/SPX (NetWare) Issues

1. SAP advertisement kills IPX routing, poses security problems (now with a response from Microsoft).

2. Automatic frame type detection doesn't work.

3. What does Novell recommend regarding Win95 and NetWare?

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. NetWare client just refuses to work on a few machines.

10. Didn't Microsoft announce that a 32-bit NetWare client bug fix/feature enhancement would be available soon?

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.

C. TCP/IP (Internet) Issues

1. No interface for changing MTU or RWIN settings.

2. Netscape packet storm bugs.

3. Web browser/TCP connection "hanging" bug.

4. Intermittent DNS bug: appending ??? to lookups.

5. Interoperability with BootP servers.

6. Can't mount servers by IP address.

7. [Removed, superseded by c15]

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 commercial-quality TCP/IP stacks are available to replace the stack that Microsoft supplies?

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.

D. Dialin (SLIP/PPP/RAS) 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.

What are some tips for better dialin performance?

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. Microsoft Office 4.3 leaves a file open, preventing proper Windows shutdown.

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)

G. Hardware-Specific Issues

1. NE4100 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.

A.Admin|B.IPX/SPX|C.TCP/IP|D.Dialin|E.Misc|F.Windows|G.Hardware

------------------------------
Content-Description: A.1. Where is the latest FAQ?
Date: Sun, 24 Sep 95 17:05:18 -0800
From: Rich Graves <llurch@networking.stanford.edu>

http://www-leland.stanford.edu/~llurch/win95netbugs/faq.html
http://www-dccs.stanford.edu/NetConsult/Win95Net/faq.html

Back to index

------------------------------
Content-Description: A.2. What's this about a Win95NetBugs email list?
Date: Sun, 24 Sep 95 22:30:47 -0800
From: Rich Graves <llurch@networking.stanford.edu>

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 will cooperatively compile a FAQ file and Web page(s) for end users.

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.

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 don't expose yourself to ridicule by posting administrative messages to the entire list!

Messages sent to the list by non-subscribers will be bounced to the moderator for review. Pertinent messages will usually be passed along with minimal delay. Spammers will be spanked.

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.

Back to index

------------------------------
Content-Description: A.3. What related resources are available?
Date: Sun, 24 Sep 95 18:09:47 -0800
From: Rich Graves <llurch@networking.stanford.edu>

For technical information on PC TCP/IP networking, 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

Microsoft publishes selected known problems and workarounds in the Windows Knowledge Base, http://www.microsoft.com/kb/indexes/windows.htm. The keywords "kbnetwork," "3rdPartyNet," and "win95" are useful to know.

Back to index

------------------------------
Content-Description: A.4. Copyright blah blah blah.
Date: Sun, 24 Sep 95 18:09:47 -0800
From: Rich Graves <llurch@networking.stanford.edu>

Back to index

------------------------------
Content-Description: A.5. To Do's and cries for help.
Date: Sun, 24 Sep 95 23:00:07 -0700
From: Rich Graves <llurch@networking.stanford.edu>

• Troubleshooting section. How to use NETSTAT, PING, TRACERT, etc.
• DLC section. I've received some cryptic notes about problems. I hardly even understand what DLC is.
• Programmer's section.
• More stuff on modems. I hardly ever use one myself.
• Recommendations for good books and Web sites.
• More on NetWare. I don't know much about it.
• Hardware incompatibilities. I know there's problems with WD/SMC 80x3, cheap NE2000 clones, 3Com 3C509 in PnP mode, and NE4100.

Back to index

A.Admin|B.IPX/SPX|C.TCP/IP|D.Dialin|E.Misc|F.Windows|G.Hardware

------------------------------
Content-Description: B.1. SAP advertisement kills IPX routing, poses security problems
Date: Sun, 17 Sep 95 22:30:47 -0800
From: Rich Graves <llurch@networking.stanford.edu>

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 response to this issue. It is saved at http://www-leland.stanford.edu/~llurch/win95netbugs/MS-SAP-Response.txt.

Back to index

------------------------------
Content-Description: B.2. Automatic frame type detection doesn't work.
Date: Sun, 17 Sep 95 22:30:47 -0800
From: Rich Graves <llurch@networking.stanford.edu>

Back to index

------------------------------
Content-Description: B.3. What does Novell recommend regarding Win95 and NetWare?
Date: Sun, 17 Sep 95 22:30:47 -0800
From: Rich Graves <llurch@networking.stanford.edu>

Back to index

------------------------------
Content-Description: B.4. Win95 Crashes NetWare 3.12 server.
Date: Wed, 13 Sep 1995 03:07:25 GMT
From: zim@grayfox.svs.com (Jason Zimberoff)
Update: Fri, 10 Oct 1995 00:00:00 GMT

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

------------------------------

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: Rich Graves <llurch@networking.stanford.edu>

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

Back to index

------------------------------

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: Tue, 10 Oct 1995 20:00:00 GMT
From: Rich Graves <llurch@networking.stanford.edu>

What I was referring to here was some setup which is allegedly necessary to make Win95 actually *work* with the OS/2 namespace.

However, 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: Sun, 24 Sep 1995 20:00:00 GMT
From: Rich Graves <llurch@networking.stanford.edu>

By default, Win95 machines using Microsoft's 32-bit NetWare client do not receive NetWare broadcast messages. Novell recommends using their existing version 1.2 real-mode drivers and NWPOPUP instead.

You could also put WINPOPUP.EXE in AUTOEXEC.BAT or your Startup folder. However, there's apparently no way to remove WINPOPUP from the task list or to stop users from quitting it.

Back to index

------------------------------

Content-Description: B.8. Can I send NetWare messages with Win95?
Date: Tue, 10 Oct 1995 20:00:00 GMT
From: Rich Graves <llurch@networking.stanford.edu>

Back to index

------------------------------

Content-Description: B.9. NetWare client just refuses to work on a few machines.
Date: Sat, 23 Sep 1995 20:02:29 -0700
From: Rich Graves <llurch@networking.stanford.edu>

Newsgroups: comp.os.ms-windows.win95.misc,comp.os.ms-windows.win95.misc

In article <44138n$e96@cnn.Princeton.EDU>, joeross@princeton.edu
(Joe Ross) wrote:

> 2 Networking questions:
> 
> 1.  I'm trying to configure a friends computer to connect to a Novell 
> Netware Network.  The only problem is I can't get a login screen to come 
> up when he turns on his computer.  I've tried everything(I think):  
> switching the primary login to Windows logon and then back to netware.  
> I haven't had this problem with anyone else's computer.

Bizarre. When you try to mount a server with \\ or net use, does anything
happen? Attach an external transceiver with idiot lights and watch the
transmit/receive activity.

You could look in C:\BOOTLOG.TXT for a record of what happens at startup.
Not that you'll be able to understand it...

------------------------------

Content-Description: B.10. Didn't Microsoft announce that a 32-bit NetWare client bug fix/feature enhancement would be available soon?
Date: Sun, 24 Sep 1995 20:00:00 GMT
From: Rich Graves <llurch@networking.stanford.edu>

Back to index

------------------------------

Content-Description: B.11. User-level access control doesn't work over IPX NWServer.
Date: Tue, 10 Oct 1995 20:00:00 GMT
From: Rich Graves <llurch@networking.stanford.edu>

Back to index

------------------------------

Content-Description: B.12. DISPLAY Command in Login Script Displays Incorrect Characters.
Date: Tue, 10 Oct 1995 20:00:00 GMT
From: Rich Graves <llurch@networking.stanford.edu>

Back to index

------------------------------

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 <llurch@networking.stanford.edu>

Back to index

------------------------------

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 <llurch@networking.stanford.edu>

Back to index

------------------------------

Content-Description: B.15. Cannot load TSRs in NetWare login scripts.
Date: Tue, 10 Oct 1995 20:00:00 GMT
From: Rich Graves <llurch@networking.stanford.edu>

Back to index

------------------------------

Content-Description: B.16. Cannot Connect to NCP Server Without SAP Advertising Enabled.
Date: Tue, 10 Oct 1995 23:00:00 GMT
From: Rich Graves <llurch@networking.stanford.edu>

Back to index

------------------------------

Content-Description: B.17. Commas Not Recognized in NetWare Logon Scripts.
Date: Tue, 10 Oct 1995 23:00:00 GMT
From: Rich Graves <llurch@networking.stanford.edu>

Back to index

------------------------------

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 <llurch@networking.stanford.edu>

Back to index

------------------------------

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>

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

A.Admin|B.IPX/SPX|C.TCP/IP|D.Dialin|E.Misc|F.Windows|G.Hardware

------------------------------

Content-Description: C.1. No interface for changing MTU or RWIN settings.
Date: Sun, 24 Sep 95 21:15:21 -0800
From: Rich Graves <llurch@networking.stanford.edu>

The entries in this section must be added to the following Registry key, where n represents the particular TCP/IP-to-network adapter binding.

Hkey_Local_Machine\System\CurrentControlSet\Services\Class\netTrans\000n

MaxMTU = 16-bit integer

Specifies the maximum size datagram IP that can pass to a media driver. SNAP and source routing headers (if used on the media) are not included in this value. For example, on an ethernet network, MaxMTU will default to 1500. The actual value used will be the minimum of the value specified with this parameter and the size reported by the media driver. The default is the size reported by the media driver.

RWIN is a TCP-specific thing, but maybe this question should be moved to the General/Dialin section anyway?

Back to index

------------------------------

Content-Description: C.2. Netscape Packet Storm Bugs.
Date: Sun, 01 Oct 95 21:31:42 -0800
From: Rich Graves <llurch@networking.stanford.edu>

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 TCP to understand the problem.

Back to index

------------------------------

Content-Description: C.3. Web browser/TCP connection "hanging" bug.
Date: Sun, 17 Sep 95 22:30:47 -0800
From: Rich Graves <llurch@networking.stanford.edu>

Back to index

------------------------------

Content-Description: C.4. Intermittent DNS bug: appending ??? to lookups.
Date: Sun, 17 Sep 95 22:30:47 -0800
From: Rich Graves <llurch@networking.stanford.edu>

Back to index

------------------------------

Content-Description: C.5. Interoperability with BootP servers.
Date: Sun, 17 Sep 95 22:30:47 -0800
From: Rich Graves <llurch@networking.stanford.edu>

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, you can ping him at jmwobus@syr.edu.

Two Guys and a Vax (www.tgv.com, sales@tgv.com) have announced a replacement TCP/IP stack for Windows 95 that handles BootP properly, and some other highly desirable features. They also make some rather nice applications. Demos are available. Of course they want real money for this stuff.

Back to index

------------------------------

Content-Description: C.6. Can't mount servers by IP address.
Date: Sun, 17 Sep 95 22:30:47 -0800
From: Rich Graves <llurch@networking.stanford.edu>

Back to index

------------------------------

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 <llurch@networking.stanford.edu>

This extract from the Resource Kit comes from Daniel M <puppet@mail.dynamsol.com. This does not seem to apply to the 32-bit WinSock; could anybody tell me about that?

Hkey_Local_Machine\System\CurrentControlSet\Services\VxD\MSTCP\ServiceProvider

The following keys describe the order used to resolve host names. A lower number
sets a higher priority for name resolution. These settings are used for 16-bit
Windows Sockets, which need to rely on the resolvers that are expected to take
the least time.
 
The numbers indicate the default values specified in Windows 95.

LocalPriority = 499
HostsPriority = 500
DNSPriority = 2000
NetbtPriority = 2001

------------------------------

Content-Description: C.9. DNS lookup timeout is ridiculously long.
Date: Sun, 17 Sep 95 22:30:47 -0800
From: Rich Graves <llurch@networking.stanford.edu>

There's gotta be a way to set this; anybody?

Back to index

------------------------------

Content-Description: C.10. Why can't I send mail/news or upload with FTP (MTU path discovery problem)?
Date:  Sun, 24 Sep 1995 15:23:18 -0700
From: Rich Graves <llurch@networking.stanford.edu>

Message-Id: <199509242223.PAA04539@Networking.Stanford.EDU>
>Subject>: Re: Eudora problem with 95 (path MTU discovery?)
Newsgroups: comp.os.ms-windows.win95.setup,
            comp.os.ms-windows.networking.tcp-ip,
            comp.protocols.tcp-ip.ibmpc,
            comp.os.ms-windows.win95.misc,
            comp.os.ms-windows.apps.winsock.mail,
            comp.os.ms-windows.apps.winsock.news,
            comp.os.ms-windows.apps.winsock.misc
            
Yes, you have accurately diagnosed the problem win Win95 uploads, commonly
seen in mail and news programs.

To fix this, open the Registry and set one or both of these:

 Hkey_Local_Machine\System\CurrentControlSet\Services\VxD\MSTCP

 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.

It would be *nice* if there were a Knowledge Base article on this, or if
the people answering the $1.95 per minute network support lines had *just
one* clue.

Setting MTU to some ridiculously low value will also work, but
it hurts
performance.

The TGV and what's-his-name replacement TCP/IP stacks for Win95 will
fragment properly according to existing Internet standards.

Posted widely, followups restricted.

> From: pirard@vm1.ulg.ac.be (Andri
Pirard)
> Newsgroups: comp.os.ms-windows.win95.setup
> >Content-Description: Re: Eudora problem with 95 (path MTU discovery?)
> Date: Sun, 24 Sep 1995 12:40:58 GMT
> Organization: SEGI, Universiti de Lihge, Belgique
> Message-ID: <443n5c$ff9@aix1.segi.ulg.ac.be>
> References: <42uv3o$2ad@tattoo.sccsi.com>
> 
> mhuff@sccsi.com (Max K. Huff) wrote:
> 
>>Eudora appears to limited to outgoing message length of about 10 lines.  
>>Anything in excess of 10 lines hangs during the "send" operation.  It
sends a 
>>"time-out" message after a while.  The results are the same with Eudora
2.0.3 
>>and the new 2.1.0 versions. Also is the same with another machine running
95 
>>with Eudora.  Is Eudora not compatible with 95, or is there a parameter I

>>missed?
>>Thanks
>>Max
> 
> Microsoft TCP/IP for Win 3, and presumably Win 4, implements recent
> "Path MTU discovery" technique. This implies setting the "Don't
> fragment" bit in outgoing IP packets. You may get in trouble with IP
> routers that would have to fragment the packets, are told not to do
> so, and discard them without replying with the now necessary ICMP
> control message (and M$ TCP/IP copes badly with this situation).
> 
> If that's your problem (which you can make almost sure by testing that
> an FTP upload blocks also), your solution is to either disable path
> MTU discovery or to set your line interface's MTU to 576 (hoping that
> the router transmits at least that without the need to fragment, it
> should).
> In Win 3, SYSTEM.INI contains a pathmtudisc=1 (or like) to be set to
> 0. MTU and Win 4: dunno, sorry, look around.
> 
> 
> 
> Andri PIRARD         SEGI, Universiti de Lihge  | 139.165.0.0 IP (ULg)
> B26 - Sart Tilman    B-4000 Lihge 1 (Belgium)   | Integrator and Adm.
> pirard@vm1.ulg.ac.be aka PIRARD@BLIULG11.BITNET   +32 (41) 664932

------------------------------

Content-Description: C.11. What commercial-quality TCP/IP stacks are available to replace the stack that Microsoft supplies?
Date: Sun, 24 Sep 1995 20:00:00 GMT
From: Rich Graves <llurch@networking.stanford.edu>

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.

Back to index

------------------------------

Content-Description: C.12. I can't get PC/NFS working under Windows 95.
Date: Sun, 24 Sep 1995 20:00:00 GMT
From: Rich Graves <llurch@networking.stanford.edu>

Betas and first releases of NFS for Win95 are available from Beame & Whiteside and others, but that's beyond the scope of this FAQ. You could also make your UNIX machines speak Microsoft's proprietary SMB protocol by installing SAMBA (reference?).

Back to index

------------------------------

Content-Description: C.13. Will Trumpet and other Win3 TCP/IP stacks work under Win95?
Date: Sun, 24 Sep 1995 20:00:00 GMT
From: Rich Graves <llurch@networking.stanford.edu>

Back to index

------------------------------

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: Sun, 24 Sep 1995 20:00:00 GMT
From: Rich Graves <llurch@networking.stanford.edu>

Back to index

------------------------------

Content-Description: C.15. Assorted DNS resolution problems.
Date: Sun, 24 Sep 1995 20:00:00 GMT
From: Rich Graves <llurch@networking.stanford.edu>

Back to index

------------------------------

Content-Description: C.16. What arcane TCP/IP parameters can be configured?
Date: Mon, 18 Sep 1995 04:44:07 +0000
From: Daniel M <puppet@mail.dynamsol.com>

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 specifi e d 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 adap t ers. 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: Sat, 23 Sep 95 23:44:29 0300
From: Vadim <vadim@melig.co.il>

Message-Id: <199509232144.XAA03624@mail.netvision.net.il>
To: win95netbugs@lists.Stanford.EDU
>Content-Description: IP forwarding in Win95 

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-imlemented feature or just wrong configuration ?

------------------------------

Content-Description: C.18. Sockets get "eaten up" and WinSmtp dies.
Date: Tue, 19 Sep 1995 11:15:38
From: Jack De Winter <jackdw@metrics.com>

To: win95netbugs@lists.Stanford.EDU
>Content-Description: Problems with sockets getting eaten up...
Message-Id: <19950919111538.8ae27b48.in@panda.metrics.com>

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?

regards,
Jack
--------------------------------------------------------------------------
Jack De Winter                  Author of WinSmtp and other  fine products
Software Metrics, inc.          'there once was a lady named bright
jackdw@metrics.com               whose speed was far greater than light
                                 she set out one day
                                 in a relative way
                                 and came back the previous night.'

Back to index

------------------------------

Content-Description: C.19. Can I disable DNS for WINS resolution?
Date: Tue, 10 Oct 95 23:30:00 -0800
From: Rich Graves <llurch@networking.stanford.edu>

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

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\MSTCP

Back to index

------------------------------

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 <llurch@networking.stanford.edu>

Back to index

A.Admin|B.IPX/SPX|C.TCP/IP|D.Dialin|E.Misc|F.Windows|G.Hardware

------------------------------

Content-Description: D.1. Nonstandard PPP implementation causes problems with BSDI and other servers.
Date: Sun, 17 Sep 95 22:30:47 -0800
From: Rich Graves <llurch@networking.stanford.edu>

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! Further information on Microsoft's implementation is available in that directory, but in general the extensions to CHAP won't cause problems.

There has been some discussion of this on the comp.protocols.ppp newsgroup.

Date: Sat, 26 Aug 1995 11:46:58 -0500
Message-Id: <199508261646.LAA05931@krystal.com>
To: Jim Flowers <jflowers@raptor.eznets.canton.oh.us>, 
bsdi-users@BSDI.COM, Small Internet Access Providers <IAP@VMA.CC.ND.EDU>
From: Paul Borman <prb@BSDI.COM>
>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.

This note is meant to be an explanation of what is happening and should
not be interpreted in any way as an offical statement by BSDI on The
Microsoft IPCP Options.

                                -Paul Borman
                                 prb@bsdi.com

------------------------------

Content-Description: D.2. Degraded SLIP/PPP performance versus Trumpet.
Date: Sun, 17 Sep 95 22:30:47 -0800
From: Rich Graves <llurch@networking.stanford.edu>

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.

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 <rpritz@panix.com>
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.

Back to index

------------------------------

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)

Organization: Primenet
Newsgroups: comp.os.ms-windows.win95.misc,comp.os.ms-windows.win95.setup
Message-Id: <432pb4$n3@nnrp3.primenet.com>

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?

------------------------------

Content-Description: D.4. Minor changes to TCP/IP or modem parameters cause dialup properties to reset to defaults without warning.
Date: Sun, 17 Sep 95 22:30:47 -0800
From: Neil Moodie <nmoodie@c031.aone.net.au>

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.

Back to index

------------------------------

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)

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.)

Back to index

------------------------------

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> <nagamatiDFBExI.DnC@netcom.com>

In article <nagamatiDFBExI.DnC@netcom.com> 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)

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. Back to index

------------------------------

Content-Description: D.8. PPP compression won't work on at least some Xyplex terminal server configs.
Date: Tue, 10 Oct 95 01:30:47 -0800
From: Rich Graves <llurch@networking.stanford.edu>

Back to index

------------------------------

Content-Description: D.8. PPP compression won't work on at least some Xyplex terminal server configs.
Date: Mon, 2 Oct 1995 01:37:03 GMT
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 what ever 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.

A.Admin|B.IPX/SPX|C.TCP/IP|D.Dialin|E.Misc|F.Windows|G.Hardware

------------------------------

Content-Description: E.1. No way to specify protocol to use for a specific service.
Date: Sun, 17 Sep 95 22:30:47 -0800
From: Rich Graves <llurch@networking.stanford.edu>

As far as I can tell, I have to browse for \\UTAH on all protocols in series. Broadcast over NetBIOS, maybe go to a Browse Master, and wait for a timeout; Broadcast over TCP/IP, check the WINS server, check the DNS server, check LMHOSTS, perhaps :including a file cross-mounted from another server, and wait for a bunch of timeouts; and only then will my machine deign to look for UTAH over IPX/SPX.

This is inefficient, wastes time, and wastes bandwidth on slow links.

Back to index

------------------------------

Content-Description: E.2. IPX must be set as the default protocol to use a Lotus Notes server.
Date: Sat, 16 Sep 1995 00:18:10 -0700
From: jzaums@ix.netcom.com (John Robert Zaums)

Newsgroups: comp.os.ms-windows.win95.setup
>Subject>: Re: HELP: Lotus Notes and Win 95.
Message-ID: <43dm40$prh@ixnews7.ix.netcom.com>
References: <43bf71$a4p@bach.threex>

mikes@threex.demon.co.uk (Michael Sheppard) wrote:

>We are having problems setting up Lotus Notes to work with Windows 95. 
>Our Notes server is running over a Novell network. We have configured the 
>IPX/SPX protocol and Novell client support under Win 95 and we can access 
>the Novell fileserver. We have configured NETBIOS to run over IPX/SPX (we 
>think) but Notes can't find the Notes server. It complains that the 
>NETBIOS unit number(0) is too large. To me this seems that we must have 
>the NETBIOS configuration wrong, but we can't see where to correct it. If 
>anyone has working NETBIOS over IPX/SPX or has setup Notes with Win 95 
>could you please help me and let me know how you did it.

It's fun ------ I'll agree with you on that one. I battled with this
for about 4-5 months until I discovered an obscure little paragraph on
Microsoft Technet describing how to do it. Two solutions:
First
If you are loading stuff real mode you can use NETBIOS.EXE real mode
and it will work.
Second
But then again what's the advantage of '95 without 32 bit drivers.
Here's the trick. 
Go to the Network Control Panel
Select IPX/SPX Compatible Protocol
Select the Advanced Tab
At the bottom of the window you will see a check box saying "Set this
protocol to be the default protocol"
Once you've done that it should work. I've found performance to be
significantly better as well.

------------------------------

Content-Description: E.3. Win95 does not honor LAN Manager security, other incompatibilities.
Date: Tue, 19 Sep 1995 10:18:27 -0400
From: Rich Graves <llurch@networking.stanford.edu>

Message-Id: <199509191418.KAA24698@io.org>
To: win95netbugs@lists.Stanford.EDU
From: mnewton@io.org (Malcolm Newton)
>Subject>: win95 and Lan Manager seriuos security problems

Win 95 does not seem to respect share level security on Lan Manager servers
plus there seems to be a bug that only displays 6 folders/files within any
other folder/sub-folder. We will switch to user level security and test this
over the next couple of days.   
Malcolm Newton    President
mnewton@io.org    http://www.io.org/~mnewton
VisiSoft Corp   2145 Dunwin Dr unit 11, Mississauga,Ont. Can L5L 4L9
(905) 607 6263 (905) 607 6122 fax

------------------------------

Content-Description: E.4. With ODI drivers, adding an NDIS 3.1 protocol does not add frame type to NET.CFG.
Date: Tue, 10 Oct 1995 10:18:27 -0400
From: Rich Graves <llurch@networking.stanford.edu>

Back to index

------------------------------

Content-Description: E.5. How can I hide the Network Neighborhood icon?
Date: Tue, 10 Oct 1995 10:18:27 -0400
From: Rich Graves <llurch@networking.stanford.edu>

Back to index

------------------------------

Content-Description: E.6. How can I hide the Inbox icon?
Date: Tue, 10 Oct 1995 10:18:27 -0400
From: Rich Graves <llurch@networking.stanford.edu>

Back to index

------------------------------

Content-Description: E.7. How can I get rid of the Microsoft Network icon?
Date: Tue, 10 Oct 1995 10:18:27 -0400
From: Rich Graves <llurch@networking.stanford.edu>

Back to index

------------------------------

Content-Description: E.8. How can I get Exchange to work like a normal Internet mail client?
Date: Tue, 10 Oct 1995 10:18:27 -0400
From: Rich Graves <llurch@networking.stanford.edu>

• No .signature
• Annoying WINMAIL.DAT attachment
• Incorrect quoted/printable parsing
• Negative time zones for anyone East of Greenwich
• Puts addresses in redundant single quotes
• Very slow
• May continue to suck mail off the server and delete it even if you think you've disabled it

Back to index

------------------------------

Content-Description: E.9. I increased the scrollback buffer size in telnet and now it doesn't work -- no menus even.
Date: Sat, 7 Oct 1995 15:45:42 GMT
From: ramesh@scr.siemens.com (Ramesh Viswanathan)
Newsgroups: comp.os.ms-windows.win95.misc

Mike DeMarco (demarco@eniac.seas.upenn.edu) wrote:
: I was trying to up the buffer size in the telnet program that comes with
: Win95 and apparently set it too high.  Now when I start the program, all 
: that comes up is the title bar of the window. I can't get back to the menu 
: settings menu because of this.  As a result, I can't set the buffer to its 
: original size.  Is there some kind of configuration file that I can edit or
: something to reset the buffer to 25 and get the program working again?

Yes, I had encountered this problem very early in the Beta, and microsoft is
aware of this problem.  I have been able to reset it using the registry as
follows:

1. Start Regedit and search for the Key word Telnet
2. Stop when you find the key: \HKEY_CURRENT_USER\Software\Microsoft\Telnet
3. On the Right hand Window Pane, double click on the Item that says Rows
4. On the Dialog Windows that comes up Choose the Decimal Radio Button
   and enter the value you want, 
5. Of course exit out of the registry.

------------------------------

Content-Description: E.10. Microsoft Office 4.3 leaves a file open, preventing proper Windows shutdown.
Date: Tue, 10 Oct 1995 10:18:27 -0400
From: "Peter Watt (Comtex)" <PETERW@RC.COMTEX.synet.net.nz>

Microsoft sources confirm that this is a problem with Win95 and Microsoft Office. Workarounds:

• Run msoffice.exe from the local disk, not the server. Other components of Microsoft Office may be run from the server.
• Run msoffice.exe by UNC (like \\server\directory\msoffice.exe) rather than by a mapped drive path. However, this might cause other problems.

Back to index

A.Admin|B.IPX/SPX|C.TCP/IP|D.Dialin|E.Misc|F.Windows|G.Hardware

------------------------------

Content-Description: F.1. If your Windows NT client is unable to connect to a Windows 95 server.
Date: Tue, 10 Oct 1995 00:00:00 -0700
From: Rich Graves <llurch@networking.stanford.edu>

The password encryption method used by Windows NT is different from the method used by Windows 95.

You may be able to work around this problem by using one of the following methods:

• Use all uppercase or all lowercase characters in the Windows 95 shared folder password.
• Remove password protection from the shared folder.
• Use user-level access control instead of share-level access control.

Back to index

------------------------------

Content-Description: F.2. Incomplete Domain Listing on Large Networks.
Date: Tue, 10 Oct 1995 00:00:00 -0700
From: Rich Graves <llurch@networking.stanford.edu>

When you are browsing the network, Windows 95 stores the domain names in a table that is limited to 64K in size. When this table is full, no more domains are displayed.

In addition, many WINS servers have a known problem that causes them to report that domains exist, even after these domains have been removed from the network. On large networks, or on networks where domains are frequently removed shortly after they are created, this problem may prevent domains that currently exist on the network from being displayed in Network Neighborhood.

Microsoft has confirmed this to be a problem in Microsoft Windows 95. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

Back to index

------------------------------

Content-Description: F.3. No Support for "Connect As" Option Like in Windows NT.
Date: Tue, 10 Oct 1995 00:00:00 -0700
From: Rich Graves <llurch@networking.stanford.edu>

Microsoft Windows NT has an option that lets you connect to a network resource as someone else. This option uses a Connect As box in the Connect Network Drive dialog box.

Microsoft Windows 95 does not have such an option in its Map Network Drive dialog box. The only way to connect to a network resource as someone else in Windows 95 is to log off and then log back on as a different user.

Back to index

------------------------------

Content-Description: F.4. How do I get Win95 to honor NT %USERNAME%?
Date: Sun, 01 Oct 1995 13:03:42 GMT
From: johnr@ids.net (John Robinson)
Newsgroups: comp.os.ms-windows.win95.misc
Message-ID: <44m359$g82@paperboy.ids.net>

>Date: Sun, 10 Sep 95 11:00:40 PDT
>From: Scott McArthur <scottmca@microsoft.com>
>To: win95netbugs-owner@lists.stanford.edu
>Subject>: RE: Win 95 and NT server
> 
> Tony Chandler <T.Chandler@blds.canterbury.ac.nz> wrote:
>>I have a NT 3.51 server.  I have set up users with a home directory 
>>in there user profile.  I have also got a logon script that sets up 
>>drives using %USERNAME%.
>>Windows 95 clients logging into the NT server canot see there home 
>>directory or the drives setup with the %username%, username is 
>>undefined. Has any body got this going?
>
>This is a resource kit documentation error.  Windows 95 does not support
>these variables.  Only supported by NT workstations.  NT sets these
>variables on boot whereas Win95 does not.  At a NT box do a set at a
>command prompt and you will see all these variables.  You can set a home
>directory in user manager by setting "connect to" to a \\server\share
>designation and on the 95 client doing a
> 
>net use h: /home
> 
>the h drive will then be mapped.  It will not be the default directory 
>apps will save to though.

I am using %username% but it took a lot of digging. You need two
programs-PUTINENV and WINSET (on the win95 CD). I am using NT server
with a logon script. The game is to get the environment variables of
the user who just logged on using PUTINENV L and then to put this
info into the Win95 master environment with WINSET. You then can map
a drive to the user's home directory and have all the benefits of
the %username% variable. Below is my login script -- hope this helps.

if %os%==Windows_NT goto END 

\\server\netlogon\putinenv L
 
\\server\netlogon\winset username=%username%

net use f: /home

\\server\netlogon\winset eudora=f:\%username%
:END

John Robinson <johnr@ids.net>

------------------------------

Content-Description: F.5. WFW machines can't log on to Win95 machines with access list from another domain.
Date: Tue, 10 Oct 1995 00:00:00 -0700
From: Rich Graves <llurch@networking.stanford.edu>

Back to index

------------------------------

Content-Description: F.6. Troubleshooting Browsing with Client for Microsoft Networks.
Date: Tue, 10 Oct 1995 00:00:00 -0700
From: Rich Graves <llurch@networking.stanford.edu>

Back to index

------------------------------

Content-Description: F.7. Can I log on to multiple NT domains?
Date: Tue, 10 Oct 1995 00:00:00 -0700
From: Rich Graves <llurch@networking.stanford.edu>

Back to index

------------------------------

Content-Description: F.8. Error Message: "VNETSUP: Error 6102" (WORKGROUP corruption)
Date: Tue, 10 Oct 1995 00:00:00 -0700
From: Rich Graves <llurch@networking.stanford.edu>

Back to index

A.Admin|B.IPX/SPX|C.TCP/IP|D.Dialin|E.Misc|F.Windows|G.Hardware

------------------------------

Content-Description: G.1. NE4100 Incompatibility.
Date: Sun, 17 Sep 1995 16:49:46 -0700
From: Nick Sayer <nsayer@quack.kfu.com>

What I believe is happening is that the NE4100 "support" simply is to just run with an NE2000 driver when you see an NE4100. This is not quite the correct thing to do.

Real NE2000 cards have a small ROM in their I/O space that contains the Ethernet address. A PCMCIA card has to have about a K of attribute ROM located elsewhere anyway in order to describe the card to the card-n-socket services. The folks who make PCMCIA NE2000 cards didn't bother to put the extra Ethernet address ROM in the I/O space as well, they simply placed the Ethernet address in the attribute ROM (usually at 0xff0) and left it up to the enabler or driver to do the right thing.

win95 does not do the right thing. It will use ff:ff:ff:ff:ff:ff as the Ethernet address for an NE4100. I reported this to the $35 tech support line and even more detail than the above paragraph. I told them exactly how a PCMCIA NE2000 differs from a real one. I even gave them tcpdump logs showing them the bogus packets (oh, by the way, the first thing win95 TCP does is send out an arp packet asking for its own Ethernet address. That's right: "arp: who is win95, tell win95"). I have not heard back from them.

[Moderator's addendum: the arp is a way of avoiding duplicate IP addresses. I think this is a Good Thing. As of October 1, 1995, Nick had still not heard back from Microsoft, the NE4100 was still on the Hardware Compatibility List, and the MS technical support lines were unaware of the problem.]

Back to index

------------------------------

Content-Description: G.2. Eagle NE200T PCMCIA NE200.COM ODI Driver Does Not Work.
Date: Tue, 10 Oct 1995 00:00:00 -0700
From: Rich Graves <llurch@networking.stanford.edu>

Back to index

------------------------------

Content-Description: G.3. IBMODISH.COM Causes Windows 95 to Exit at Startup.
Date: Tue, 10 Oct 1995 00:00:00 -0700
From: Rich Graves <llurch@networking.stanford.edu>

Back to index

------------------------------

Content-Description: G.4. 3Com 3C5x9 EtherLink III "Plug and Play" problems.
Date: Tue, 10 Oct 1995 00:00:00 -0700
From: Rich Graves <llurch@networking.stanford.edu>

Back to index

------------------------------

Content-Description: G.5. MS Client and PC/NFS conflict on some Xircom/IBM/Cabletron adapters.
Date: Tue, 10 Oct 1995 00:00:00 -0700
From: Rich Graves <llurch@networking.stanford.edu>

A Windows 95 computer running SunSoft's PC-NFS version 5.x and the Microsoft Client for Microsoft Networks may not be able to see shared resources on a PC-NFS server or an SMB server running the NetBEUI protocol.

This problem occurs because of a conflict between the NDISHLP.SYS driver used by VREDIR and the PCNFS.SYS driver supplied by SunSoft for their PC-NFS client. The conflict causes network packets to be forwarded incorrectly, so no packets are broadcast on the network.

This problem affects only certain PCMCIA and Cabletron network adapters. The following network adapters are known to exhibit this behavior:

• Xircom PCMCIA network adapters
• IBM Ethernet PCMCIA network adapters
• Cabletron Ethernet network adapters

Back to index

------------------------------

Content-Description: G.6. Errors and retransmissions with a SoundBlaster installed.
Date: Tue, 10 Oct 1995 00:00:00 -0700
From: Rich Graves <llurch@networking.stanford.edu>

Back to index

------------------------------

A.Admin|B.IPX/SPX|C.TCP/IP|D.Dialin|E.Misc|F.Windows|G.Hardware

------------------------------

Microsoft, MS, MS-DOS, Windoze, Windows NT, Windows 95, and the Windows logo are either registered trademarks or trademarks 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. Your mileage may vary. Trix are for kids. Back to the Top.