Hi Marcus, > 1 NETMEETING 1720 1720 192.168.0.5 > 2 NETMEETING 1503 1503 192.168.0.5 > 3 More 30000 30010 192.168.0.5 right until here... > 4 even more 5000 5007 192.168.0.5 What is missing here is the fact that these are UDP, not TCP. I don't wanna spoil your fun, but very very likely your router cannot do any UDP-forwarding. ;) > 9 ILS 389 389 192.168.0.5 No need to forward this. you don't run ILS on the internal network. For connections to ILS servers on the internet, you don't need a route back to your host. It works just like HTTP or SMTP... ;) > doing both for each port (only TCP would be quite sensless, eh?). Is there a > way to verify that? usually nmap comes in quite handy for that. But the general rule is, where there's no option TCP/UDP there's only TCP selected by default with no way to make UDP be forwarded. -- Best regards, Kilian
Attachment:
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil