Ok, thanks for the help, but can't the server be refusing the port? An online service to check open ports said it was closed: Reason: Connection refused. I did: netstat -an, and it did list the machine as "LISTENING" on port 6118, but telnet 192.168.1.12 6118 won't allow a connection.

The firewall settings has an exception, and security configuration manager also has it listed as a valid port. I've done some of the things that other sites have listen, such as checking the router settings and whatnot, so any ideas why this port just won't give in?

When you say the problem isn't the port, it's the server, what exactly do you mean? The server must be refusing any attempt at a connection except through itself..

Nothing should be using that port. We created the entry in the port forwarding to be sure that it is to be used only for this server instance.

No. A while back I had a server written in VB.net to listen to the port, but now I'm messing around with a web socket server. The port 6118 is listed as a port to be allowed through windows firewall, on Windows Server 2003.