Page 1 of 1

Wrong Port Number error in unforwarded log

PostPosted: Sun Dec 23, 2007 12:00 am
by jcanker
We are trying to get GIT to work in order to play Joint Ops.

The status screen appears as if we are making a connection/handshake with each other--we get last packet sent/received data that updates with the new time when we hit refresh; however neither of us can see a game, regardless of who is hosting the Joint Ops game.

When I check the logs, I get:
[Sat Dec 22 23:48:06 2007] network: hw:00:11:09:66:c3:3c EthernetII IPv4 UDP to:64.53.xxx.xxx:213 from:192.168.1.10:213 'wrong port number'

(obviously, there is a valid IP address in the To: that I've x'ed out for security).

What gives? It doesn't seem like this program should be terribly difficult to consider, given our collective experience, yet we're banging out heads against the wall. He's running a linksys with port 213 forwarded, I'm running a Smoothwall 3.0, also with 213 forwarded and included in the outgoing exception list.

Any suggestions?

PostPosted: Fri Dec 28, 2007 6:18 am
by karma
Hey, post up your respective Local Area Network settings, your GIT configuration settings, and GIT Advanced Cfg settings...that's a good start.

PAY ATTENTIN TO THIS...PARTICULAR INFO FOR JOINT OPS HERE!! "You will need to add ports 32768, 49152, 64206-64211 and 7597 in the port forwarding ranges, in the GIT Config section." that is to make JO work.

Here is a list of what to checkmark under GIT Advanced Cfg.

IEEE 802.2
ETHERNET II
IPX
NETBIOS
ALSO MATCH SOURCE PORT
FORWARD ARP
ZLIB COMPRESSION
TCP
UDP
ICMP
DON'T SEND ROUTABLE

So there you go.
Checkmark all that. Uncheckmark the rest.

And...Important...If using TCP which you may be doing, Make Sure Your Networks can communicate with each other (10.x.x.x won't communicate with 192.168.x.x) ... post your questions.

--rob