Creating a TCP/IP network for a small (5 computer) office

[fastard]

Could someone point me in the right direction? Currently my lan uses NetBEUI for lan traffic and TCP/IP for internet traffic, but I'd like to ditch NetBEUI completely, as I've heard it might solve a lot of my current network woes. The problem is, I have no idea how to go about setting up a TCP/IP network.

I don't plan to have a "server", since we don't have any spare machines to handle it =) Well, we do have one Sony VAIO laptop that's a p200 with 32 megs of ram, but I doubt that would cut it.

Four of my computers run Win98 and the other runs Windows ME (it came bundled with the laptop and is used by my boss). Four of them are pentium 3/Duron 800 quality with 128+ megs of RAM, and the fifth is the receptionist's machine, which is an older machine that uses a p2 233 with 96 megs.

Currently we have a block of 6 IPs (1 for the gateway, so therefore 5 usable).

If anyone could recommend some documents or websites I could study up on to aid me in building this network, I'd appreciate it.

Thanks a lot!

-John

 

[Russ]

You already have TCP/IP on each machine? If so, and assuming the network is currently communicating (in other words, all the hardware works), do the following on each machine:

1. Remove NetBEUI.
2. Reboot.

Russ, NCNE

 

[Aves]

<< 1. Remove NetBEUI. >>
<< 2. Reboot. >>

LOL... Direct and to the point, I like it!

 

[Garion]

Since you use the word &quot;gateway&quot; I assume you are directly connected to the Internet with some kind of a small router.

Assuming that NetBEUI is your default network protocol you're now a miniscule bit protected against hacking from the Internet. Netbeui isn't routable so it's not getting onto the 'net. You still can probably get to your machines via IP, however, so you are open to a LOT of other nasty things.

In a small LAN with no routers to any other parts of the company, NetBEUI is, by far, your best bet. TCP/IP has a lot over &quot;overhead&quot; that needs to be in place to make it work well. Done best with some kind of NT/2000 server. You can still use TCP/IP for the Internet, just stick with NetBEUI for the LAN.

If you really ARE directly on the Internet, I'd think about getting a small cable/dsl router - They will give you room to grow, a lot of flexibility and very good security. For $100 you'll be happy you did and it will be money well spent.

- G

 

[JackMDS]

I don?t know if it is just my network.

Network with 6 computers (All 650MHz and up, 256MB memory, Win98SE), when the whole network is on TCP/IP, while two people use the Internet, and the other 4 use the network for regular office work, the network gets sluggish, and choppy.

I installed NetBEUI, and made it default protocol. Under the same condition, the Network is much smoother.

I assume that while two are surfing (TCP/IP), the rest are using NetBEUI, and there are fewer interactions between the action???

 

[Lightbulb]

Keep NetBEUI for connection between each PCs. Use TCP/IP for Internet connection on each PC.
Set the PC/device which connecting to the internet with using dial-up/ADSL/DSL/Cable.etc connection as the gateway.
Choose either DCHP for IP or static IP on each machine.

 

[L3Guy]

Fastard;

Before I agree with the other posters, what are the problems you are trying to resolve by
removing netbeui.

It was absolutely designed for 5 people and a laser printer, and works very well in that situation for the most part.

On the other hand, non-routable protocols cannot be tolerated, excused of even contemplated in this day and age on a large network. (sorry for the rant) Other options work well in this
sandbox, where netbeui does not.

HTH

 

[Garion]

Actually, exactly to the contrary, ! NetBEUI is designed to be used in a small, non-routed network win WinNT/95/98/ME to simplify the location of computers without requiring a more sophisticated locator service like WINS or static LMHosts files. With an unprotected broadband connection to the Internet, using TCP/IP as your primary sharing service is pretty iffy, especially given it's reliance on DNS. Your Internet connection goes down, so does your network (or you have to suffer through 30+ second delays to do ANYTHING).

Everyone likes to turn their nose up at NetBEUI. In larger environments where there's a server to centralize the TCP/IP network and run WINS/DNS you have no need for anything but IP. But for small peer-to-peer networks TCP/IP just adds a layer of complexity that's not really necessary. The small amount of performance that IP gives you over NetBEUI doesn't really justify the adoption of the more complex and difficult protocol.

One thing to remember above all else with Microsoft networking over IP. The box always goes first to the local LMHOSTS/HOSTS table THEN to DNS and finally to WINS or another locator protocol. I've seen this a million times - If you DNS is slow your network will be slow. If your DNS goes down your network is going to dog down and cause massive delays all over the place.

- G

 

[fastard]

Thanks for all the comments!

