Anonymous wrote:
>> The work around is to set your game computer as DMZ host for the time you're playing online and then disable it again afterward.
I tried that with no success. I'm thinking of loading mtm2 up on the comp near the router and just going from the modem when nobody else needs the internet.
probably the best solution, personally MTM2 is the only game i cant play thru my router, all others play just fine. Thru my router, even with the DMZ, (without it it wont even connect) if i am the host, usually people wont be in the right trucks (lol) and we gotta go back to MP screen once or twice b4 it works properly (tho most ppl lose faith and would rather just a different host). I've gon ethrough a lot of routers to get one that I almost like, routers seem to be an under-developed technology still, either that or just under-tested for home networks. I believe i heard it was the NAT addressing that screws up MTM2 because that kind of technology in 1998 didn't really exist for home networks and you had better not have been playing at work so the makers didn't plan for it. Each frame that must go through a router keeps track of which port it went through, I believe the theory was MTM2 doesn't keep track of those numbers for each connected client so when MTM2 makes a reply to the request for a connection, it just sends to the IP and MAC it got when it received the frames, which of course ends off at your router, and you router sees no destination port in the frames and simply discards them.
Thats just the theory ive heard, I thought the NIC handled all the addressing and MTM2 simply is the application layer and doesn't handle the TCP/IP connection.