
From: gordonf@vcn.bc.ca (Gordon Fecyk)
Newsgroups: comp.os.ms-windows.win95.misc,comp.os.ms-windows.setup.win95,comp.os.ms-windows.networking.win95,comp.os.ms-windows.apps.compatibility.win95,comp.answers,news.answers
Subject: Windows 95 Frequently Asked Questions and Answers Part 7 of 14
Followup-To: comp.os.ms-windows.win95.misc,comp.os.ms-windows.setup.win95,comp.os.ms-windows.networking.win95,comp.os.ms-windows.apps.compatibility.win95
Date: 14 May 1996 01:44:29 GMT
Organization: Vancouver Regional FreeNet
Lines: 1380
Approved: news-answers-request@MIT.EDU
Message-ID: <4n8oht$4r@milo.vcn.bc.ca>
NNTP-Posting-Host: opus.vcn.bc.ca
Summary: These postings list many questions asked in said newsgroups,
         and answers them as best as I can.  I make references to other
         Web sites and FAQs when appropriate.  Visit the WWW home of
         this FAQ (http://www.intouch.bc.ca/win95) for the appropriate
         links.  This section is the 7th one: Networking
X-Newsreader: TIN [version 1.2 PL2]
Xref: news.eunet.fi comp.os.ms-windows.win95.misc:144557 comp.os.ms-windows.setup.win95:12806 comp.os.ms-windows.networking.win95:8827 comp.os.ms-windows.apps.compatibility.win95:4350 comp.answers:17464 news.answers:61860

Archive-name: windows/win95/faq/part07
Last-Modified: 1996/04/29
URL: http://www.intouch.bc.ca/win95/faq7.htm

7) Windows 95 networking 

Windows 95 networking basics you MUST know 
How do I connect to... 
...other Windows 95 computers? 
...other Windows for Workgroups computers? 
...Novell NetWare (tm) servers? 
What do I have to do to a NetWare server to work with 
Win95 clients? 
NetWare 2.x 
NetWare 3.x 
NetWare 3.12 
NetWare 4.x and NetWare Directory Services 
How do I run DOS TSRs in a login script? 
Using clients from Novell (Client32, NETX, VLM) 
How do I connect to NetWare servers while I'm not 
running Win95? 
How can I receive NetWare popup messages? 
Bugs to watch out for, and patches 
How do I disable password caching? 
Top ten NetWare mistakes 
...Windows NT servers and Windows NT domains? 
How do I get Win95 to honor NT %username% ? (and 
other NT user variables) 
Bugs to watch out for, and patches 
How do I disable password caching? 
How do I log in to multiple domains? 
Top ten NT network mistakes 
...Banyan Vines( tm) servers? (Who uses this anyway?) 
...LANtastic( tm) servers? (Yes Virginia there IS a 32-bit 
LANtastic!) 
...AppleTalk (tm) AFP servers? 
...other network servers? (DOS client advice) 
The Internet? 
How do I share my hard drive or printer to... 
...other Win95 users? 
...on The Internet? 
...other Windows for Workgroups users? 
...other NetWare users? (Avoid if possible) 
How do I make RPRINTER work? 
...Macintosh (tm) users? 
...other computers' users? (SAMBA network clients) 
How do I print to HP JetDirect (tm) printers on the network? 
DLC protocol 
I heard that Win95 has (this cool feature). How do I set up... 
...system policies? 
...on a NetWare network? 
...on a NetWare network using NDS? 
...on a Windows NT network? 
...on another network with a 32-bit client? 
...on another network with a DOS client? 
...on a peer to peer Win95 network? (It is possible, but not 
easy!) 
...user profiles? (Requires system policies to work effectively) 
...on a stand-alone workstation? 
...on a NetWare network so it'll follow the user around? 
How do I make roving Desktop and Start Menus work 
on NetWare? 
...on a NetWare network using NDS? 
...on a Windows NT network so it'll follow the user 
around? 
...on another network with a 32-bit client? (Not possible on 
DOS clients) 
Why user profiles is a really cool and useful feature! 
...remote administration? 
...on a NetWare network? 
...on a Windows NT network? 
...on a Peer Win95 network? 
...user level access to shared drives and printers? (as opposed 
to multiple passwords) 
Windows 95 has (this security bug). How do I fix... 
...the "cancel" button on the login window? 
...the Samba bug I heard about? 
...the NetWare C$ bug I heard about? 
...the password caching bug? 
How do I disable password caching? 
How to enable user level access to eliminate the need to 
cache passwords 
Visiting Rich Graves' Win95NetBugs site for details 
Useful network utilities 
----------------------------------------------------------------------

Windows 95 networking basics you MUST know 

I briefly described NDIS 3.1 back in the Hardware section, but I'll 
cover it quickly here again. It's a Plug & Play version of Microsoft's 
Network Device Interface Spec, which lets you do cool stuff like 
dis-connect from the network when you un-dock your notebook, then 
re-connect as soon as you insert a PCMCIA network card, or dial in 
with your modem. 

Win95 has four classes of network components: Clients (For using 
shared resources), Services (for sharing or controlling shared 
resources), Transport Protocols (To communicate over network 
cards), and the network cards themselves. Protocols can use any 
network card, and usually, clients and services can use any protocol 
(there are specific dependancies, such as Client for NetWare on 
IPX/SPX Protocol). Clients are actually file system drivers, which use 
local caching (VCACHE) to off-load the server a bit. 

NDIS 3.1 software does NOT occupy conventional memory, so if 
you have all Win95 clients, services, drivers, and protocols, you can 
run your DOS programs within Win95 without worrying about how 
much RAM you have. This goes for IPX network games too. 

All net components in Win95 should conform to this, otherwise don't 
waste your time. This includes avoiding Novell's Client32, because 
they're forcing a 32-bit ODI, and .NLMs, and crap that belong in a 
NetWare server. Be Warned: I'm quite anti-Client32, and I tend to 
preach using MS's clients for the sake of simplicity and speed. If 
you have a problem with this, leave this page now. 
----------------------------------------------------------------------

How do I connect to other Windows 95 computers? 

Get a Win95 compatible net card for each machine, tie the cards 
together however they're supposed to tie together, and install these 
components on it: 

Client for MS networks 
Win95 net card driver 
NetBEUI Protocol (Or any single common protocol; NetBEUI's 
the easiest to set up, but IPX will get you a bit more speed) 
File & Print Sharing for MS Networks 

Usually, when you insert a net card for the first time, Win95 Setup will 
install Client for MS and Client for NetWare networks, and all the 
needed components, at the same time. After everything works you 
can remove un-needed stuff to make it faster. 

Use unique computer names and a common workgroup name in the 
Identification tab. To ease browsing difficulties, set aside one 
computer to be turned on all the time (the one that has the printer is a 
good candidate), and set "Browse Master: Enabled" on that machine's 
File & Print Sharing properties. 
----------------------------------------------------------------------

How do I connect to other Windows for Workgroups 
computers? 

Set up the Win95 machine as you would for networking Win95 
machines together. The WFWG machines use the same protocols, 
from the Transport protocol up, as Win95 does. On the WFWG 
machine, tell it to install Microsoft Windows Network support. 

