Windows Millennium Edition Network.txt File Contents (262912)

MORE INFORMATION

     ----------------------------------------
       Microsoft Windows Millennium Edition
              README for Networks
                   June 2000
     ----------------------------------------

     (c)Copyright Microsoft Corporation, 2000


This document provides complementary or late-breaking 
information to supplement the Microsoft(R) Windows(R) 
Millennium Edition (Windows Me) documentation.


------------------------
HOW TO USE THIS DOCUMENT
------------------------

To view Network.txt on-screen in Notepad, maximize 
the Notepad window.

To print Network.txt, open it in Notepad or another 
word processor, and then on the File menu, click Print.

--------
CONTENTS
--------

INTEL ETHEREXPRESS 16 NICs AND PCI COMPUTERS

NOVELL NETWARE

USING AN IBM THINKPAD WITH A DOCK II

USING COMSPEC VARIABLES POINTING 
  TO NETWORK COMMAND.COM FILES

SAMBA AND WINDOWS ME

MIRAMAR SYSTEMS PC MACLAN APPLETALK CONNECTIVITY

NETWORKS NOT SUPPORTED IN WINDOWS ME


============================================
INTEL ETHEREXPRESS 16 NICs AND PCI COMPUTERS
============================================

If you are using an Intel EtherExpress 16-network interface 
card (NIC) in a PCI computer that has a Diamond Speed Star 
PCI video card, your computer might stop responding or not 
initialize properly. According to Intel customer support, 
these problems are not related to Windows Me and happen on 
a variety of operating systems. 

If you have one of the following video cards, contact your 
vendor to obtain a new video BIOS update:

- Diamond Speed Star PCI video card with BIOS version 1.01

- Diamond Viper PCI VGA Video Adapter

- Diamond Stealth video card, BIOS v1.03

Other PCI video cards might also cause problems with this 
Intel NIC. In general, if you experience problems with your 
EtherExpress 16 in a PCI computer other than those described 
above, replace the card. If your computer still stops responding 
or does not initialize properly, report the problem to Microsoft.


==============
NOVELL NETWARE
==============

Syntax for Client32
-------------------
The following is the syntax for a Client32 UNC:

	\\NDS Tree Name\NDS Object Name

For example, to open a volume whose NDS container name is 
"server_vol1" in the context organizational unit "test" 
organization "ms" in the tree "Microsoft", the UNC syntax 
would be:

     \\Microsoft\.server_vol1.test.ms
or
     \\Microsoft\.cn=server_vol1.ou=test.o=ms

Subfolder information can be appended to NDS volumes. 
For example: 

     \\Microsoft\.server_vol1.test.ms\public

This path takes the user to the public folder on the 
server_vol1 volume.

Upgrading Over Client32
-----------------------
You must upgrade to Client32 2.2 or later before installing 
Windows Me.

IP Gateway Service
------------------
The Novell IP Gateway Service Task does not close after you 
browse using Internet Explorer 4.0 integrated shell. When 
Internet Explorer 4.0 is running as the shell, closing the 
browser window does not terminate Internet Explorer 4.0, and 
the Winsock is not closed. Functionality of the IP Gateway is 
not affected. Additional browser windows and other Winsock 
programs can use the Novell Winsock.

====================================
USING AN IBM THINKPAD WITH A DOCK II
====================================

If you enable 32-bit PC (PCMCIA) card support, and your network 
cards do not appear to work properly when inserted into the 
Dock II PC card slots, or if you have an ISA network card in 
the Dock II that has a "Code 10" error in its properties in 
Device Manager, call the IBM Help Center. They can provide you 
with a file to correct this problem.


================================
USING COMSPEC VARIABLES POINTING 
TO NETWORK COMMAND.COM FILES
================================

If you are on a network and are mapping your comspec environment 
variable to a network file server, you might see "Incorrect 
MS-DOS version" error messages. To correct this issue, map the 
comspec to a network location that contains Windows Me files or 
map the comspec to a local copy of the files. The MS-DOS version 
reported by Windows Me is 8.0.

====================
SAMBA AND WINDOWS ME
====================

For security reasons, Windows Me no longer allows you to send 
plain-text passwords; it sends only encrypted passwords. However, 
Samba servers require plain-text passwords, so you cannot connect 
to Samba servers unless you change a registry entry to enable 
plain-text passwords.

To enable plain-text passwords, add the registry entry 
EnablePlainTextPassword (reg Dword) 1 in the following registry 
location:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\Vnetsup


================================================
MIRAMAR SYSTEMS PC MACLAN APPLETALK CONNECTIVITY
================================================

In Windows Me, any change to the Network dialog box in Control 
Panel automatically removes PC MACLAN. To correct this problem, 
contact Miramar Systems, Inc., or carry out the following 
procedure. To prevent this problem from occurring, complete 
steps 5 through 7 only.

To restore Appletalk connectivity:

1. Click Start, click Shut Down, click Restart in MS-DOS 
   mode, and then click OK.

2. At the MS-DOS command prompt, type scanreg/restore, and 
   then press ENTER.

3. In the Microsoft Registry Checker list, select the file 
   whose date most immediately precedes the date of the change 
   you made in the Network dialog box, and then press ENTER.

   WARNING: Any changes you made to your system after that 
   file date are removed.

4. Press ENTER to restart your computer.

5. Using the Setup utility that came with the software, remove 
   Miramar Systems PC MACLAN.

6. When prompted, press ENTER to restart your computer.

7. Using the Setup utility, reinstall PC MACLAN.


====================================
NETWORKS NOT SUPPORTED IN WINDOWS ME
====================================

The following network systems are not supported in Windows Me. 
These networks may work after you upgrade to Windows Me, but 
Microsoft does not guarantee that they will work correctly.

- Vines16: All versions earlier than 7.1
- NetWare: Using Client for Microsoft Networks connecting 
    to server versions earlier than 3.11.
- Client32: It is recommended that you use Client32 
    versions later than 2.2.
- Client 32 for DOS/Win31: All versions.
- VLM/NetX: Monolithic drivers (ipx.com)
- Lantastic16: All versions
- Lantastic32: All versions earlier than 7.0
- Pathworks16: Not supported
- Pathworks32: It is recommended that you use 
    Lantastic 7.0 or later
- Backup Agents, Jetadmin Services: Versions shipped 
    with Windows 95
- TCP: 16-bit stacks

NOTE: Non-WinSock2 TCP/IP stacks are supported only on upgrades. 
These products do not function if installed on Windows Me.