Actually you can have Netbeui, TCP/IP and IPX/SPX enabled on Windows 95 and
Windows NT. They can all coexist. The question is why would you want to?
1. Netbeui is the protocol of choice for Windows NT and Windows 95. It is
the simplest protocol to set up. It either works, or it doesn't work.
There are no settings as in TCP/IP and it is the fastest LAN based
protocol for Windows.
2. TCP/IP is the protocol of the Internet, it is a UNIX protocol and
Windows 95 and Windows NT support natively. There is no reason why you
would not use it, as Windows NT provides tools to manage TCP/IP addresses
such as WINS, DHCP and now DNS. One you set it up, it works fine, lasts a
long time. You can also talk to other non-Windows computers via TCP/IP,
such as the HP 3000.
3. IPX/SPX is the language Novell lifted from Xerox these many years ago.
Windows 95 and Windows NT can handle IPX/SPX with no problems, as the
client is built into both operating systems. I recommend that you get the
Windows 95 Novell client from Novell though, as it is somewhat superior to
Mickey$oft's implementation. Suffice it to say that if you have Novell on
the network, you need IPX/SPX protocol to talk to it.
The issue comes with master browsers. Each protocol requires its own
master browser in order to be able to show the network neighborhood,
amongst other things. So, whilst it is neat to have all protocols enabled,
it is a load on the network as each system announces its existence on each
protocol to the protocol's master browser every 15 minutes. Also, you will
have a backup master browser for every 15 or so nodes on the network, per
protocol. The backup master browsers need to synchronize with the master
browsers at fixed intervals or about every 30 minutes.
Bottom line, keep the protocols used to a minimum. If you do not need
NetBeui, dump it. If you do not need IPX/SPX, dump it also. Keep only one
protocol, TCP/IP. Set up DHCP or BOOTP with DNS or WINS and live long and
prosper.
One last thing, if you have Windows NT servers on the network, disable
browser capabilities on you Windows 95 workstations. If left on, I have
seen a situation where the network gets confused about who is the master
browser, and elections are forced needlessly.
Kind regards,
Denys. . .
Denys Beauchemin
Hicomp America, Inc.
[log in to unmask] www.hicomp.com
(800) 323-8863 (281) 288-7438 fax: (281) 355-6879
-----Original Message-----
From: Tony Knowles [SMTP:[log in to unmask]]
Sent: Sunday, June 29, 1997 5:23 PM
To: [log in to unmask]
Subject: Re: Networking 102
I'm no networking expert, but I have managed to get my PC running
reflection for HP with NSVT to the HP3000. It was quite a struggle, I too
referred to Denys' excellent tips which I only found out about near the end
of my struggle!
I have IPX/SPX and TCP/IP configured but not NETBEUI which I read somewhere
that Win95 networking uses. Someone posted a message recently that
suggested that IPX and TCP/IP couldn't co-exist??
I didn't need to make any changes in NMMGR as all the networking stuff was
already setup. Look at NETXPORT.NI.LAN.PROTOCOL.IP and make sure that the
HP3000 has an IP address specified.
The steps I missed early on were having a PATH entry in AUTOEXEC.BAT for
the location of RNNSVT.DLL, after I installed Reflection this file was
named RNNSVTX.DLL, I just nenamed it. I have set up a HOSTS file in
C:\WINDOWS, but I think you can just plug the IP address of the HP3000 into
Reflection.
The only problem I still have is that when I start up a new Reflection
session, I always get prompted for a dial-up connection first, even though
I have set 'don't prompt for dial-up' in the dial-up networking program.
Now my challenge is to connect up the laset printer.
Tony Knowles [log in to unmask]
[log in to unmask]
----------
> From: Jim Phillips <[log in to unmask]>
> To: [log in to unmask]
> Subject: Networking 102
> Date: Saturday, 28 June, 1997 07:30
>
> Thanks to all for the help I've received so far! This is a great
> list! I've downloaded the HP3000-L FAQ (and finally learned how to
> pronounce Denys' last name! :-)), got to see Denys' great web page
> and learned how to install TCP/IP for WIN 95 (Thanks, Denys).
>
> Okay, so I've got TCP/IP running on my WIN 95 PC (at least I think so,
> can't connect to the HP3K, so who knows?). I go into NMMGR to configure
> the network and it wants the "Physical Path of LANIC". Using SYSINFO,
> in the IOMAP GENERAL HOST MAP, I see under "Channel Adapter 4" a
> "Local Area Network(4.3)", so that must be it, right? Wrong! That
> address is in use by the DTC's as shown by this error message when I
> exit NMMGR:
>
> Searching for subsystem validation routine VALIDATEDTS
> ---> Validation of DTS/LINK started. <---
> Path: LINK.TOL948
> The same physical path is being used at LINK.DTSLINK. (DTSERR=4)
> 1 Errors Encountered.
> ---> Validation of DTS/LINK finished. <---
>
> So, how do I determine what the LANIC path is? How do I know if I
> have a LANIC?
>
> You know, I remember seeing George Stachnik connecting a PC to the
> HP3000 in one of those video teleconferences and he didn't do any
> of this stuff! It was just plug the PC in and away we go! :-)
>
> Jim Phillips Manager of Information Systems
> E-Mail: [log in to unmask] Therm-O-Link, Inc.
> Phone: (330) 527-2124 P. O. Box 285
> Fax: (330) 527-2123 Garrettsville, Ohio 44231
|
