This is quite surprising to me. I'm hoping someone has some insight. At first, I was so sure it couldn't be STN that I was reluctant to test if it was, but I finally broke down and did. I was having horrible timeout problems when playing Diablo on Battle.Net. At first, before I put in any port rules into STN, battle.net complained it couldn't work at all. I looked it up at battle.net online, and it needs port 6112, both tcp and udp. They were quite clear about that--no ranges, just the one port (on both protocols). So I put a "both" rule in STN's gui on that port, going to my one and only inside host playing Diablo. Diablo's battle.net no longer complained, and I was able to join games. Eureka! Or not. Most games I played, I would soon get kicked due to a network timeout. Some I played a while, but with noticable lag. I then buckled down and took STN out of the loop. Actually connected my 95 PC directly to the Internet. Voila!!! (And Eureka!, but for real this time.) No more lag problems, no more timeouts. Any ideas? pjb PS: Neither here nor there, but in my first non-lag Diablo game, some moron player promptly turned against me and killed me. Repeatedly. A FINE how-do-you-do. HRmrmrmrph. PPS: Any Diablo players out there? It was recommended to me I try to play in private (passworded) games to avoid this latter problem of other players HACKING ME TO DEATH! -- Visit http://www.ShareTheNet.com for info about ShareTheNet Visit http://www.topica.com/lists/sharethenet for info about this list _________________________________________________________ Enlighten your in-box. http://www.topica.com/t/15
