Discussion in 'Windows Server' started by Simon3264, Feb 6, 2012.
You need to login to view this posts content.
Hand drawn diagram would be helpful
To you it might be all logically setup, but reading it, does not sound as the cleanest of solutions to understand
Yeah, sounds like a routing issue.
The server can probably access the 192.168.10.0/24 network because it has an IP in that subnet and so it doesn't need a gateway/router to it. Anyone not in 192.168.10.0 see it it as a remote network, so they'll attempt to reach it via their default gateway (10.0.0.1). I don't know the Kerio software, but presumably it's missing a setting that allow s it to forward from 10.0.0.0 to 192.168.10.0.
@Sebus: you are in right, so there is a small sketch of my physical network with configs beside.
I didn't include the virtual machine because the problem is not related with it (it was here before I install the VM).
@100: I will check in depth the manual of Kerio, but does my routing table seems ok?
Yeah, the routing table looks good. Since you can access both LAN1 and LAN2 from the server directly the routes work. It just seems like there's something preventing routing between them, some additional rules requiring setup in Kerio perhaps?
What is the IP of the server you are pinging?
"If I ping a LAN1 IP since my server it works and vice versa" * you mean from, right?
Routing between LAN1/LAN2/WAN is done by Kerio?
Yes, sorry: If I ping "form" the server itself.
Routing seems ok in the routing table:
LAN1, LAN2 and WAN have their parameters in the routing table: network, mask, interface, metric.
I tried adding a static route by trying several settings but it did not work...
Thanks for support
[guote]If I ping a LAN1 IP from my server it works and vice versa[/quote]
I assume you do it from server console (directly attached?)
This proves nothing as the server pings itself (so it will always work as it does not go via any routing)
That means that routing does not in fact work, so it points to Kerio setup
You will best to have Wireshark installed & see what packets get dropped on what interface
thanks for support:
I tried Wireshark while i do a ping and destination IP is random and it is unreachable, so it seems to be a routing issue.
The test was done on a LAN1 computer, with 192.168.10.2 (e2000) as ping destination.
Ill check the manual of Kerio, but the config seems OK...
I temporarily solved the problem:
I have an old router (Dlink di-604), i settled the WAN as 192.168.10.3/255.255.255.0 Gateway/DNS 192.168.10.1 and LAN as 10.1.1.1/255.0.0.0.
The Wan cable is plugged in a LAN plug on the e2000 and the Lan plug is plugged on a switch in LAN1
So on computers in LAN1 (10.0.0.0/255.0.0.0), when i need to access 192.168.10.1, 192.168.10.2 directly for administration, I just have to change the Gateway from 10.0.0.1 to 10.1.1.1 by keeping the same IP/mask/DNS and all works. When the administration task is done, i switch back to DHCP.
I know it's not clean but it works for now till i find the problem.
Thanks for support anyway