Denys,
Thanks for the info, very helpful as usual. We have just switched over from
a Novell server to WinNT and now only have TCP/IP configured. I must find
out about DHCP, etc.
I have got my network laser printer going too, it was easy. Only problem
was I had to re-boot the 918. I tried IOCONFIG and SYSGEN followed by
DOIONOW and neither worked.
All the best
Tony Knowles [log in to unmask]
[log in to unmask]
----------
> From: Denys Beauchemin <[log in to unmask]>
> To: [log in to unmask]
> Subject: Re: Networking 102
> Date: Monday, June 30, 1997 1:36 PM
>
> 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
|
