Debian network segment problem

[Nefarious]

Was not totally sure what to title this but it seemed like a funky title so I went with it.

I have two networks with an IPSec bridge and several 'dial-in' VPN connections. On one of the networks (segment 192.168.0.x) the server is working fine and you can SSH into the server and access its drives over the network (using samba to configure for windows access). Neither people on the other side of the bridge nor people who VPN in seem to be able to access the server. I have set up a port redirection so that SSH connections over the net should just be able to type in the static IP address and get straight in - this isn't working either.

Any ideas?

I must say I'm a little stumped, I could understand the bridge being a problem but people who VPN should 'appear' to be on the network as the same segment and should be treated the same as the computers that are physically there. I thought that it might be a problem with the router but when VPNing in externally I can reach other computer's hard drives and I would find it hard to believe that the router is singling out one IP address that it refuses to route to.

 

[AndrewP]

Any firewalls on the server/anywhere else, router NATing correctly if necessary and Samba being set up to allow the right hosts/segments would be things to look at.

I'd probably try tcpdump to see if any traffic (e.g. SSH forward or from VPN hosts) was reaching the server and check sshd_config and hosts.allow/deny for sufficient permissions.

 

[Nefarious]

given that both samba and SSH aren't getting through (and were previously) I think that it is a more global setup than samba or SSH settings (unless they were both altered by something at the same time).

NAT wouldn't be an issue as it manages the VPN and views those connections in as on the same segment.

Any more ideas?