At my wit's end with a customer. Bear with me, this should be fun.
The customer had a web server and database server, with everything working fine:
Web Server -> scripting -> DB Server
Now he wants to put a server in the middle - a Windows-based server, no less - to "hide" it from the Internet. This server is NOT a web server, and will never be. It is intended to accept data from the public web server and run scripts to interact with the database server, then send a response back to the public server:
Web Server -> forward data --> Windows Server --> scripting -> DB Server
I understand this (can, or not?) be done with port forwarding, which I am clueless about. I'm a lowly web guy. I deal in the language of http protocol.
All I've been provided is an IP address beginning in 192, the private LAN IP of the middle-box. Of course you can't post a form to that. The networking geniuses that put this scheme together are ALSO clueless as to how it can be done and have dropped the task of "connecting" them in my lap.
The customer keeps talking with "network engineers" who tell him, sure, you can connect to the middle server, no problem. But not one of them suggests how to do this.
This is a long time acquaintance, I've avoided telling him this is a convoluted and frivolous solution when what he had originally was just fine. I'd like to do it for him but sheesh, how?
Has anyone got any resources that might expand my horizons sufficiently to help him out?