Set aside one Win95 machine to act as Browse Master, as Win95 
machines take browse master precidence over WFWG machines. 
This will ease browsing troubles. Set that machine's FPS properties to 
"Browse Master: Enabled". 

NOTE: If you use IPX Protocol on the Win95 machine and you're 
connecting to WFWG servers, turn on "I want to enable NetBIOS 
over IPX", because the WFWG servers normally use NetBIOS over 
IPX. Otherwise change the WFWG station's protocol to "IPX/SPX 
Transport", instead of "IPX/SPX Transport with NetBIOS". 
Microsoft refers to this as Direct Hosting over IPX, rather than 
through NetBIOS, which explains the speed boost you'd get. 
----------------------------------------------------------------------

How do I connect to Novell NetWare (tm) servers? 

First, ask your administrator if he prepared the server for Win95 
clients. This is critical, if you want your administrator to like you. 

Then, Install Client for NetWare networks, and fill in the "Preferred 
Server" value in CNW's Properties. Set your primary login to "Client 
for NetWare Networks". 

Also, install IPX/SPX protocol (It will install automatically along with 
Client for NetWare), and select a frame type in its Advanced 
properties. Auto-detect does not always work. Your choice of frame 
type depends on what the NetWare server uses. NetWare 3.11 and 
earlier typically use 802.3, later servers use 802.2. 

The next time you restart, you will get a NetWare login requester 
asking for your name and password. When you feed it this, your 
NetWare login script will execute. 

More details for NetWare Directory Services later. 
----------------------------------------------------------------------

What do I have to do to a NetWare server to work with Win95 
clients? 

Many, many, people have crashed NetWare servers with Win95 
computers using Microsoft's Client for NetWare. A lot of this is from 
the client pushing the server, but a lot more of it comes from 
mis-understandings from users! 

The most critical thing to do to a NetWare server is to update its 
software. Old .LAN drivers might not keep up with the Win95 clients. 
An old '386 or '486 class server will also have troubles keeping up 
with Pentiums running Client for NetWare. Novell's VLM Client for 
DOS causes many of these troubles too. Details are at Rich Graves' 
Win95NetBugs site. 

Special notes for server versions below: 

NetWare 2.x 

Ensure you disable Packet Burst and long filenames on the Win95 
clients, by adding these lines to the clients' SYSTEM.INI file: 

[nwredir]
SupportBurst=0
SupportLFN=0

You can also use a non-burst frame type (802.3) and enforce no 
LFNs via system policies. 

NetWare 3.11 

These servers have a nasty time with Win95 clients using long 
filenames and packet burst. Use the NetWare 2.x techniques above, 
or apply PBURST.NLM and the OS/2 name space fix, available at 
Novell's NetWire site. Back up your server before powering up a 
Win95 client for the first time! 

Client for NetWare will not use long filenames on a NetWare 3.11 
server unless you explicitly tell it to, meaning you KNOW you have 
the name space patch installed. If you want to use long filenames on a 
patched NetWare 3.11 server, you should set up a system policy to 
enforce LFN usage, or include: 

[nwredir]
SupportLFN=2

in SYSTEM.INI. 

NetWare 3.12 

This, according to my observations, is a patched and bug-fixed NW 
3.11. This is the server that Microsoft did most of their client testing 
on, and it will work with packet burst and long filenames without 
patches. You still need the OS/2 name space to support long 
filenames. Set the frame type on the Win95 stations to 
Ethernet_802.2. 

NetWare 4.x and NetWare Directory Services 

If you don't need to use NDS and you have Bindery emulation 
available on the server, you can use the Client for NetWare as per 
NetWare 3.12 servers. The big catch is it won't recognize an NDS 
login script! To work around this, you can hand-copy the NDS 
system login script to SYS:PUBLIC and call it NET$LOG.DAT. 
Another work-around is to log into the server in Bindery mode (An 
option available in LOGIN.EXE, or just log in with regular Client for 
NetWare) and run a copy of NW 3.12's SYSCON to make system 
and user login scripts for Bindery mode. Details are in KB article 
Q128253. 

However, Microsoft released an NDS Service which will use NDS 
login scripts and work with NDS programs. Install Services for NDS 
by adding it as a Service (you still need Client for NetWare installed). 
Services for NDS is part of Microsoft's Win95 Service Pack 1, 
Admin Edition. You will also need the Shell32 Fix and the 
NWSERVER fix, which come with Service Pack 1, and six DLL files 
from Novell which come with the NetWare 4.x server. You will still 
need Bindery emulation for peer sharing (File & print sharing for 
NetWare) and Remote Administration. Set the User Level security 
provider to point to this server running Bindery emulation and you're 
all set. Or just don't bother with peer sharing via NetWare (Which 
you shouldn't do anyways except for Remote Administration.) 

I had the opportunity to finally try Services for NDS this week (25 
APR 96) and it appears to run just fine. After I hand-copied several 
DLL files from Novell's SYS:PUBLIC\CLIENT\DOSWIN directory 
to SYS:PUBLIC (Not just the six core DLLs that MS mentions) I 
could run NWADMIN and the other Win 3.1 NDS utilities in there. 
----------------------------------------------------------------------

How do I load TSRs from a login script? 

You can't. Win95 runs the login script from a single DOS session, 
which completely unloads when the login script finishes. Loading 
TSRs from a login script is stupid anyways, in fact, loading DOS 
TSRs in Win95 in general is stupid. 

But if you have to load network TSRs, Win95 did keep the old 
WINSTART.BAT capability. WINSTART.BAT, in the 
%WINDIR%, executes just after all the network components load, 
and just before the login prompt comes on. Load your TSRs in that. 
They will be available from all DOS sessions afterwards. Details are in 
KB article Q127794. 
----------------------------------------------------------------------

Using clients from Novell (Client32, NETX, VLM) 

I won't touch Client32 yet; you can read about it at Novell's Client32 
Home Page and make your own judgements. However, some 
applications need to see real mode NetWare clients (even though all 
the real mode hooks are there with Client for NetWare, and with 
Services for NDS). So... 

To use a DOS client, you will need all the regular DOS client software 
(LSL, IPXODI, etc). Once you have all that in place, you can add 
Win 3.1 support from Network Control Panel as a Client. 

NETX: Novell no longer recommends running NETX, but it does 
work as it did with Win 3.1. Install the DOS client, then add "Novell 
NetWare Shell 3.x" as a Client from Network Control Panel. Setup 
will prompt you for Novell's disks when needed. 

VLM: This works better with Win95 than NETX, and is "Safer" than 
Client for NetWare for your finicky programs and NDS apps. Try this 
as a last resort, if you can't get the app makers to clean up their 
programs. Use Novell's regular DOS installation of this client (Don't 
add the Windows software from Novell's setup), then add "Novell 
NetWare Shell 4.x and above" as a Client from Network Control 
Panel. Setup will prompt you for Novell's disks when needed. 

