![[Update]](icons/update.gif){kind=icon}
![[New]](icons/new.gif){kind=icon}
Date: Sun, 17 Sep 95 22:30:47 -0800
From: Rich Graves <[email protected]>
Say I want to connect to UTAH, my local NetWare server, but my default
protocol is NetBIOS and I also have TCP/IP enabled. Maybe I have
NetBIOS-over-IPX turned on, too.
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.
Date: Sat, 16 Sep 1995 00:18:10 -0700
From: [email protected] (John Robert Zaums)
Newsgroups: comp.os.ms-windows.win95.setup
Message-ID: <[email protected]>
References: <[email protected]>
[email protected] (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.
Date: Tue, 19 Sep 1995 10:18:27 -0400 From: Rich Graves <[email protected]> Message-Id: <[email protected]> From: [email protected] (Malcolm Newton) 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 [email protected] http://www.io.org/~mnewton VisiSoft Corp 2145 Dunwin Dr unit 11, Mississauga,Ont. Can L5L 4L9 (905) 607 6263 (905) 607 6122 fax
Date: Tue, 10 Oct 1995 10:18:27 -0400
From: Rich Graves <[email protected]>
You need to add frame types (like ETHERNET_II, ETHERNET_SNAP) manually. See
article Q124848
in the Microsoft Knowledge Base.
Date: Thu, 07 Dec 95 10:15:00 -0800
From: Rich Graves <[email protected]>
Let me count the ways:
HKEY_CURRENT_USER\Software\Microsoft\
Windows\CurrentVersion\Policies\Explorer
Add this dword: NoNetHood 00000001
Date: Thu, 07 Dec 95 10:15:00 -0800
From: Rich Graves <[email protected]>
Let me count the ways:
Date: Tue, 10 Oct 1995 10:18:27 -0400
From: Rich Graves <[email protected]>
In theory, you just open the Add/Remove Programs control panel, select
Windows Setup, and uncheck The Microsoft Network. However, this doesn't
always work. One thing you can try is reinstalling MSN, then
trying to delete it.
For more information, see the
Resource Kit or
http://www.creativelement.com/win95ann/.
Date: Wed, 27 Dec 1995 18:00:00 -0800
From: Rich Graves <[email protected]>
Exchange has the following idiosyncrasies that make it a poor Internet mail
client:
For more information, see http://www.creativelement.com/win95ann/.
Date: Wed, 27 Dec 1995 18:05:00 -0800
From: [email protected] (Ramesh Viswanathan)
Newsgroups: comp.os.ms-windows.win95.misc
Mike DeMarco ([email protected]) 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.
[Actually, if you use telnet more than occasionally, you should
dump Microsoft's exceptionally slow and buggy telnet in favor of the
vastly superior
CRT, WinQVT, or
Kermit 95.
I am told that it is only a coincidence that Windows-UNIX connectivity
worsens as Windows-NT connectivity improves.]
Date: Tue, 10 Oct 1995 10:18:27 -0400
From: "Peter Watt (Comtex)" <[email protected]>
Microsoft Office 4.3 leaves the file dialog.fon open when it closes. Win95
does not like this, and refuses to shut down.
Microsoft sources confirm that this is a problem with Win95 and Microsoft Office. Workarounds:
Date: Wed, 27 Dec 1995 18:25:00 -0800
From: Philip J. Koenig <[email protected]>
One thing you should be aware of... if you're running MS
Access -- it uses GOBS of record locks, and that alone can lock
up a Netware server.
There is a patch for 3.11 that solves part of this, and some parameters that should be used for any 3.x server. First, you must use the set utility from the console to set the "Maximum record locks per connection" to 10,000. (!) Also, you must set the maximum record locks on the server to the maximum, which I believe is 100,000. Due to Access's page-locking nonsense, it gobbles up huge amounts of locks... so much that MS's API built into their own MS-DOS (SHARE.EXE) is incapable of supporting the required number of locks... which means that any "Microsoft Compatible" NOS (i.e. LANtastic, Powerlan, 10Net, etc.) really won't fully support Access. I thought it was cute. :-)
Date: 1 Oct 1995 19:37:36 GMT
From: Charles Denny <[email protected]>
[This is off topic, but it gets asked so often...]
You need to buy or build a crossover cable. The following is taken from the
Data Communications Cabling FAQ:
10.0 Birds and Bees (Plugs vs. Jacks)
The EIA/TIA specifies an RJ-45 (ISO 8877) connector for Unshielded
Twisted Pair (UTP) cable. The plug is the male component crimped
on the end of the cable while the jack is the female component in
a wall plate or patch panel, etc. Here is the pin numbering to
answer the question, where is pin one?
Plug Jack
(Looking at connector (Looking at cavity
end with the cable in the wall)
running away from you)
---------- / ----------
| 87654321 | | 12345678 |
|__ __|/ |/_ /_|
|____| |/___|
12.2 Ethernet 10Base-T Crossover patch cord;
This cable can be used to cascade hubs, or for connecting
two Ethernet stations back-to-back without a hub (ideal for
two station Doom!) Note pin numbering in item 10.0 above.
RJ45 Plug 1 Tx+ -------------- Rx+ 3 RJ45 Plug
2 Tx- -------------- Rx- 6
3 Rx+ -------------- Tx+ 1
6 Rx- -------------- Tx- 2
I built this cable and everything works fine on my system. For more
information on the cables, refer to
http://www.cis.ohio-state.edu/hypertext/faq/usenet/LANs/cabling-faq/toc.html
and for more info on Ethernet, try
http://wwwhost.ots.utexas.edu/ethernet/toc.html.
Date: Wed, 04 Oct 1995 11:33:05 GMT From: [email protected]I don't know. Microsoft AT Work FAX won't work; see article Q130395 in the Microsoft Knowledge Base.
Date: Wed, 04 Oct 1995 11:33:05 GMT
From: Tag Carpenter <[email protected]>
The only way we can get Win95 clients to use Lan
Manager 2.X printer shares is this:
The best answer I have gotten on why the printer shares don't click is that there was some network printing stuff done by the old real mode redirectors which didn't make it into the Win95 "LM3" code. My guess? Another attempt by MS to force you into putting up NT servers all over the place!
Date: Unknown From: MicrosoftThis is just a minor bug with Setup forgetting to clean up after itself; it's not a problem. For an explanation, see article Q127970 in the Microsoft "Knowledge" Base.
Date: Tue, 3 Oct 95 15:29:31 EDT From: Kevin Lacy <[email protected]>I've been told that this is dangerous, but it helped at least a dozen people who had been declared hopeless cases by Microsoft "Technical Support." Most were getting random errors in VIP and VTDI.
If you installed Win95 over an existing Win3 (which is almost always a bad idea), try moving all *.386 out of your WINDOWS and WINDOWS\SYSTEM directories and rebooting. These are old Windows 3.1 VxDs; all Win95 VxDs have the new .VXD extension.
If this works, it means you have a virtual device driver conflict with something that Win95 Setup didn't recognize, and which you probably don't really need. You should either install Win95 again into a fresh directory (strongly preferred), or spend several weeks poring through your WIN.INI and SYSTEM.INI files.
Have a boot disk handy before you try this!!!
Date: Various
From: Rich Graves <[email protected]>
Nobody knows. This happens a lot. The workaround is usually to "log
off and log on as different user" (Nigel Mackintosh
<[email protected]>
and [email protected]
(Mike Stickney) found this workaround independently).
A possible hint:
Joe Ross <[email protected]> reported that he always gets a login prompt when there is a disc in his CD-ROM drive, but not when there isn't.
Date: Sun, 15 Oct 95 08:35:17 0700 From: MicrosoftMicrosoft Knowledge Base article Q135849: http://www.microsoft.com:80/KB/PEROPSYS/win95/Q135849.htm
Date: Sun, 15 Oct 1995 15:56:04 GMT
From: [email protected] (James Gerber)
The Resource Kit says there is support for several flavors of IBM's real-mode
LAN client DOS LAN requester including for LAN Server 1.3 and 2.0. It even
has a diagram of the layers of drivers used and tells you to install DOS LAN
Requester before installing Windows 95. Then you are supposed to select the
appropriate version of DOS LAN Requester from a menu during install. Only
problem is IBM is not even on the list! If you try to use DLR anyway, you get
crashes and lockups.
In fact, Microsoft and IBM had another one of their spats during beta testing and the effort to accommodate IBM's client was abandoned. Unfortunately, despite several bug reports, Microsoft never corrected the resource kit.
Date: 16 Oct 1995 21:30:56 GMT
From: Don Bourrie <[email protected]>
Nobody. But there are two DOS/Win3 stacks that are somewhat compatible with
Win95 (no "long" filenames, of course), and both are working on new
"Designed for Windows 95" versions. Maybe by second quarter
1996. Note that a Microsoft press release pre-announced the Win95 version of
MacLAN Connect on August 8th, 1995 -- ha ha.
Personal MacLAN Connect
Miramar Systems
http://www.miramarsys.com/
[email protected]
805-966-2432
COPSTalk
Cooperative Printing Solutions
http://www.copstalk.com/
404-840-0810
Date: Tue, 31 Oct 1995 21:08:33 -0800
From: Rich Graves <[email protected]>
On my PC, and on those of at least two other Usenetters, the system
will crash hard if left alone long enough for the energy-saving monitor
features to kick in while System Monitor or the SNMP Agent are running.
My PC has a Number 9 Motion 771 video card.
Date: Thu, 02 Nov 1995 15:47:28 -0600
From: [email protected] (Dave Andrews)
Message-ID: <[email protected]>
You can't. This useful feature was removed.
P.S. - They did this with Paintbrush too. I actually still use the old version of paintbrush.
Date: Mon, 13 Nov 1995 14:37:12 GMT From: [email protected] (Raymond Chen) Message-ID: <[email protected]> On Sat, 11 Nov 1995 19:27:47 GMT, [email protected] (Dave Wickberg) wrote: >It seem that my due to some error my recycle bin has disappeared, I've >tried fooling around with the registry but I can't get it back onto >the desktop, any ideas? Right-click the file C:\Windows\Inf\Shell.Inf and pick "Install", then log off and back on. This will reinstall all the standard shell gizmos (forgiving many registry sins).
Date: Tue, 14 Nov 1995 06:33:34 GMT
From: [email protected] (Patrick Moore)
Message-ID: <[email protected]>
Microsoft's answer, from
Knowledge Base article Q137454, is to delete the following
Registry entry:
HKEY_LOCAL_MACHINE\System\CurrentControlset\Services\VxD\vnetsup
You can delete it if you want, but if you have it in your old system.ini, or win.ini etc., it will just show up again and again every time you restart windows. Do a search of these files in your windows directory and remove any reference to vnetsup. Then remove it from your registry, ******** I would strongly suggest you backup your startup files ( four in all including msdos.sys ) before you change anything in your registry.
Date: Fri, 29 Dec 1995 20:10:00 -0800 From: VariousVincent P. Amiot <[email protected]> and others report that sleeping various kinds of laptops can cause crashes in NetWare or TCP/IP DLLs.
I and others have experienced crashes if the "Energy Star" monitor power-down feature kicks in while SNMP or System Monitor (SysMon) are active.
Various people have reported lost NetWare drive mappings when "Green" PCs go into suspend mode. They can only be reestablished by restarting Windows.
Date: 14 Nov 1995 17:22:51 GMT
From: [email protected] (Rob Philpott)
Message-ID: <[email protected]>
In article <[email protected]>,
[email protected] says...
>
>Can anybody tell me how I can perform a broadcast RPC from Windows95?
>The Win32 SDK documentation and MSDN indicate that a datagram protocol
>(either ncadg_ip_udp or ncadg_ipx) is required to support this, but
>neither appear to be supported under Windows95. The documentation
>from both sources listed above is vague on the subject of Windows95
>support.
Windows 95 does not support the UDP/IP nor the IPX protocols. Even if
the transport protocols were available (e.g. from a third party), you'd
still need the RPC transport support DLLs for those transports (i.e. the
RPCDGCn.DLL/RPCDGSn.DLL).
We've been requesting Windows 95 UDP/IP support from Microsoft for some time now. To this point, the answer has been "no". They don't perceive sufficient market demand for it to offset the development cost and the additional memory requirements that it imposes on the system.
Date: Fri, 29 Dec 1995 21:00:00 -0800
From: Rich Graves <[email protected]>
By default, Windows stores all network and dialup passwords in world-readable
.PWL files. Even if Microsoft successfully resolves the
serious .PWL encryption bugs that make
password storage totally insecure (which they have promised to do for Win95, but not
for Windows for Workgroups), this default "password caching"
behavior is inappropriate for many sites.
To turn it off for Windows for Workgroups, add the following to SYSTEM.INI [Credit Jim Carlson]:
[NETWORK]
passwordcaching=no
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\ Network\DisablePwdCachingThis gets a binary value of 1 [Credit Malcolm G. Miles].
Here's a simple RegEdit script to accomplish the above. Save it as NOCACHE.REG and run it from either DOS (in a network login script, for example) or Windows.
REGEDIT4 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Network] "DisablePwdCaching"=dword:00000001Note that there are *three* nonblank lines. The second nonblank line ends with the right bracket and the third starts with the double quote; what you're seeing is *not* a line broken at column 80.