I don't care which network protocol I'm using, as long as it WORKS and can be kept relatively secure at a low cost =) I started with NetBEUI two years ago because we were on a 10base2 peer-to-peer inherited from a LanTastic network that only handled intranet traffic; all internet access at that time was via dial-up modem. Once we migrated to Windows 98, I needed to get the network running again, and NetBEUI was the easiest to learn in the time constraints I had. It got it up and running and since then had no problems. Because it worked, I saw no need to learn other protocols, since my time was needed elsewhere.

We then moved on to 10BASE-T and hooked it into what we use now, a LinkSys 16-port hub. A while later, we upgraded from modems to a partial T1, so I installed TCP/IP to handle the T1, while keeping the NetBEUI for intranet traffic.

Like I mentioned in a past post, I've been having network printer problems the last 2 weeks, which prompted me to think about reworking the network. I know it's not the printer's fault, or the printer server's fault, since I've tested multiple printers and multiple printer servers (and can print locally with no problem). Until 2 weeks ago, we were printing flawlessly, and then wham, the errors began. I have to get this problem solved, because it is killing our office productivity.

Anyways, thanks for the help! Any more comments are of course quite welcome! =)

-John

 

[Garion]

If you're on a hub you might ante up some cash to get a 10/100 switch. You can easily pick one up for under $100 (granted, not the greatest quality in the world, but it works). If you're having traffic-related performance problems this should take care of it.

Exactly what are the symptoms of your slowdowns? Slow to print, slow to bootup, slow to transfer files, slow to access the Internet, etc.? Do you have long delays and then things start to suddenly work again?

- G

 

[fastard]

Accessing the intranet for each PC takes about 10 to 20 seconds after first attempting to do so, but after that it's ok usually. Sometimes I'll have to type in the name of a computer (like //JOHN) in the Windows Explorer address bar to get Network Neighborhood to list all the computers in the network.

Transferring files is not a problem at all once the network connections are established.

Accessing the internet after bootup is instantaneous.

Bootup itself is fast for all computers.

As for the printing, it had been 100% fast and reliable until two weeks ago, when we started getting this error message when trying to print from any computer except the computer the printer's hooked up to:

There was an error writing to \\VAIO\HPLJ2100PCL6 for printer (HP LaserJet 2100 (Network VAIO)):
There was a problem printing to the printer due to an unknown system error.
Restart Windows, and then try printing again.
This printer will be set to work offline.
To save your print job in the local printer queue, click OK.

After clicking ok, the printer is set to Offline (if you go to the Printer Folder->Printer menu, there is an option to &quot;Use Printer Offline&quot; -- this becomes checked when I click OK). If I go to the Printer Folder->Printer menu and uncheck &quot;Use Printer Offline&quot;, then there's a chance the job will go through, but usually I get the same error message -- it might take 10 tries to get the job to go through, but lately nothing's going through at all.



What is odd is that sometimes jobs will go through with no problems, only to stop working again some time later.

For instance, we were able to print yesterday morning, but by the afternoon it was impossible. I stayed late after everyone had left and reinstalled the printer on every machine off the HP LaserJet 2100 cdrom.

That didn't help, so I uninstalled and tried again, this time using the latest drivers. I first installed the printer on the serving machine (which happens to be my desktop pc), using the cd to install the program files, fonts, etc, and then using the latest downloaded patch to update the drivers. I then went to each computer and installed the printer using Windows' printer installation module (instead of using HP's cd installation proggy). This time, every computer could print.

I left the office a happy man, but when I came in this morning, I found out no one could print again.

I tried a few things, including making NetBEUI the default protocol (as someone suggested above), but that didn't help things.

However, just an hour ago, the receptionist was able to print something. We tried it again from her machine, and she got the error message three times before she could print again. About 15 minutes later someone else tried to print, but to absolutely no avail.


I hope the above helps shed some light.

Thanks again!

-John

 

[Garion]

Excellent response, lots of detail. Here's a suggestion Get back to basics:

Remove TCP/IP on two computers, leaving just the NIC, Client for Microsoft Networks and NetBEUI on them. See if they can communicate with each other. If they can, it's an IP problem. If they can't, download the latest NIC drivers from the Internet for both and put them on the respective computers, delete the NICS from the device manager on both machines then re-install the NICs.

Configure those two to be on their OWN separate workgroup. If it still doesn't work, try a crossover cable between those two PC's. If that doesn't work, something is wrong with one of the PC's or the hub.

Once you get the two working together, try to add TCP/IP. Leave it with just an IP address/subnet mask/default gateway. No DNS! If that still works, try to add DNS. If that still works, repeat the process with the rest of the PC's, joining your new workgroup.

- G