NOTE: Do NOT use Client for MS/File & Print Sharing for MS 
networks alongside a real mode Novell client! Neither Novell nor 
Microsoft support this, and the mix of real mode/protected mode 
clients can cause loss of hair for network administrators. Use all 
protected mode clients and services if you want NetWare logins 
AND peer sharing. Client/FPS for MS networks works great 
alongside Client for NetWare, and even Client32 from Novell. 

Client32? Well, I don't believe in it myself, because Novell introduced 
its server concepts to Win95; concepts that belong in the server. 
Read all about it in Novell's Client32 FAQ. 

At either rate, try to avoid this, unless you like seeing multiple 
instances of IPX or you don't use a notebook computer. If you 
update the server, Win95 clients can run VLM or Client for NetWare 
safely. 
----------------------------------------------------------------------

How do I connect to NetWare servers while I'm not running 
Win95? 

Win95 Network Setup installed a real mode client for NetWare at the 
same time as the protected mode one. If you exit to DOS ("Restart in 
DOS mode") or boot to "Command Prompt Only", and you're using 
Microsoft's Client for NetWare, you can log in to the NetWare server 
by typing 

NET START NWREDIR

at the DOS prompt. This will load a NETX compatible client using 
NDIS2 drivers and protocols. You can then change to your login 
drive and perform a normal DOS client login. Since it's only a NETX 
compatible client it can't perform NDS logins; so you could try: 

NET START NWLINK
VLM

Which uses Novell's VLM client, to do NDS logins. I haven't tried 
using Microsoft's IPX and Novell's client together, but in theory it 
should work. If it doesn't, you can always load Novell's net card 
drivers (LSL, etc) and VLM. 

NOTE: NWREDIR's real mode components take more conventional 
memory than a NETX client would, so you should only use this if your 
application can't run in a DOS session, or if you're performing any 
debugging. However, these components will automatically load high if 
you have upper memory available. You should prepare a special PIF 
file for this kind of configuration. 
----------------------------------------------------------------------

How can I receive NetWare popup messages? 

With Client for NetWare, use WINPOPUP. Add it from 
Add/Remove Programs/Windows Setup, in the Accessories 
components. Keep this loaded or you won't be able to see or send 
pop up messages. WINPOPUP will receive messages from Bindery 
and NDS clients, but you can only send messages to Bindery clients. 
Novell's SEND command in a DOS session will let you send 
messages to NDS clients. 

For all of Novell's clients, their supplied NWPOPUP works just fine. 
I'd even hazard a guess that NWPOPUP would work on Client for 
NetWare, but I haven't tried it yet. 
----------------------------------------------------------------------

Bugs to watch out for, and patches (and links to apprporiate 
Win95NetBugs pages) 

Automatic Frame Detection Bug: Auto detect does not always work, 
especially in multi-protocol networks. Bring up IPX properties and 
manually select a frame type. 

NWSERVER security bug: If you use Remote Administration, it may 
keep the admin share active after you dis-connect! Apply Service 
Pack 1 to fix. 

SAP Advertising kills IPX routing: When Win95 stations act like 
NetWare servers, all hell can break loose. SAP traffic can bog the 
network, clients might log in to a Win95 station instead of the real 
NetWare server. Don't use File & Print Sharing for NetWare to share 
out printers and files to non-Win95 clients; use the server and print 
queues like you're supposed to, or use Client/FPS for MS networks 
instead. More on print sharing via RPRINTER later. 

Password caching: Win95 will store your login password locally, and 
the password encryption is easily cracked! Apply Service Pack 1 to 
fix, or better yet, disable password caching and use User Level 
Security for peer sharing. Check out the System Policies part to find 
out how to do force this. 

Server self-destructs when booting Win95: Any general mishap that 
occurs to the server that either causes an ABEND or otherwise kills it 
(I won't get into technical details; all I know is that Win95's 
demonstrated that it does bad stuff to NetWare servers). Check the 
steps you need to prepare the server or dis-arm the Win95 client. 
----------------------------------------------------------------------

How do I disable password caching? 

Set up a system policy file, and include "Disable Caching of Login 
Password" or "Disable Password Caching". 
----------------------------------------------------------------------

Top ten NetWare mistakes 

10) Using a '386 machine as a server with Pentiums running Win95 as 
clients 

9) Installing File & Print Sharing for NetWare without knowing what 
you're doing 

8) Enabling long filenames on a NetWare 3.11 server (Patch it first!) 

7) Installing Novell's Client32 out of fear 

6) Using regular Client for NetWare to login to an NDS server 

5) Turning on SAP advertising in a large routed network 

4) Leaving "Auto-Detect" as the frame type for IPX 

3) Not specifying the prefered server in Client for NetWare 
properties 

2) Not updating the server before adding Win95 clients 

1) Not using system policies (Always a good idea to use system 
policies for basic stuff) 
----------------------------------------------------------------------

How do I connect to Windows NT servers and Windows NT 
domains? 

Microsoft released Windows NT 3.51 purely to support Windows 95 
clients. If you have Windows NT servers or workstations and Win95 
workstations, upgrade to NT 3.51. Save yourself the hassles. 

If you aren't using NT domains, you can connect to the NT 
workstations and servers as you could any MS Windows Network 
client; install Client/FPS for MS networks. 

Client for MS Networks can also perform NT domain logins, similar 
to how the NetWare client performs NetWare logins. You just 
specify that you want to log in to a domain in the Client for MS 
properties. You needn't specify the name of the domain controller; 
just the name of the domain. Unlike the domain client in Windows for 
Workgroups, however, you log in to the domain first, then into 
Windows. 

Upon re-boot, Win95 gives you an MS Client login prompt. Feed it 
your username and password, and your NT login script will execute. 
----------------------------------------------------------------------

How do I get Win95 to honor NT %username% ? (and other 
NT user variables) 

Win95 isn't Windows NT, so it can't receive NT user profiles which 
include the environment variables. However, there's a cool 
LanManager utility that works on NT servers: PUTINENV. 
PUTINENV copies all the LanManager user variables (including 
%USERNAME%) to a DOS client. But it only copies them to the 
local DOS session's environment; you will need to copy the variable 
to the global Windows environment with WINSET, a utility that 
comes with the Win95 CD-ROM. 

So, to copy the user variables over during a login, copy 
PUTINENV.EXE and WINSET.EXE to the domain controller's 
NETLOGON share, then add these lines to the login script: 

\\server-name\NETLOGON\PUTINENV L
\\server-name\NETLOGON\WINSET USERNAME=%USERNAME%

(Repeat the WINSET line for any other user variables in the user's 
NT profile.) 

You could also map a drive and run the programs from that mapped 
drive, or even from the client's local hard drive. Since Win95 supports 
commands using network paths, however, it's far easier to just copy 
them to the server. 

For interest's sake, PUTINENV also works with Windows for 
Workgroups clients, where Windows uses the same environment for 
all DOS sessions. Of course WINSET won't work, being a Win32 
program, but you could use the same script for WFWG and Win95 
clients without harm. NT clients will GPF on running WINSET, 
however. Read the note on Rich Graves' Site. 
----------------------------------------------------------------------

Bugs to watch out for, and patches 

