Hm. If you can use this public network, forget my complaint about private addresses.
So assumed, your network is OK, there could be a firewall thing - reread the thread and found:
I've tried iptables -nL and the result is
Chain Input (POLICY DROP)
Chain Forward (POLICY DROP)
Chain Output (POLICY ACCEPT)
I - sad to say - am not very fit with iptables. Just know some basics.
But I am nearly to sure, that this configuration is contraproductive for a server. If I see right, the input chain drops everything including http requests, ssh or telnet. Correct me, if I am wrong.
IIRC, open suse provides some gui tool for opening the firewall for several services. Did you try?
To give any hint for an iptables command, I have to google/man myself... I'd try and error on my own machine, but IO don't want to ruin your machine ;-)
Just kidding, after rebooting, iptables should be in its current state.