by Ark » Wed Mar 31, 2004 10:28 am
That is one of the most inefficient ways to set up GIT, regarding the lines telling you to:
- forward 'all well-known' IPX sockets
- forward 'standard' TCP/UDP ports
and
- look into which frame types: everything except SNAP
For starters, games typically only use IPX *or* TCP/UDP, not both.
You never want to forward all ports either, unless you are testing to find out what port a game uses, in which case you want to enable the logging options and find out what ports to use, then use just those ports.
Also, the frame types will effect whether or not your connection works - TCP/UDP only use Ethernet II (D.I.X. frame types) while IPX can use any of those 4, and depending on the version of windows a computer is using, the default setting of 'auto' may use 802.3 or 802.2. If two computers are using different frame types for IPX, they will never be able to communicate via IPX, even if they are on the same LAN, so they definately won't be able to via GIT. It is always recommended to manually set each computer to use 802.2 frame types, and then only use those in GIT.