🚀 go-pugleaf

Ahh, yes.  That reminds me of one more thing.

Windows offers you several different "networking protocols," including
NetBEUI, Netware-compliant, and TCP/IP.  It allows you to install and
use more than one of these at the same time.  Which is not, as it turns
out, a good idea.

You should adopt one, consistent protocol to your network, then use that
alone, removing the other protocols from all your workstations and
servers.  Microsoft Networking can run on top of any of these.  But if
you offer up a choice of low-level protocols, you're introducing more
complexity and more time.  Performance can be slower, and the system as
a whole, more unreliable.

Many installations use TCP/IP consistently, but what is appropriate for
you should be a discussion between yourself and your network technician.


>Robbie wrote:
[...]
> Not only VREDIR, I found I also had to update Winsock2 drivers on all
> W/S and the server. Mind you, the server in my case is just Win95. I
> had 4 W/S + 1 server and this was running fine. I then installed
> another 4 W/S's and found that W/S's were locking up at random with
> error an message of "Unknown internal Operating System Error".
> 
> After some discussions with a friend he advised updating to the Latest
> Winsock drivers. I did this 3 weeks ago, and there hasn't been a
> problem since.
> 
> thank's for you excellent TechTips...
> 
------------------------------------------------------------------
Sundial Services :: Scottsdale, AZ (USA) :: (480) 946-8259
mailto:info@sundialservices.com  (PGP public key available.)
> Fast(!), automatic table-repair with two clicks of the mouse!
> ChimneySweep(R):  "Click click, it's fixed!" {tm}
> http://www.sundialservices.com/products/chimneysweep