Koozali.org: home of the SME Server
Legacy Forums => General Discussion (Legacy) => Topic started by: Troy Harrington on December 07, 1999, 01:52:40 AM
-
Here's my situation:
We have three buildings, all connected through a T-1 Line (building 1, 2 and 3). There is a Linux box (not e-smith) that acts as an IP Firewall/Router, a similar setup to E-Smith (didn't know about E-Smith at the time, otherwise we would have gone that route). It is our connection to the outer world and is physically located in building 2. A router connects building 1 with building 2 and a seperate router connects building 3 to building 2.
We have installed an E-Smith Box (also located in building two) to act as the Intranet Server... no outside access. In our first Linux Box I have configured it to recognize the E-Smith Server... no problem there. Where I'm running into difficulties is accessing the E-Smith Manager from any building other than bldg. 2. Also, getting Samba to show the e-smith server it too only shows in the building where it physically sits).
I have added the routing commands so that it's supposed to route through the routers to the other buildings.
in the "/etc/rc.d/rc3.d/S10network" file and it looks like this:
route add -net 192.168.1.0 netmask 255.255.255.0 gw 192.168.2.1 eth0
route add -net 192.168.3.0 netmask 255.255.255.0 gw 192.168.2.2 eth0
What do I need to change and where do I change it to be able to see the E-Smith Manager from anywhere on the local network and to see the server (Samba) from anywhere on the local network?
I've been beating my head against the wall for a couple of weeks now trying to tweak it, but no luck. Any thoughts/help would be greatly appreciated!!
troy
-
Can you ping the e-smith machine from the other buildings?
If you change the security setting for Telnet from 'private' to 'public', can you access with Telnet from the other buildings?
If yes to both, then your routing is OK and you need to review the security settings for SAMBA etc, if not, you must first get the routing correctly. It would help if you
gave us the actual IP addresses for all router interfaces and the IP used for the
e-smith machine.
-
Troy Harrington wrote:
> We have installed an E-Smith Box ...
> to act as the Intranet Server... no outside access.
...
> Where I'm running into
> difficulties is accessing the E-Smith Manager from any
> building other than bldg. 2.
The problem there is that anywhere other than the LAN connected
to the e-smith server is considered "outside access". You will
need to carefully open up the access lists for the web server to
be able to access the manager. Check out the design documentation on www.e-smith.org. The template you need to change is /etc/e-smith/web/panels/manager/access.incl.
> Also, getting Samba to show the e-smith
> server it too only shows in the building where it physically
> sits).
Getting samba servers to show up in the network neighbourhood
of remote subnets is a subject in itself. Go to www.samba.org
and read the samba documentation. Blame MickySoft if you don't
linke the way Windows networking works :-)
> I have added the routing commands so that it's supposed to
> route through the routers to the other buildings.
You won't need to add any route commands. If you have your gateway IP correctly set to the router's address you won't have to do anything more.
Charlie
-
Thanks! This information was helpful!!
I edited the /etc/e-smith/web/panels/manager/access.incl file and am now able to access the e-smith manager from any building.
I'll do some more investigating on getting Samba to work.
Let me say that I am very pleased with the E-Smith product and with the information that I find on this bulletin board.