Migrating to TCP/IP from netBEUI...

[Mini-Me]

Hi there.

I have a home network consisting of about 6 different PC's, connected to a 10/100 switch, all running the netBEUI protocol.

I want to change all these machines to TCP/IP, as I am thinking about JetStream(broadband), and netBEUI is not routeable.

Is there some PAINLESS way I can do this?
Every time I approach TCP/IP, it proves to be a pain in the preverbial backside to configure and get to talk.(which is why I am still using netBEUI!)

I DO NOT HAVE THE BROADBAND DEVICE yet, so in preperation for it, I wanted to get all the machines talking on the TCP/IP protocol first, as this could be a fine oppurtunity to teach myself how to get it to work.

However, I need a bit of a prod in the right direction.

IP addresses: what numbers can I put in there, that will make the network work?
DNS server: What do I put in these boxes?

I want ALL boxes on the network to have FULL ACCESS to every other box on the network(including write ability).

Little help?

[Erik]

The simplest solution for you will be to buy a router with a built in switch. Then the broadband modem gets connected to the WAN port, and PCs get connected on the switch ports. Set all of the PCs to obtain IP address information automatically, and make sure the router is setup as a DHCP server (usually the default behavior).

In this way the router will handle all of the IP addressing tasks and make sure that the PCs all get IPs that are in the same range. No headaches worrying about subnets, IP addresses, default gateways, etc. It will also provide a simple NAT firewall for your network to protect it from internet threats when you get broadband. Lastly it provides you with the ability to share the connection your ISP gives you, likely a single public IP, with as many internal PCs as you like (within reason).

As far as getting full access to all PCs it really would depend on what OS you are running. Generally though it is not a good practice to share everything on a drive, i.e. the whole drive including system folders. It is a much better practice to decide what things you want to have access from across the network, and then just allow those resources. Windows XP actually makes it difficult to impossible to give full control of system files over the network to help protect you PC.

[Mini-Me]

Thanks, Erik!!!
:)

Great idea...

I think I'll do that.(once I get the broadband modem and switch device)

4 boxes are XP Pro, 2 boxes are 98SE, and 1 box is the test-bench area(for fixing other people's boxes), and can be anything from 95 to Linux.

[Erik]

Most consumer routers come with a built in 4 port switch. If you go wireless you get a built in access point too for not much more (at least in the US).

As far as the PCs go it shouldn't be a big problem in terms of just sharing the internet. Creating a full network with file and print sharing between NT based systems and 9x systems can be a pain though.

My home network started somethin like yours, now I am on a 24 port Cisco managed switch, multiple VLANs and multiple servers. This way I can keep my machines seperated from a machine I am bringing into the network to repair. So basically if I just get a computer to fix I can plug it into a seperated VLAN that only has access to the internet, get any updates, run any scans, and not risk infecting my PCs with anything that might be on the PC I am fixing.