General discussion


Mixed OS Networking

By jbrephan ·
I have a small Consumer Consulting Business. I often run across a small busness set of user's computers that often are running a mix of OS's. What i'm looking for is a primer somewhere on the internet that will get me started in understanding how tofix (troubleshoot)multi-OS ethernet networking in a 3-6 computer environment. Very often, one (or two)computers are running XP home or pro, others are running a variation of Win 95, 98, ME & 2000.

As yet, I simply do not understand how to speak the different Netbui, TCPIP etc., protocols. I can let Win XP Networking Wizard help on a XP network - but that's about it. Any suggestions on where to start?

Thanks in advance
J. Bradley Rephan
Argaine Consulting
Nashville, TN 37203
615.662.2277 Business
615.662.6644 Fax
615.300.9009 Mobile

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

Collapse -

Mixed OS Networking

by TheChas In reply to Mixed OS Networking

Item 1: NO business should be using XP Home in a networked setup. For security reasons alone, they should upgrade those PCs to XP Pro.

Item 2: Again for no other reason than security, Windows 95 and 98 should not be on a networked business computer. Unless, there is NO connection to the outside world from the network.

That said, here is my list of sites with good networking information:


Collapse -

Mixed OS Networking

by Curacao_Dejavu In reply to Mixed OS Networking

In addition; suggest to them to stick to 1 os platform. Your task will be easier when troubleshooting items, and keeping up with the security and update patches on so many different os's is ****.
Stick to 1 platform, use reliable/known nics (3com, intel for example, try to tick with 1 brand too)

MS is terminating support for win95/win98 and nt beginning next year. If you dont have the knowledge/experience with them I suggest again to upgrade to newer platforms, and (in my experience) stay away from winme.
It may sound too simple (I am/was there too).


Collapse -

by jbrephan In reply to Mixed OS Networking

Poster rated this answer.

Collapse -

by lumberjack In reply to Mixed OS Networking

Excellent advice from colleagues - cannot emphasise too much - work smarter - not harder

ie All Pcs to same O/S asap (and same patch level)
try to get the sytems to be as standardised as poss - may cost money but will save in manpower and cost in the long run.

As for reading matter etc - i have purchased a number of XXXXX for dummies - whether it be win2000, networking , TCPIP, excel ......
I have been in the biz for over 15 years and still dip into these regularly - and they are a light hearted but informative set of books

Collapse -

by jbrephan In reply to

Poster rated this answer.

Collapse -

by BCPower In reply to Mixed OS Networking

It's going to be hard to find information on the internet that will address your specific needs in its entirety.

I'm not really shooting for points here so let me suggest a different approach. Some of the issues you described here point to Microsoft exclusive technologies such as NetBeui. That's an obsolete technology that Win9x boxes often have to use. Strange things start to occur in a mixed OS envirnment. Many IT guys won't touch that. However, if you must address the issue, Look to the source - Microsoft. I use TechNet ( almost every day. There are mounds of articles in there.

As for networking in general, my alternate approach would be to study the OSI model and the TCP/IP model. These are the theories behind modern networking. Once you get a good idea of how applications, protocols and NIC cards talk to each other, you'll find troubleshooting will become more second nature. I took a Cisco CCNA class that was certified by the Cisco academy and got my CCNA certification that way. I highly recommend it to anyone in the networking field.

Here's where you can go to find out more:

Happy hunting and good luck in finding your answer. ;o)

Collapse -

by Choppit In reply to Mixed OS Networking

If you're going to read up on any protocol make it TCP/IP.

Related Discussions

Related Forums