Topic: Port Forwarding Mystery

[Hemeltje]

Port Forwarding on SME SERVER 6.0.1 doesn't work with my current infrastructure. I don't know the exact reason, but I'm sure it's a combination of SME, Motherboard and NIC.
- The ISP is not to blame; port forwarding (albeit only ports>1024) works fine with all kind of cheap firewall-routers.
- When changing the external NIC, I got a different result: with an old 3COM 10/100 Combo I got a "(111) Connection refused" message from SME. With a D-Link 630TX I simply got no connection. But in both cases, internet connection form the inside works ok!
- ClarkConnect does the job fine in both previous situations ( ?hum).
- The iptables -L gives the same result in SME and ClarkConnect.

I wonder now if there is a difference in software used between SME and ClarkConnect. But I removed ClarkConnect from the system now so I can't check.
Maybe an update to SME 6.0.1 can help? I only tested on a fresh install from CD.

All hints are welcome!

Peter

[CharlieBrady]

All hints are welcome!

It would help if you actually described your problem. What network setup do you have, what are you trying to do, what do you see, etc?

[Ness]

Hi... what is the D-Link 630TX? IO can't find it on the DLINK web site....

Chris

[Hemeltje]

I can't find it on the DLINK web site....

Chris

Ness, it should be 530TX.  
But it's been swapped out now for a 3Com...

[Hemeltje]

After I built a FreeBSD firewall and did some tests, I must decide that the problem is with the internal webserver.
All kind of machines are reachable from the outside, through my custom firewall or the SME firewall but not this one webserver!?
(the webserver IS reachable if I use a hardware -SMC or USR- NAT fw/router)

This webserver is a virtual FreeBSD 4.10/Apache 1.3 machine running on VMware GSX 3.1
A second virtual machine is a SME Server and that one IS reachable.

There must be some configuration option (VMware/FreeBSD/Apache?) that can fix this problem, I'm sure!  I want to use the SME firewall !