Small Business Network help

Associate
Joined
20 Oct 2002
Posts
1,127
Location
Redcar
Need some help on small business network setup.

Three companies share one business Internet connection in a multi tenant office space.

Two companies use the first wireless router, setup as a standard 192.168.1.x network with DHCP on. These two are just interested in Internet access and are non technical users.

A third company that is more technical and had a ‘tech guy’ (MD speak) who looked after things but has now left. Their network has started playing up, slow access and people not able to get a valid IP when connecting via wireless.

This third company have a second router at 192.168.1.100

This second router has a LAN IP of 60.1.10.1 with DHCP on

There is a wireless access point at 60.1.10.2 with DHCP off

Company 3 wants to secure a few servers and their local machines from the other two companies as well as resolving their DHCP connection issues, is this possible?
 
Sounds like the second router (ext 192.168.1.100, int 60.1.10.1) is protecting Company 3 from the others already. They'll only be able to see anything portforwarded on 192.168.1.100.

DHCP is correctly configured by the sounds of it. I'm guessing wired PCs are fine, it's just the wireless ones? I'd try assigning a static IP and pinging 60.1.10.1 just to make it's not a connectivity issue.

Btw. 60.1.10.1 is in use in China :)
 
I thought it was odd that somebody has chosen to use a public address for company 3 internal lan, what could it be changed to? 192.168.128.1?

I think the access point is bit ropy, they are using WEP for some reason, I need to check if the AP can offer anything else and get a list of the devices that connect before I see if changing it would be a benefit.
 
http://en.wikipedia.org/wiki/Private_network#Private_IPv4_address_spaces

Yup, I'd pick something random in one of the private ranges. Also, I'd ditch WEP ASAP. Even the 128bit version can be cracked in minutes. In the long term they could look towards getting their own broadband and a new all-in-one wireless router.

Btw. if they're running SBS the server should be running the DHCP (for the correct DNS settings used to find the Active Directory log in server).
 
WEP, yeah, I know :( I've only offered to take a look at what they have as a favour to the boss since their previous tech left.

They aren't running SBS, no domain to speak of at all. I'm a programmer really not a network admin so wanted to know how best to approach the network as that is their biggest problem in its setup.

I'll be offering advice to them, but mainly advising them to get a real professional to look at it and manage it.
 
WEP, yeah, I know :( I've only offered to take a look at what they have as a favour to the boss since their previous tech left.

They aren't running SBS, no domain to speak of at all. I'm a programmer really not a network admin so wanted to know how best to approach the network as that is their biggest problem in its setup.

I'll be offering advice to them, but mainly advising them to get a real professional to look at it and manage it.

I suggest they do get a tech in too, don't touch it if they are having problems they need someone who can fix it without questions.
 
Indeed - you might fix one thing but then anything else that happens will get shoved on your plate, even if totally unrelated.

I'd be looking to properly segment each company (which can be done relatively cheaply). Potential for a scenario like a PC from Company A picking up a virus/malware and resulting in Company B suffering downtime - not good.
 
Back
Top Bottom