Topic: 2 nd network link to e-smith server

[Feyes]

I need help!! I've been battling for a week now to link the following 2 networks
I've got a e-smith server with 3 networks card setup as in the diagram.  My esmith -proxy server is set up as the 192.168.40.25

I followed Allen's How-to to install and add the additional card the 192.168.41.25.

  192.168.40.1 -- 192.168.40.n          
    ------------------------+-----------------------------------
                            |
                            |
                            |
                      ------+---------
                      | 192.168.40.25|
                      |                  |
                      |                  |192.168.8.2              192.168.8.1
                      |                 +-------------------------external router
                      |                 |
                      |192.168.41.25 |
                      ------+---------
                            |
                            |
                            |
  ------------------------------------------------------
  192.168.41.1 -- 192.168.40.n

But I have a problem whenever I allocate the local network rights as per his
last point and can't ping any card on the e-smith server or the 192.168.40 network.
I've tried to update the masq file and when I do it is possible to ping any of the addresses on the network but I still can't get access to the proxy server from the 192.168.41 network from my internet browsing software. All the computers on the original 192.168.40 net work can access the internet without a problem.

I’ve changed the computer, upgraded the software the only option now is that I'm missingsomething obvious. Any help will be appreciated

Thanks
Feyes

[Duncan]

I dont know if this will help but,

I have a similar setup. It simply worked with no real problems. The only reason i needed to adjust the Masq file was to get dhcp working on the third nic (so i dont see that you should have had to edit masq simply to get ping responses).

I did have problems if i tried to run the third nic as eth 0 or 1 as these are written into the system templates. I assume you are running your third nic as eth 2 (or other).

I found that i couldnt access the server manager on eth2 ip address (but could by pointing it at the eth 0 ip address).

Like i said, dont know if that helped - but it might give some clues.

Regards Duncan

[Feyes]

I solved the problem but still don't understand why it didn't work before. It can only be that I don't understand how TCP/IP works.

In specifying the local network I specified the "Local" address to allocate rights as the 192.168.41.0 with the IP mask as 255.255.255.0 with the router as 192.168.40.25.

As a last resort I decided to change the IP mask to 255.255.0.0 with the same router and suddenly I can see all the computers on the network.

As a test I decided to add the address 192.168.41.0 with the 255.255.255.0 mask as another  "local" network and when I did I could not access  any of the machines on the 40 network from the 41 network as well as none of the nics on the router computer. Now my logic tells me that If I assign rights to all machines on the network and then assign rights to a subset of those machines that I should at least get access to the subset.   Is my reasing wrong or is this the way TCP/IP works?

[Duncan]

Feyes wrote:
>
> I solved the problem but still don't understand why it didn't
> work before. It can only be that I don't understand how
> TCP/IP works.
>
> In specifying the local network I specified the "Local"
> address to allocate rights as the 192.168.41.0 with the IP
> mask as 255.255.255.0 with the router as 192.168.40.25.

No need to put anything in the router option. Just leave it blank. You would use this as an entry for an external router to the system.
 
> As a last resort I decided to change the IP mask to
> 255.255.0.0 with the same router and suddenly I can see all
> the computers on the network.
>
> As a test I decided to add the address 192.168.41.0 with the
> 255.255.255.0 mask as another  "local" network and when I did
> I could not access  any of the machines on the 40 network
> from the 41 network as well as none of the nics on the router
> computer. Now my logic tells me that If I assign rights to
> all machines on the network and then assign rights to a
> subset of those machines that I should at least get access to
> the subset.   Is my reasing wrong or is this the way TCP/IP
> works?

Again i think your problem was adding the router option. Try it without (it will come up as default) and see what happens.

Regards Duncan

[Boris]

>In specifying the local network I specified the "Local" address to allocate rights as the 192.168.41.0 with the IP mask as 255.255.255.0 with the router as 192.168.40.25.
>

your NIC on 192.168.41.0 was on the different network from router on 192.168.40.25 according to the mask 255.255.255.0 (first tree octets are the same and fourth different)
changing mask to 255.255.0.0 brings both router and NIC to the same network.

Do not overcomplicate this setup,  just remove the router ip and have it calculate the routes automaticaly. Change subnet mask back to 255.255.255.0 as well.

[Feyes]

Thanks that solved it. I knew it was going to be something simple.