Since Microsoft meshed Win95 and NT so closely together there are 
hardly "any" bugs, but Rich Graves does mention a few at his 
Win95NetBugs site. 

There's the Password Caching bug of course, but you can disable 
password caching. 
----------------------------------------------------------------------

How do I disable password caching? 

The best way is to set up a system policy which does so. You can 
disable caching of the login password, or caching altogether. 
----------------------------------------------------------------------

How do I log in to multiple domains? 

Although you can't LOGIN to multiple domains, LOGIN and 
ATTACH are two very different actions. You will need to establish a 
Trust relationship between the two domains, a topic best covered in 
Microsoft's NT Resource Kit. Once set up though, you can map 
drives to shares on the other domains through the login script, or 
browse through Network Neighborhood, as though they were part of 
your domain. 
----------------------------------------------------------------------

Top ten NT network mistakes 

10) Using a LanManager server as a domain controller (hah hah hah) 

9) Using an NT version earlier than 3.51 for Win95 clients 

8) Not using system policies (Always a good idea to use system 
policies for basic stuff) 

(oops... not enough mistakes to fill the list! You got any?) 
----------------------------------------------------------------------

How do I connect to Banyan Vines (tm) servers? (Who uses 
this anyway?) 

Banyan has a 32-bit client for Win95. By what I read on their 
installation instructions, it's a proper Win95 client for a VINES server. 
I don't have access to a VINES server, so if you have any insight on 
this, please tell me. 
----------------------------------------------------------------------

How do I connect to LANtastic (tm) servers? (Yes Virginia 
there IS a 32-bit LANtastic!) 

Artisoft has a Client for LANtastic, that pretty much works like Client 
for MS networks! You can map and browse server drives, share 
drives with the LANtastic service, capture and share printers, and 
have your connections saved per user, via User Profiles. Because they 
use the OS nicely, you could use the Client for NetWare, for 
example, and LANtastic client at the same time, if for some unusual 
reason you didn't want to use Client for MS for peer sharing. Now 
this is playing nicely! 

NOTE: Artisoft stopped offering their Client for LANtastic on 
their web site. Visit Artisoft's site or your favorite vendor for 
LANtastic for Windows 95. 
----------------------------------------------------------------------

How do I connect to AppleTalk (tm) AFP servers? 

Miramar Systems has a Win 3.1 client and server for AFP, which 
they managed to hack into Win95. Miramar told me via E-MAIL that 
they will release a Win95 client and server in June. With any luck it 
can co-exist with other Win95 components. 
----------------------------------------------------------------------

How do I connect to other network servers? (DOS client 
advice) 

Microsoft TRIED to allow weird DOS clients, with Win 3.1 support, 
to work in Win95 like they did in Win 3.1. Win 3.1 support for 
networks shows up as a stand alone Client in Network Control Panel. 
For example, if you install Novell NETX support, you don't need to 
add any protocols or net cards. The big limitation is you can only 
install ONE Win 3.1 network client. 

The best advice I can give is to only use the network support the 
vendor gives you. Don't try to use DOS clients alongside Client for 
MS Networks, for example. 

If you have to make more conventional memory available, you can 
use real mode HIMEM.SYS and EMM386.EXE, and prepare a 
normal DOS configuration that will start up before Win95 does. At 
this point it would perform much like Win 3.1 did, but it should work. 
----------------------------------------------------------------------

How do I connect to The Internet? 

Since Win95 comes with nearly all the components you need to 
connect to The Internet, the easiest way is to grab Microsoft's Internet 
Explorer and run it. The first time you run it, the Internet Setup Wizard 
comes up and asks you a bunch of questions only your service 
provider can answer. Get an answer sheet from your provider for 
these settings: 

Dial-in phone number 
Login Name (Not E-MAIL name); may include descriptors like 
%PPP or whatever 
Login Password (Whatever you chose when you signed up) 
IP address and Subnet mask if manually given, or use "My ISP 
provides me one" 
DNS server addresses (in the form of XXX.XXX.XXX.XXX) 
Full E-MAIL address 
Mail server address (usually something like mail.nowhere.com) 
Mail server username (Usually the same as your login name) 
Mail server password (Usually the same as your login password) 
Items to have handy: News server address, outbound mail server 
address, Gateway address (if not using default gateway) 

These are the items the Internet Wizard will ask you for. The Wizard 
will prepare IEXPLORE.EXE, the main Web browser, and Microsoft 
Exchange for sending and receiving electronic mail. It will also prepare 
a dial-up networking connection with all the right switches turned on, 
or off, and install all the needed components from your Win95 disks 
or CD-ROM. The only fine-tuning you'll need to do is to add the 
news server address to Internet Explorer (or whatever news reader 
you want to use), and maybe add an Outbound Mail Server name to 
Exchange's Internet Mail properties, if the provider has a different 
server to process outbound mail. 

About 99% of us will connect to The Net using a modem and a 
dial-up line, but for the rare few of us that have a direct network 
connection, the Wizard will work with that too. 

Oh yes, it will make you use Internet Explorer. No matter; just use it 
to get your favorite Web browser, such as NCSA Mosaic for Win95, 
or (ACK!) Netscape, and install that afterwards. 

You can always re-run the setup wizard if the provider's settings 
change, or if you change providers. You'll find it in your Accessories 
group on the Start Menu. I cover the rest of the Internet stuff in a 
separate page. 
----------------------------------------------------------------------

How do I share my hard drive or printer to other Win95 users? 

Install File & Print Sharing for MS networks in your network setup. If 
you set up the computer like I told you back in the How do I connect 
to other Win95 computers? section, this'll already be done. 

Next, right-click on any drive or folder you want to share, and select 
the "Sharing" menu. You can specify a read-only or full access share 
like you could in Windows for Workgroups, or make it dependant on 
password. 
----------------------------------------------------------------------

How do I share my hard drive or printer to other Win95 users 
on The Internet? 

This is pretty tricky because you need to run NetBIOS over TCP/IP. 
You can't just type "\\206.116.13.2" and expect a list of shared 
resources to appear. Running NetBIOS over TCP/IP usually requires 
a WINS server, but you can also do NetBIOS naming through DNS, 
or by manually writing an LMHOSTS file, neither of which I 
recommend. 

Your easiest bet is to obtain a free FTP server for Win95, available at 
www.windows95.com. Then the other user can just use their FTP 
client or browse using their web browser, using "ftp://206.116.13.2" 
as the URL. 
----------------------------------------------------------------------

How do I share my hard drive or printer to other Windows for 
Workgroups users? 

Just like you would for Win95 users. Be careful if you use User Level 
security, because WFWG clients won't recognize weird security 
providers, like NetWare servers. Either share out to "The World", or 
specify a Windows NT domain as your security provider, and have 
the WFWG client log into it. Or, simply use Share Level security a'la 
WFWG. 

