Thanks all,
There is somethings seriously wrong in my ebox which I am not able to
figure out.
I have decided to reinstall the whole lot.
Since I didn't have enough diskspace anyhow anymore.
I am able to connect through ssh by using this command:
iptables -I INPUT -p tcp --destination-port 22 -j ACCEPT
(inspired by an earlier comment of Javier Uruen Val)
I will use it to copy my files to an external harddisk and then will
copy back later on the newly installed ebox with more diskspace
Luc
Enrique José Hernández Blasco wrote:
El sáb, 08-12-2007 a las 13:22 +0100, Luc van Stappershoef escribió:
Ok,
The webinterface runs again, the fileserver runs ..... but the windows
network is unable to trace my ebox.
I had a network drive mapped to a users directory of ebox but I am
unable to reastablish the connection.
reaching the files through ssh (winscp) is also not working.
In the 0.097 version i could open ssh in the firewall I can't see this
option in the 0.11 version
anybody any clue ? what I can do ?
thanks in advance
Luc
Hi Luc,
The ssh service is open by default to the internal interfaces. It is not
already there, you may need to set up a new ssh service setting as
destination port to 22/tcp under Services menu entry. Then, add the
filtering Rule (Firewall -> Packet filtering) in "Filtering rules from
internal networks to eBox" by setting as service the new created one
with allowing policy.
Best regards and thanks for using eBox!
_______________________________________________
Ebox-user mailing list
[email protected]
https://lists.warp.es/mailman/listinfo/ebox-user
_______________________________________________
Ebox-user mailing list
[email protected]
https://lists.warp.es/mailman/listinfo/ebox-user
