Here is the problem:
192.168.X.X are private IP addresses. They are reserved for use inside a private network, not accessible from the internet. In order to reach the internet, all the computers on a network with a 192.168.X address pass through a gateway (a firewall, or router. Lets use router.). The router has an external IP address, which anyone on the internet can see. In the information you have just posted, your external IP address is 65.93.216.239. If you want your friends to connect to your sever, that is the address they need. But it isn't that simple...
<lecture on network address translation>
Say you are browsing the internet, donwloading illegal mp3's from some filesharing service, and chatting on MSN. To prevent all this network activity from getting all tangled up when it gets to your computer, each of these programs talk on different port numbers. When you are a client, it usually doesn't matter much what port number you have. When you make a request to google, your browser will randomly pick a port number and tell google (via your router) "And send the reply back to....oh...port 1025 will work for now".
On google, it is different. Since you are initiating the conversation with google, google doesn't have the means to tell you what port to connect to. That is why servers always use well defined port numbers. Web servers run on port 80 by default. Your web browser KNOWS that google will be on port 80, and so connects to that port for you by default. When you SSH to a website, you use port 22 by default. When you play counter-strike, you connect to some other WELL DEFINED port (27015?).
What the router does is something called network address translation, or NAT. When you want to view a website, say google.com, your computer sends a request to your router on some random port (say, port 1025), to be forwarded to google. Your router see a request coming from an internal address (192.168.2.1), and makes note saying "192.168.2.1 just sent a request to google from port 1025, so if I get a response in the next couple seconds, I'll forward the response back to 192.168.2.1 on port 1025". Google only sees a request from the external address 65.93.216.239, and happily replies.
When the reply comes back, your router will do exactly what it has promised: forward the reply to 192.168.2.1 on port 1025. That is how your Internet browsing works, or any "client side" application.
So why can't my friends just connect to 65.93.216.239 on port 27015?
If your friend tries to connect to port 27015, your router will say "Why is this guy trying to connect to my port 27015? I'm not waiting for a reply on 25535 to a request that one of my internal addresses (192.168.X) sent out. I'll just tell this dude whatever he's trying to connect to won't work."
What you need to do is configure your router to port forward. Tell your router "Anything you get from on the internet on port 27015, can you please forward that to my machine 192.168.2.1? Oh, and forward it to port 27015...cause that's what port my counter-strike server is running on." The exact steps to do this will vary, but consult your routers manual. Shouldn't be too hard to set up. You will probably start by browsing to 192.168.2.1 and finding the config area.
</lecture on network address translation>
Man, Saturday sucks when your drinking buddy has an office Christmas party.
.