NOTE: If you chose IPX as your base protocol between Win95 and 
WFWG computers, you should decide if you want to use NetBIOS 
or not, because WFWG has one default (NetBIOS ON) and Win95 
has another default (NetBIOS OFF). Neither WFWG nor Win95 
need NetBIOS over IPX unless you're specifically running NetBIOS 
apps, so on the Win95 machine have "I want to enable NetBIOS" 
turned off in IPX properties, and change the protocol on the WFWG 
machines to "IPX/SPX Transport" insead of "IPX/SPX Transport 
with NetBIOS". Microsoft calls this "Direct Hosting over IPX" which 
will give you a speed boost. Windows NT and Workgroup 
Connection for DOS also support Direct Hosting over IPX. 
----------------------------------------------------------------------

How do I share my hard drive or printer to other NetWare 
users? (Avoid if possible) 

Depending on wether the clients are Win95 clients or DOS clients, it 
can be either really easy or really messy! Complications include the 
SAP Advertising bug and the Login bug. 

If the clients are other Win95 machines running Client for NetWare, 
you merely have to install File & Print Sharing for NetWare networks, 
and specify your NetWare server as the security provider in Access 
Control. When you re-boot you can share out drives and printers to 
specific users in the NetWare server's Bindery. 

Now, if the client runs Win95 there's no real troubles, because Win95 
will perform "Workgroup advertising" which works like the 
workgroup naming service (browse master) in WFWG, and this won't 
interfere with normal NetWare communication. 

Beware if you want to share to non-Win95 clients via FPS for 
NetWare; you have to turn on "Service Advertising Protocol" (SAP). 
This is how NetWare servers become aware of each other, and if you 
turn on SAP for a Win95 machine, it will appear in SLISTs and 
SYSCON etc as NetWare servers. You can even get connection info 
(Server version: "Windows 95 4.00.950, 250 user") from SYSCON. 
Problem is, not only would SAP advertising by a lot of Win95 
systems cause a lot of network traffic, it could possibly kill any routing 
in an inter-network, and make DOS clients try to log in (as in 
Preferred Server login) to Win95 servers, which won't work. If you 
really want to screw up your network, share out your hard drive with 
the share name SYS and make a directory called LOGIN, and watch 
what happens. NOTE: Please don't do this, unless you LIKE 
getting beaten up by your network administrator. 

A better solution is to install FPS for MS networks and put either 
WFWG on the non-Win95 clients, or if they can't run Windows, 
Workgroup Connection for DOS. Both of these can run alongside 
Novell's NETX and VLM client software. OS/2 Warp Connect can 
load Windows and NetWare clients simultaneously as well. To save 
on memory on the DOS computers, consider using "Direct Hosting 
over IPX", which will remove the need to use NetBEUI and save 40 
KB of memory or so. The absolute smartest way, however, is to use 
a common space on the server. 

Now printer sharing is another story... 
----------------------------------------------------------------------

How do I make RPRINTER work? 

Oh no... you can't run RPRINTER.EXE on a Win95 station because 
you have to run it before Windows loads! Well, you could use VLM 
and RPRINTER together but what's the point of real mode network 
software on Win95? There is a better way. And no, running it from 
WINSTART.BAT doesn't work. 

Download and Install Microsoft Print Agent for NetWare. Add a 
Service from Network control panel and hit "Have disk", then tell it to 
look in ADMIN\NETTOOLS\PRTAGENT on the Win95 
CD-ROM, or wherever you extracted that download. Note that Print 
Agent will only work if you run Client for NetWare; it won't run with 
VLM or Novell's Client32. BE WARNED: MSPSRV was a last 
minute hack by Microsoft and doesn't have the re-connect 
features, etc of Client for NetWare. 

Just before you re-boot, change your IPX properties so you have 
Maximum Sockets and Maximum Connections set to at least 70, like 
RPRINTER/PSERVER's recommended setting of 

SPX CONENCTIONS=60

Now, also just before you re-boot, run PCONSOLE and create a 
new print server object. Add one printer to it named "Printer 0", set 
for Remote Parallel, LPT1 (Or just Parallel on NW 4.x servers). 
Attach it to a print queue on the NetWare server, if necessary, 
detaching the queue from any other print server object it was attached 
to. If you did detach it from an existing print server object, you will 
have to re-start that PSERVER, which usually means typing "unload 
pserver" and "load pserver xxxxxxxx" (whatever the print server 
object's name was) from the NetWare console. 

Now finally, re-boot the Win95 station and log in. Local printers on 
this station will now have a "Print Server" tab in their properties 
sheets. Be warned: This tab has bugs, so follow these six steps 
precisely! 

Select the Print Server tab and turn on "Enable print server for 
NetWare". If you get any evil error message just ignore it. 
Select the NetWare server with your new pserver object, from the 
DROP DOWN LIST, even if it was already selected. 
Select the pserver object you just created from the print server 
drop down list. 
Select how often you want this computer to check the queue for 
print jobs. The 30 second default is fine. 
Hit OK. 
Hit Start Menu/Shut Down, close all programs and log in as 
different user, and re-log in. Now all jobs in that NetWare queue 
will find their way to this printer. 

The reason you have to re-log in, is you will lose your drive mappings 
as soon as you OK those settings! MSPSRV is riddled with many 
dumb bugs, but Microsoft seems to swear by it. Check out KB article 
Q134747 for all the gory details. Every time you view this "Print 
Server" tab, it seems you will lose all your drive mappings. Re-logging 
in will restore them. 

You will also have to create a print server object for EVERY Win95 
computer sharing a printer this way, because each system becomes a 
PSERVER look-alike, with all the requirements of a stand alone 
PSERVER.EXE or PSERVER.NLM; the only difference is that it 
multi-tasks. You will also have to remain logged in to keep MSPSRV 
running, as logging out causes all programs to close, including 
MSPSRV. It will re-start when you re-log in, or cancel the log in. On 
machines with very active printers, you might want to consider setting 
their Default Login to "Windows Logon" with a blank password, so 
they automatically log in to NetWare on power-up, and re-enabling 
Automatic NetWare Login for those specific machines, if you disabled 
it via system policies. 

Oh yeah, one more thing: Don't try to capture LPT1: to a network 
queue if you're running MSPSRV to share a printer. This might have 
worked in RPRINTER, but it doesn't work here. Copy your printer in 
Win95 and have it point to the queue, if you're afraid of cutting in front 
of other people's print jobs. 

So to recap: Create a print server object with a single printer, for each 
Win95 computer sharing a printer through MSPSRV. Attach a print 
queue to each of them. Make sure you aren't capturing LPT1: to a 
network printer. Install MSPSRV on the Win95 computers sharing 
printers. Set Max Connections and Max Sockets to at least 70 in 
IPX/SPX properties. Re-boot to activate. Select the "Print Server" 
tab in the printer you want to share. Select the file server from the 
drop-down list and the print server object from its drop down list. Hit 
OK. Re-log in. And Pray. Heh heh... 
----------------------------------------------------------------------

How do I share my hard drive or printer to Macintosh (tm) 
users? 

Miramar Systems will include an AFP and ASDP print service with 
their MacLAN product, which they plan to release in June 1996. In 
the meantime, they managed to hack in their Win 3.1 Personal 
MacLAN into Win95. 
----------------------------------------------------------------------

How do I share my hard drive or printer to other computers' 
users? (SAMBA network clients) 

