Can't ping or browse; Published Routes are In Conflict!

[bigkush]

Gateway Master (Host) - Gateway Local (join):
VPN connects OK, but can't ping or browse; Published Routes are In Conflict!

We installed Wingate and Wingate VPN on communication servers of our two offices. My

office has a join and the other has host configured.
The address range on one network is 10.0.0.0/255.0.0.0 (my side, gate: 10.0.0.2) and

on the other side (remote) 10.10.1.0/255.255.255.0 (gate: 10.10.1.2).
The link comes up, computers are visible on both sides, but ping and browse are still

not possible. Neither can we get a remote desktop access.
The only computer accessible is the one where WinGate and WinGate VPN are installed

and only via its public IP address (not 10.10.1.2). What can be the problem? How can

we see the network from other PCs? When trying to connect through remote desktop

connection I get the message: “The client could not connect to remote computer”
I have network participation enabled to the full network on both sides.

P.S.: In GateKeeper on our local office (where the join configured) in the Published

routes for remote office have mark (In Conflict).
On local office (join) in GateKeeper I see the following:
Local network of remote office [Master]:
Published Routes
--- <!> 10.10.1.0/255.255.255.0 (In Conflict)
--- <!> 10.10.1.2/255.255.255.255 (In Conflict)

[genie]

Your 10.0.0.0/255.0.0.0 covers the other range - therefore you have conflict of IP addresses - you have to re-number one of your networks to avoid this conflict.