Moderator: pcwzrd13
Bob Dobbs wrote:@ Kazade:
I am just reporting my isms to assist in development. I do not know if PCwzrd13 informed you but anytime after I connect to Starlancer via GD-ROM, it kills my router when attempting to "join" or "create a game. It needs rebooting at that point. It is to note that no other "anything" does that, so this is isolated to this scenario. I also know that it will not allow me to "join" a game in PBA Tour Bowling although I can connect.
This is not a complaint, I am just reporting my results.
Xerxes3rd wrote:How does the lack of port-forwarding result in a stale TCP session? For a TCP session initiated by the client, port-forwarding shouldn't matter. For a TCP session initiated by the server, the connection should fail/timeout, but that shouldn't affect the router or client at all, right? Sorry if I'm misunderstanding the situation.
Shuouma wrote:Yes, that came out wrong, of course that will never establish a TCP session
due to missing port-forwarding. But so you know Xerxes3rd, Bob couldn't even
connect to the Gamespy until I added the dcgamespy software to 1.6, that is,
his ISP blocks TCP packets with certain flag combinations. So you have some
background if you want to help out
Bob Dobbs wrote:"The same thing happens when I create a game...run to the basement and reboot."
death_pixel wrote:Is dreampi 1.6 mandatory to have or can I stick with 1.5?
Users browsing this forum: No registered users