MS Windows Network has a short name: SMB, or "Server Message 
Blocks". SAMBA is a GNU public-license SMB client for Unix 
machines, with versions available for The Amiga and several other 
smaller systems. Visit one of many SAMBA FAQs, or visit the 
newsgroup comp.protocols.smb, or if you want to connect to Amigas, 
visit AMINET. If anyone of you fellow Amigans have ported the 
SAMBA client (Not the SERVER) to Amiga yet, please E-MAIL 
ME! 

SAMBA clients exploit a nasty file sharing bug in Win95 and 
WFWG; if the Win95 server shared out a directory, it will 
inadvertently share the entire hard drive with the same restrictions! 
Ack! Microsoft fixed this in Service Pack 1. 
----------------------------------------------------------------------

How do I print to HP JetDirect (tm) printers on the network? 

Win95 includes a JetDirect service, which allows you to control and 
attach to printers with JetDirect cards installed. HP JetAdmin depends 
on IPX protocol, so install that as well. 

Once you installed the JetAdmin service, you can print to the 
JetDirect printers like you could to any network print queue, but you 
cannot map a DOS LPT port to one. Read up on DLC Protocol 
below, to learn how to create new DOS ports instead. 
----------------------------------------------------------------------

DLC protocol 

I forget what this thing was originally written for... IBM 3720 
terminals, was it? HP takes advantage of this to connect JetDirect 
printers to print spoolers, though, so you can isolate the printer from 
outside network interference. 

First off, don't waste your time with the DLC protocol that comes 
with Win95. Download Microsoft's DLC32 Update and install that 
instead. Once you do, you will have a new port option in your Printer 
properties when you select "Add port", called "Hewlett-Packard 
Network Port". Once you select this kind of port, Printer Setup will 
ask you for a port name, and the Ethernet address of the JetDirect 
printer you want to connect to. You may have to reset the printer to 
have its address show up in this list. 

Once you connect to the JetDirect printer this way, you can print to it 
like any other DOS port, and you can share the printer, so your 
computer acts as print spooler for it. Of course you have all the other 
JetDirect advantages, like being able to re-locate the printer without 
moving any computers around, and wicked printing speed through 
Ethernet. 
----------------------------------------------------------------------

I heard that Win95 has System policies. How do I set it up? 

System Policies let you enforce a bunch of settings for Win95 
computers on a network. This is real handy to disable long filename 
support for NetWare, or disable password caching, for example, 
without going to each and every computer on the network and editing 
SYSTEM.INI or the Registry. 

Copy the contents of ADMIN\APPTOOLS\POLEDIT from the 
CD-ROM, to a convenient directory that only you (the Administrator) 
have access to. The first time you run POLEDIT, it will ask you for a 
policy template. Choose ADMIN.ADM. There are other policy 
templates for other networks (including NDS), but ADMIN covers 
most of the stuff for now. 

Have a nice look at all the settings you can enforce on, enforce off, or 
not enforce. Notice you have three choices; an "On", "Off", and 
"Don't Care"; the "Don't Care" state means that the computer will use 
the setting it already has. "Default User" refers to people, and you can 
add unique policies for unique users if you have a central security 
provider (like an NT domain controller or NetWare server) by adding 
users to this policy file. "Default Computer" refers to computers, and 
you can add computers here as well, named by the "Identification" tab 
back in Network Control Panel. 

Definitely set these policies up at a bare minimum: 

Network path for Windows 95 files 
Remote Update: Automatic (Use Default Path). Remote Update 
refers to updating local settings from the policy file, and Default 
Path refers to the location of the policy file itself. The default path 
depends on the kind of network client installed (Microsoft 
Networks, NetWare, LANtastic, whatever) and this "Automatic" 
option only works if you have a Win95 client for a central server 
of some kind. You can do non-central policies too, but I'll cover 
that later. 

Save this policy file with the name CONFIG.POL and copy it to the 
path your client expects to find it. 

POLEDIT also works directly on a local Registry, which is really 
convenient if you don't trust yourself with REGEDIT. 

...on a NetWare network? 

Prepare the CONFIG.POL file and copy it to your Prefered Server's 
SYS:LOGIN directory. Notice I wrote LOGIN directory, not 
"PUBLIC", as the Win95 Resource Kit erroneously states. The 
LOGIN directory is the only freely accessible directory on a server 
when not logged in to it, so it only makes sense! 

Additional useful policies for NetWare networks include: 

Disable/Enable Long Filename support (You have three choices 
here) 
Disable Password Caching 
Disable File and Print Sharing (Remote Administration still works) 
Disable Automatic NetWare Login 
Preferred Server 
Disable SAP Advertising 

...on a NetWare network using NDS? 

Microsoft's Services for NDS has some pretty cool extensions to this 
policy logic; you can enforce policies dependant on whatever level on 
the NDS tree you log in to, starting from servers, up to organizational 
units, all the way up to the Root. So, you can enforce Root policies, 
then policies specific to organizational units, then specific servers, 
etc... 

To add NDS policies, change your template to the MAPLE.ADM 
template included with Services for NDS. Then load your 
previously-made CONFIG.POL file and make the appropriate NDS 
policy changes. 

Bring up the server in Network Neighborhood. If you have Admin 
privelages, you can control the location of the policy file (and even the 
policy file name) for that server, or the organizational unit, or the Root. 
Right-click on the server/organization/whatever icon in Net 
Neighborhood and hit "Properties". Make your changes. 

Two very useful NDS policies: 

Load NetWare DLLs at Startup (To make dumb NDS apps 
work) 
Allow only NDS logins (To prevent User Profile screwups) 

...on a Windows NT network? 

Create the CONFIG.POL and copy it to the NETLOGON share of 
your primary domain controller. You can spread the policy file to all 
your backup domain controllers as well, in which case, the "Load 
Balancing" option can save some server overhead on slow WAN 
links. 

Useful policies for NT networks: 

Log on to Windows NT (Specify domain name here too) 
Workgroup (Use same name as the domain to ease browsing 
troubles) 
Disable Password Caching 
Enable Load Balancing (If you use multiple domain controllers per 
domain) 

...on another network with a 32-bit client? 

Other Win95 clients will have their own policy templates and their 
own unique location for the policy file. Check with the vendor for the 
details. If there's no default path, you can enforce the "Manual 
Update" policy and specify a UNC path to the policy file (like 
\\SRV\POLICIES\CONFIG.POL), but you will need to run 
POLEDIT on each station to set this in each Registry. Remote 
Administration can help here, so you don't have to physically do it at 
each station. 

...on another network with a DOS client? 

You will have to set the "Manual Update" policy and set a DOS 
Drive:\DIR\CONFIG.POL path on each station in each Registry. You 
will also need to map this network drive before running Win95 itself. 

...on a peer to peer Win95 network? 

If you keep one Win95 station on all the time (Usually the machine 
with the printer attached) you can put a policy file there. You will still 
have to manually change the Remote Update path in each station, but 
this time it can be a UNC path. 
----------------------------------------------------------------------

I heard that Win95 has user profiles. How do I set it up? 

