How to set up port forwarding for GlassFish on Windows Server 2008 and IIS7

As long as you have a static IP on the server and not DHCP'd through your router...if it's a home router as some have suggested...it should work as long as you have the proper port going to your server's services.

• Verify from within the network that you can connect to the services.
• Verify that you have the correct external address (www.whatismyip.com).
• Verify that the ports are "open" and not firewalled on the server.
• Verify that the ports are "open" from the outside (nmap is your friend, otherwise you need another service to scan your external IP)
• Restart the router to verify that the new settings "took". Shouldn't need to be done, but if it's an inexpensive router, you never know.
• If you have any logging available for particular services, check the logs to see if there's any connection attempts or anything showing up on the server side.

You might want to consider with those services (FTP especially) just putting the server in a DMZ. You're really kind of opening it to all sorts of hack attempts with the services you mentioned all on one machine and I personally wouldn't want it on the same subnet as my personal machines. DMZ it and you might have an easier time than individual port forwarding.

Does restarting the ubuntu server or the verizon firewall make it start working again temporarily?

To check the status of your firewall rules, use

sudo /sbin/iptables -nvL |less

what do you see there? Save that output right after restart and then compare to when it stops working - is some other process mucking with your firewall rules (via crontab maybe)? Seems odd, but that could explain the behavior you are seeing.