Intranet setup: How to wire and organize the network?

Hey everyone,

So, I’ve got five computers set up within about 25 feet of each other. Each one has a USB Wi-Fi adapter plugged in just so they can grab an internet connection from a Wi-Fi modem located on the floor above us.

Right now, those machines are also all tethered by cables to our intranet (local network, 255.255.255.0).

Quick question for you guys:
I actually have an extra modem lying around, and honestly, dealing with all these tangled wires is getting a bit exhausting... so, does anyone know

1. if I can use this spare modem for the intranet, or maybe even repurpose the current one?
2. and if that's doable, would the existing Wi-Fi adapters work for this potential intranet setup, or am I going to need to pick up some additional ones?

Basically, I'm just trying to figure out how I might be able to pull this off.

You’ve got a few ways to play this. You could just extend that intranet out to the web and hook everything up to your ISP router.

Another way is using Wi-Fi for the internet while keeping the intranet on a hardwired connection. Honestly, if you're moving big files, wires are still king... much better than wireless.

Then there's that third option you mentioned—just slapping in another network card... maybe a Wi-Fi one. Not sure how well that'll actually work without testing it first, though. Windows isn't exactly known for being user-friendly when you give it too many networking choices. Dealing with multiple networks can be a total headache...

swiftowl7 said:I've got five PCs within maybe 25 feet of each other. Each one has a USB Wi-Fi adapter plugged in just to grab an internet connection from a modem sitting on the floor above.

you could just use those existing Wi-Fi adapters for that potential intranet setup

since everything is running through a single router, you basically already have an intranet
you just need to configure the computers so they actually realize it
as things stand right now, the machines probably don't even know the others exist (unless you're manually pinging them to see if they're still alive)
you'll need to put all the computers into the same workgroup and make sure user permissions are set up to allow resource sharing on every single one

otherwise, there's another way to look at this:
what exactly are you looking for from an intranet?
what's the actual goal here?

@ William Richardson12 & Michelle Bennett5

My intranet has basically just been used for file sharing between computers, printer sharing, and stuff like that in the past. It worked fine when everything was tucked away together. But now, I need to spread these machines out across two or three different rooms, and I’m really hoping to ditch the Ethernet cables if there's any way to make it happen. Honestly, cables just get tangled up, they're such a pain to manage, they create a mess, and they force my setup to stay cramped together—whenever I move a PC, the whole cable situation becomes a headache.

Data transfer can be pretty heavy sometimes; I might be moving 1,000 to 3,000 files in a single folder, though other times it's just tiny bits of data. The largest individual file is maybe around 1GB, but most of them are usually in the 10-300kB range.

Each computer handles its own specific job: one is for Desktop Publishing, another is for video and audio editing, the third is running a LAMP stack server, the fourth is for high-end video effects and 3D work like Lightwave, the fifth is for gaming and browsing (which I control via a KVM switch), and all of them have dual backup hard drives where each drive has its own IP on a 192.168.0.x subnet mask.

I also have three identical backup machines sitting in a closet. They aren't being used right now, but they serve as perfect spares; if one of the main rigs crashes, I can get a replacement up and running in an hour max, assuming I just swap the drives.

*****

Anyway, like I mentioned, I have an extra router lying around from my old ISP that isn't doing anything. I was thinking I could repurpose it as a dedicated "multi-switch" for the intranet, which would probably be a much cleaner setup. I haven't actually tried building this yet, but I'll likely need to pull the trigger on it in a month or two.

So, the idea is to have two routers upstairs: one for the Internet and a separate one strictly for the intranet.

It's worth noting that most of the machines are running Windows XP, while the Desktop Publishing rig is on Windows 2000 Pro. To be honest, that machine doesn't even need internet access, just the intranet. Running everything over Ethernet has been totally seamless so far, and I don't see any reason to bother installing new versions of Windows unless it causes major headaches. That Desktop Publishing setup reached its peak back on Win2k, and the video editing side isn't too far behind using Premiere Pro and VideoPad. The only recent hiccup has been working with H.265 (HEVC), but I'm sure we can figure that out. Audio is my main focus, though.

But here is the big question: what about USB Wi-Fi adapters? I don't have any PCI Wi-Fi cards, just those USB dongles. Do I need to have two separate adapters per computer, or can one handle both connections? My guess is I'll need two, but I actually have a few extra USB Wi-Fi adapters on hand. They're older models with antennas that I picked up for cheap on AliExpress, but they look brand new and work great. I'm just wondering about driver compatibility; since they're mostly "no-name" brands, even if they're Linksys, I might run into some issues. If they clash, I can always grab some from a different manufacturer, so it's not a huge deal.

Basically, here is the game plan:
1. Set up that spare router (which won't be connected to the web) to host the intranet network—I don't really know how to do that yet, so if anyone has tips, please let me know! And then...

2. Find some USB Wi-Fi adapters from a different brand and plug one extra into each PC so that Windows recognizes "USB-Wi-Fi-1" as the internet connection and the second one as the intranet connection.

Do you guys think this will actually work? Also, do you think Wi-Fi is going to struggle when I'm transferring large amounts of data?

And seriously... has anyone ever actually tried setting up a private intranet like this before?

Since you’ve already got a server and a backup rig, just run some Ethernet through the wall conduits. Put an outlet on every wall in those rooms and you won't have any more headaches...

You mentioned thousands of files up to 1GB each. That shouldn't be a Wi-Fi issue.

The thing is, wireless networks can get messy and unreliable. You're better off going with cables.

😉

You might be dealing with thousands of tiny little files—like a massive PHP site used for automation—but then you've got those random heavy hitters, too, like a 1GB video file straight from a camcorder or some movie you grabbed online.

Running cables through the walls just isn't happening for me; I’d honestly rather just mail everything out and set them up properly later, though I definitely want to give the Wi-Fi a shot first.

It isn't just me and the cabling causing headaches, because that switcher keeps acting up and messing with the power supply... honestly, it's probably easier to just deal with the wireless setup than to wrestle with this mess.

Let me give you a quick rundown on this:

1. Can I use this extra modem I have lying around for my intranet, or maybe even use the one I already have?

- Yeah, you could.

2. And if that's an option, would the Wi-Fi adapters I've already plugged in work for that potential intranet, or should I be looking at adding some more?

- The ones you already have should do the trick.

My setup:

It's actually pretty similar to what I've got going on; I'm big into the whole Smart Home thing.
For file storage, I run a custom DIY NAS, and I've got a dedicated print server for everything.
My network layout looks roughly like this:
1. VLAN
The gear I actually trust.
Tablet, phone, NAS.
2. VLAN
Alexa,
smart bulbs, and all that other random junk from unverified sources.
Plus Client Isolation,

But honestly, pulling all that off requires some decent hardware. 😁

swiftowl7 said:@ William Richardson12 & Michelle Bennett5

My intranet has basically just been for file sharing between machines, printer sharing, and that kind of junk. With Ethernet cables, it was fine. But now, I need to spread these computers across two or three different rooms, and I’d really love to ditch the cables if there's any way to do it. They get tangled easily, the wires are a pain, they create a mess, and you're stuck having the PCs right next to the cords. Move one computer, and suddenly the whole cable setup is a headache.

Data transfer can be pretty heavy sometimes—we're talking maybe 1,000 to 3,000 files per folder—but other times it's just tiny stuff. Biggest file might hit 1GB, but usually, it's more like 10-300kB.

The rigs all have their specific purposes: one for Desktop Publishing, one for video and audio editing, a third is a LAMP stack server, a fourth handles the fancy effects and processing for video, audio, and 3D (Lightwave), then a fifth for gaming and surfing, which I manage via a KVM switch. Every single one has dual backup HDDs, and each of those HDDs has its own IP on the subnet mask (192.168.0.x).

I also have three backup machines sitting in a closet. Hardware-wise, they're 100% identical to the others, but they just sit there. They're my "in case someone sneezes" backups so I can get back up and running in an hour max—basically just so I can swap the drives out.

*****

Anyway, like I mentioned, I have an extra router lying around from my old ISP that isn't doing anything. I figured I could use it as a "multi-switch" for the intranet, which would probably be even better. I haven't actually tried setting this up yet, but in a month or two, I'll likely need to pull the trigger on it.

So, upstairs, I'll end up with two routers. One for the Internet and one for the intranet.

It's worth noting that all the computers are running XP, while the Desktop Publishing rig is on Windows 2000 Pro—honestly, it doesn't even need the web, just the intranet. Networking over Ethernet works without a hitch. There's no reason to bother installing new Windows versions unless it becomes a massive headache. That Desktop Publishing setup peaked back in the Windows 2000 days, and video editing isn't far behind with Premiere Pro and VideoPad. The only recent hiccup has been dealing with H.265 (HEVC), but we'll figure that out eventually. And man, don't even get me started on the audio side.

But the main question is about USB Wi-Fi adapters (I don't have any PCI Wi-Fi cards, just the USB ones). Should I have two separate adapters per computer, or can one handle everything? My guess is I'll need two? Then again, the USB adapters aren't a huge issue; I've got a few spares. They're older, have antennas, and were cheap finds on AliExpress, but they look brand new and work great. Who knows what the drivers will say, though—might be some drama there. Even though they're basically "no-name" brands, I bought them from a few different sellers, mostly Linksys, but if they start acting up, I'll just grab something else. Not a big deal.

Basically, the plan is:
1. Set up that spare router (which has zero connection to the Internet) and configure it as the intranet network (I have no clue how to do that technically, but I'll try soon, so suggestions are welcome), and

2. Find some USB Wi-Fi adapters from a different manufacturer and grab one extra for each PC, so Windows sees the first USB Wi-Fi connection as the Internet and the second one as the intranet.

Do you think that could actually work? And by the way, do you think Wi-Fi is going to act up when transferring large amounts of data?

And... has anyone actually ever tried building an intranet like this?

Also, once everything is switched over to Wi-Fi, how am I supposed to connect to those HDDs where each one has its own IP (like in my current
Ethernet setup)?

I’m a little lost here: we’re talking about five different computers all within an 8-meter radius, spread across maybe two or three rooms, so I figured there were five people working.
Then someone brings up a KVM switch (how does that even work in this setup?), which makes it sound like one single person is just jumping between five different machines?
Or is this some kind of "cross-multitasking" madness where multiple people are rotating through a KVM at one workstation to manage several PCs?

Because honestly, sharing files or printers (or any other network gear/peripherals) is child's play, whether you're using a cable or Wi-Fi.

Just a thought: if everything is in one room—or even two or three adjacent ones—it’s basically one big local network. There shouldn't even be a debate on how to set it up: just run some wires.
Setting up ad hoc Wi-Fi is exactly that: ad hoc.

So the only real headache would be handling the internet connection:
- Run the intranet via Ethernet, assign static IPs so everyone knows exactly what's connected where, and call it a day.
- Plug everything into a single switch and route the WAN from there.
- Or, go the pro route and slap a Mikrotik on it to split things into two subnets: one Ethernet lane for the "fixed intranet" and another for everything "mobile"—phones, laptops, maybe even separate "home" and "guest" access.

In my book, standard Wi-Fi—especially those consumer routers you get from ISPs—is totally fine for casual home use. But business? Real work? You can't have it constantly breaking because someone's device grabbed the wrong IP address. Set it up right once, share the resources, and let it rip.
And don't even get me started on trying to run "parallel" networks—one for internet and one for the intranet, both over Wi-Fi. Based on what I'm seeing, that sounds like an absolute nightmare to manage. Trying to track down collisions or figuring out who's stepping on whose toes? Forget it. Everything should just run through one solid network.

John Cook72 said:Once everything transitions over to Wi-Fi, I was just sitting here wondering how we’re actually going to handle connecting all those hard drives, especially since each one currently relies on its own specific IP address to stay online.
I was just thinking about that whole situation with the wiring diagrams—you know, the ones where everything seems to be a complete mess of tangled lines? It’s funny how you can stare at a schematic for an hour and still feel like you're looking at a bowl of spaghetti rather than a functional circuit. I remember back when I was first messing around with some old hardware in my garage, I spent an entire Saturday tracing one of those chaotic layouts only to realize I'd misread a single connection point. It’s easy to get lost in the weeds! Anyway, what's your take on those messy schematics?

Thanks so much for reaching out about this, because I think I probably phrased things a bit poorly the first time around, so please excuse me!

I'm not actually looking to set up a whole Wi-Fi network here, more like...
- So, I was thinking about how to get a wireless LAN—you know, a solid WLAN or intranet setup—up and running. It’s one of those things that sounds complicated until you actually dive into it!

So, I was thinking about how to get five different USB Wi-Fi adapters or computers all linked up into a single intranet workgroup—basically making it function exactly like a setup using Ethernet cables. Does anyone know if a router is actually necessary to pull that off?

Man, I'm pretty sure that WLAN thing is just some fancy way of saying wireless local area network, right? 😁

Come on, someone please give me some actual helpful advice here! I really don't want to have to figure this all out on my own just to come back and post the answer myself later. 🙂

Michael Jackson10 said:I’m a little confused here—you’ve got five computers all set up within about a 25-foot radius, and since they're being spread out across two or three different rooms now, I figured there must be about five people working in that space.
So, then there’s the mention of a KVM switch—which makes me wonder how that setup actually functions in practice. Is someone really expected to spend their whole day constantly toggling back and forth between five different computers?

Not even related to the main topic, but in that specific room—you know, where those developers work—they’ve got this setup where they refuse to deal with five different towers, five monitors, five keyboards, and five mice cluttering up their desks. It would be such a mess! They clearly understand exactly why a KVM switch is a total lifesaver for a workspace like that.

Just as an example, once you’ve finished editing a video and hit that export button—which can easily take anywhere from thirty minutes to several hours depending on the project—there's really no reason to just sit there staring at the progress bar for five hours. I usually find it much more productive to just fire up a second computer and use a KVM to jump over and work on things like intros or quick teasers. Or, if I'm feeling particularly ambitious, I might even hop onto a sixth machine to start cutting another video entirely, set it to export, and then circle back to those quick edits once the heavy lifting is done.

Once you find yourself staring at a massive pile of old PC cases and a handful of laptops just sitting there waiting to be used for file transfers, it’ll become pretty obvious why managing all this hardware can turn into such a headache.

It’s actually a pretty straightforward question: So, I've been thinking about how much I hate seeing cables snaking all over my floor, and I was wondering—what's the best way to go wireless with my LAN setup and finally ditch all those wires for good?

And let me tell you, I don't want to hear any talk about running "parallel" networks where you have one setup for the internet and another for the intranet, both fighting over the same Wi-Fi signal. Honestly, that sounds like an absolute nightmare for anyone handling administration; trying to track down collisions or figuring out which device is messing with what would be such a massive headache. Everything should just run through one seamless network.

That’s exactly why I started this thread about how to easily—and safely—bridge a LAN connection wirelessly. I really wanted to create a space where we could figure out how to get even 10 or 15 computers all linked up without any major headaches.

I’m not saying the IT guys aren't doing their jobs, but honestly, I’ve had just about enough of them lately. It feels like every time we need to move a computer from one room to another—whatever the reason may be—it turns into this massive, recurring headache that just drags everything to a halt.