User Profiles are a really, really, cool feature of Win95. Not only can 
you set a personalized desktop for each user and have personal Start 
Menus, but you can have personalized settings for MS Exchange, 
Word for 95, or pretty much any program that stores user 
preferences in HKEY_CURRENT_USER in the Registry! Profiles 
will also follow a user around in a centralized network, copying their 
program settings to each station as required. 

To turn on User Profiles, run the Passwords control panel. Regardless 
of wether you installed Networking or not, you turn on "Users may 
select their own preferences" on the User Profiles tab. 

Custom Desktops and Start Menus are actually one of these user 
preferences. You can enable or enforce User Profiles, but it's up to 
the users if they want their shortcuts to be unique to them. 

Regardless of user profile preferences, Win95 creates a Profiles 
folder, and a sub-folder for each user to store a personal copy of 
USER.DAT, the user portion of The Registry. If the user chooses to 
have custom Desktops and Start Menus, it stores them in that folder 
as well. Deleting shortcuts from Win95's default Dekstop and Start 
Menu folders will not affect a user's personal Desktop or Start Menu. 

Profiles work best when you have all Win32 apps, and if you keep 
copies of the apps in the local hard drives, that you install the apps in 
the same place on each computer! The "C:\Program Files" Directory 
is a good place for apps in a User Profile environment. Keep the 
Windows directory the same name, too. 

SOFTWARE DEVELOPERS: Be VERY VERY CAREFUL where 
you store your program settings! Hardware settings (like local cache 
directories or modem preferences) belong in 
HKEY_LOCAL_MACHINE, mobile and user settings (like 
bookmarks or spell check preferences) belong in 
HKEY_CURRENT_USER or in HKEY_USERS\Default! Test your 
software in a User Profile environment! This includes you, Netscape 
Communications! 

...on a stand-alone workstation? 

The Password Control Panel is always there, wether you have a 
network client loaded or not. In here, select the User Profiles tab, and 
select "Users can customize their settings". Specific users can choose 
to keep a custom Desktop and Start Menu included in their profile. 

When you aren't on a network and you have User Profiles turned on, 
you need to have a password for each user, otherwise it will happily 
automatically use the last password-less user's profile. Selecting "Shut 
Down" and "Close all programs and log on as different user" will let 
you enter your own name and password. 

...on a NetWare network so it'll follow the user around? 

Win95's Client for NetWare stores a user profile in their MAIL 
directory, so be sure you give each user one. SYSCON automatically 
creates a MAIL directory for each new user. The Win95 station 
copies their profile to the MAIL directory on log out, and reads it in 
on log in. 

You should enforce "Enable User Profiles" as a system policy, to 
keep multiple profiles straightened out. 

How do I make roving Desktop and Start Menus work on 
NetWare? 

The Desktop directory and Start Menu directory (which as you would 
recall here, are just a bunch of .LNK and .PIF files) get copied to the 
user's MAIL directory too, if they turned on "Include Desktop" and 
"Include Start Menu" in Passwords/User Profiles. Because Shortcuts 
have long filenames, you need to enable LFN support on the SYS: 
volume. This will only work on patched NW 3.11, NW 3.12, or NW 
4.x servers with the OS/2 name space installed. Enforce LFN support 
via system policies. 

You should also ensure you have enough space on your SYS: volume 
for the shortcuts! Microsoft recommended setting aside 150 KB per 
user, but my own custom profile eats 250 KB easily! 

...on a NetWare network using NDS? 

Services for NDS stores a user profile in the user's HOME directory 
instead of the MAIL directory, so make sure you define a home 
directory for each user, but the same rules regarding roving Desktop 
and Start Menu (LFN support, space requirements) apply. 

NDS clients can perform Bindery and NDS logins, so it is possible to 
have two sets of profiles for each user! You should enforce NDS 
logins only, via system policies, to prevent this mix up. 

...on a Windows NT network so it'll follow the user around? 

NT clients keep their profiles in their HOME directory, so make sure 
you define a home directory for each user, in User Manager. NT 
servers 3.5 or later have long filename support built in, even for FAT 
file systems, so you have no worries regarding roving desktops and 
Start Menus... just the space requirements. 

Also, enforce "Enable User Profiles" through system policies, to keep 
multiple profiles straightened out. 

...on another network? 

Roving User Profiles require a central storage space, and are specific 
to what network client you run. So the location of user profiles on that 
network depend on that client. This won't work with Client for MS 
networks without a Windows NT domain to log in to (So it doesn't 
work on just a bunch of Win95 machines together), but you can 
define a custom Desktop or Start Menu for each user, with 
POLEDIT. 

In Default User (Or whoever user) Shell settings, you can define a 
path for custom folders. The custom folders include Desktop, Start 
Menu, Programs, NetHood, and "Hide Start Menu Subfolders". So 
for each user (By selecting Edit/Add User) you can insert a custom 
path for these items. If you do this in one master CONFIG.POL file 
stored in one location, and you have "Remote Update: Manual Path" 
turned on, you can enforce a different Desktop and Start Menu for 
each user without a central server. Just make sure the path exists 
when Win95 starts (Either by using a UNC path, or by logging in 
before running Win95, in the case of real mode clients). 

If you also enforce user profiles through the central policy file as well, 
Win95 will store USER.DAT for each user on the machine, but it will 
not follow the user around. If you want the benefit of full roving user 
profiles, get a central server with Win95 client support, and check 
with the network OS vendor about user profile support, if it isn't an 
NT or NetWare server. 

Why user profiles is a really cool and useful feature! 

One time I read a question on how to make Netscape 2.0 work with 
more than one user's E-MAIL settings, so it would work with more 
than one provider. The answer was simply: Turn on User Profiles in 
the Passwords Control Panel. With that, Netscape had different 
settings for each user, and what was better, each user had their own 
dial-up networking preferences stored under their own profile! 

User Profiles is cool because it offers a central control for 
personalized settings, regardless of whose program you run! The 
software developer doesn't have to account for multiple users for a 
given program; they need only store personal settings in the 
USER.DAT portion of The Registry, and let the OS take care of the 
rest. I know this works with these programs: 

MS Office 95 suite 
Corel Graphics suite 6.0 
MS Exchange 
Netscape 1.2N up to 2.0 (You will need to fix the cache path for 
each user though) 
NCSA Mosaic 

Other programs Designed for Windows 95 had better work with this. 
----------------------------------------------------------------------

I heard that Win95 has remote administration. How do I set it 
up? 

The Passwords Control Panel has a "Remote Administration" tab that 
works only if you have networking installed. If you use a central 
server, you can assign administrative privelage (Or enforce admin 
privelages through system policies) to a SUPERVISOR or Domain 
Admin. 

First, install File & Print Sharing for either MS networks (for a pure 
Win95 or NT domain network) or NetWare (For NetWare 
networks). If you use FPS for NetWare, keep SAP advertising OFF. 
In addition, install the Remote Registry service from Network Control 
Panel, as a Service (in ADMIN\NETTOOLS\REMOTREG on the 
CD-ROM) on the remote machines. You can do this (and even 
enforce this) when you install Win95 as well. 

