Good. Phase one is completed: you are able to connect internally of the LAN.

And from the looks of your ipconfig output, your gateway is probably a router (Linksys, D-Link etc) that all machines on the LAN connect to, and which has a "special" connector for connecting a modem/cable box that gives shared access for all LAN machines to the Internet. Correct?

If so, then the important thing to understand is that your public (Comcast) IP is the IP address of the modem, not of any of the machines in your LAN.

Your modem is smart enough to send incoming connection requests to the router. (Since the modem is connected to only one device, it doesn't take much brains to do so.) The router, therefore, must be told what it should do with incoming connections.

That's where port-forwarding comes in. It's the exact same issues that Spasm mentioned many days ago, in his first post.

You must configure your router to forward incoming connection requests for the port your server is listening on, to the LAN address of the machine where the server is located. For your system, you must configure the router to forward incoming requests for port 6980 over to the machine located at 192.168.1.101

Your router probably has a convenient HTTP interface, for entering these settings, which you can find at http://192.168.1.1/ . If you do not understand how to effect these settings, then go to www.portforward.com , find the model of your router, and then follow the directions there.

Once the port forwarding is set, then remote users on the Internet can connect to your machine using the public IP address of your modem/router. They will need to enter the dotted numerical IP address.

Mike