Now, if the workstations use User level security (highly advisable on 
NT Domains and NetWare networks), Setup will automatically 
enable remote administration for ADMIN and SUPERVISOR 
(NetWare) or DOMAIN ADMINS (NT Domain). If the stations use 
passwords instead of user lists (Share level security), or you don't 
have a central server, you will need to manually enable Remote 
Administration and supply a password to each station. Remote 
Administration settings will differ with each type of network client 
installed. 

Once done, you (the administrator) can control computers via 
Network Neighborhood. Right-click on any Win95 station and select 
"Properties". You will see a "Tools" tab that lets you edit the Registry, 
view network activity, or even browse the hard drives, on the remote 
computer. REGEDIT and POLEDIT also works on these stations. 

...on a NetWare network? 

Install FPS for NetWare or FPS for MS networks, install Remote 
Registry service, and enable User level security (No choice really for 
FPS for NetWare). Keep SAP advertising OFF. Re-boot. Then, 
from any other Win95 station, log in as SUPERVISOR or ADMIN 
(on NDS) and get properties on the Win95 station from Network 
Neighborhood. The remote stations automatically assign remote 
admin privelages to SUPERVISOR and ADMIN. 

There is one bug in Remote Administration, that makes the remote 
system keep sharing its hard drive, even when you end the Remote 
Admin session. Install Service Pack 1 on the remote station to correct 
this. This bug does not happen if you use FPS for MS networks 
instead of FPS for NetWare, but then you need to install Client for 
MS networks on the station you're administering from. There's no 
need to install two clients on the stations, really, so use FPS for 
NetWare, disable File & Print sharing controls (but not File Sharing 
itself) and SAP advertising via system policies, and install Service 
Pack 1. 

...on a Windows NT network? 

Install FPS for MS networks, install Remote Registry service, and 
enable User level security. Remote Admin privelages are automatically 
given to anyone in the Domain Admins group on the domain 
controller. Re-boot. Then, go to another Win95 station, log in as 
Administrator (or anyone else in Domain Admins) and get properties 
on the remote station from Network Neighborhood. 

...on a Peer Win95 network? 

Install FPS for MS networks, install Remote Registry service, and 
re-boot. Then run the Passwords Control Panel and assign a 
password for remote administration. Then go to another Win95 
station and bring up properties for the remote station in Net 
Neighborhood. When you pick one of the Admin tools, it will prompt 
you for the password. 
----------------------------------------------------------------------

I heard that Win95 has user level access. How do I set it up? 

User Level access spares us the potential of lost passwords and 
multiple, security-killing, cached passwords, because the passwords 
remain on the central security provider. You need only log in once and 
type your password once, and you have access to any resources 
shared on the network that have you on their access list. 

Enable User Level security from Network Control Panel, in Access 
Control. Pick a security provider (the name of an NT domain, 
NetWare server, or other central server if your client/service software 
allows for it). The next time you re-boot, all your share requesters and 
password requesters will have user list requesters in their place. You 
could also enforce user level security via system policies. 

If the server is a NetWare 4.x server, you will need to run Bindery 
emulation on it. This will allow all NDS clients access to any Win95 
stations sharing resources via FPS for NetWare. 

Unusual combinations to avoid: 

FPS for MS networks, using a NetWare server as security 
provider (WFWG stations can't get access then!) 
FPS for NetWare, using an NT server as a security provider 
(Quite impossible) 
FPS for NetWare, using Share level security (It won't let you) 
----------------------------------------------------------------------

Win95 lets me cancel the log in and still use Windows. How do I 
fix it? 

You can demand log in for Win95 access, through system policies, if 
you use a central security provider with a Win95 client. This way, a 
failed log in or a cancelled login will give "Unable to log you in" errors. 
Be warned: CTRL-ESC at a login prompt will bring up the task 
manager, so you will also want to remove TASKMAN.EXE from 
that computer. 

Win95 is not as secure as Windows NT, but some other security 
measures will prove useful enough to keep the bad guys out. These 
include: 

Remove the floppy drive from the computer once you install 
Win95 
Disable REGEDIT.EXE via system policies, and rely on Remote 
Administration 
Remove TASKMAN.EXE from the system; the task bar replaces 
it anyways 
If you insist on keeping the floppy drive in the computer, force it 
(through BIOS setup) to always boot from Drive C. 
Password-protect your BIOS setup too. 
Edit MSDOS.SYS to prevent Safe Mode booting, force the 
system to always boot into Win95 on power-up, and to set the 
boot delay to zero. 
Hide components of the Control Panel, such as Network, via 
system policies. You can hide quite a few Desktop components 
via _system policies_ too. Check them out. 
----------------------------------------------------------------------

Win95 has this Samba bug. How do I fix it? 

Install Service Pack 1. Or just disable the binding to File & Print 
Sharing for MS Networks to TCP/IP. Bring up TCP/IP properties for 
each net card, hit "Bindings", and turn off the binding to FPS for MS 
networks. 

Microsoft claims this bug happens when Samba clients issue "Illegal 
network commands" to the computer acting as a server. Fact is, this 
bug was in WFWG originally, and I suspect it's even in NT Server! 
Rich Graves has all the gory details. Microsoft seems to have many 
troubles with Samba clients and servers; there was even a Client for 
MS networks update in Service Pack 1 that fixed troubles with 
Win95 accessing a Samba server. 
----------------------------------------------------------------------

Win95 has this NetWare C$ bug I heard about. How do I fix it? 

This bug creeps up when you perform Remote Administration on a 
Win95 computer that uses File & Print Sharing for NetWare. The 
Admin share (\\machine\C$) remains active, and users can connect to 
it by typing that UNC path. Install Service Pack 1, or do without 
remote administration. 

This was another bug that Microsoft danced around. Again, Rich has 
the details. 
----------------------------------------------------------------------

Win95 has this password caching bug. How do I fix it? 

Install Service Pack 1 or disable password caching via system 
policies. 
----------------------------------------------------------------------

How do I disable password caching? 

Password caching only happens if you have a Win95 network client 
installed, OR you have User Profiles enabled on a stand alone 
computer. 

The clients for NetWare and NT have separate caching restrictions 
(such as "Prevent caching of log on password") you can use, or you 
can disable password caching entirely, in the Network section of 
POLEDIT. 
----------------------------------------------------------------------

How do I enable user level access to eliminate the need to 
cache passwords? 

Read all about it in User level security. You will need a central 
security provider (like an NT domain or NetWare server) for this 
though. 
----------------------------------------------------------------------

Visiting Rich Graves' Win95NetBugs site for details 

He's at http://www-leland.stanford.edu/~llurch/win95netbugs/faq.html 
and while he's very anti-Microsoft, he does present the facts. 
----------------------------------------------------------------------

Cool software for Win95 dial up networking, and other Winsock 
and network apps 

Visit http://www.windows95.com for a lot of 32-bit apps, utilities, 
hacks, whatever, that will make your networking life easier. 

Also visit http://www.cwsapps.com for the Consumate Winsock 
Apps list; the original. 
----------------------------------------------------------------------

[Back to Table of Contents]

