i got the tunnel to work perfectly between my LAN at home(5 users on 192.168.1.x) and a computer here, which is assigned static dsl settings for the network adapter, with no router.(with the help of remote desktop) im writing this because all the other guides in other threads have one option flipped, and it didn't work for me. ill explain further. this is only relevant if you are trying to make GIT work with a computer NOT on a NAT that needs an extra network adapter to get on a subnet.
PC1 = dynamic ip DSL client behind a router/NAT along with 4 other PCs on 192.168.1.x. GIT .99 b4
PC2 = static IP DSL. no router. internet IP info inputted directly into NIC TCP/IP properties. SP2 Windows firewall. GIT .99 b4
-
1. PC1 and PC2 both have to do first obvious step. forwarding/opening the GIT port. So i did this on both. (on the router for PC1, and in the SP2 windows firewall on PC2.
2. Configuration for both is not really relevant. all it should have is you connecting to 213 of their IP or hostname. and the ports you want forwarded.
In advanced config, Each person should have the important 4 options checked:
Ethernet II
Forward ARP
UDP
Also match source port
this will let me play any modern game that I've tried. if i uncheck any of these options, games like splinter cell stop working.
3. so for PC1, thats all you need in advanced config. make sure the proper NIC is selected as the one that forward the packets(the one that has your private ip settings in it) hes done.
4. now for PC2. the bad thing about PC2 was his NIC address settings are taken up by the static DSL settings to get on the net. but then how do you also get a 192.168.1.x address so you can communicate with the other guy? so then i must add a loopback adapter.
http://support.microsoft.com/default.as ... -us;839013
instructions for winXP ^
the loopback adapter would be assigned onto the same subnet and subnet mask as PC1's private network. 192.168.1.x, 255.255.255.0 for me.
without this loopback adapter, PC1's private network wouldn't bother talking to me, so i think of it like security key. gotta get on the 192.168.1.x subnet, this is how.
5. lastly, you must go into advanced config of GIT for PC2. check the same important 4 options. AND now you must do one more thing to make it all work.
check 'alter source IP'. now you're saying ok duh, now i put my loopback adapter address(192.168.1.x) into the internal, and my external internet IP into external and check it, BUT
NO!
it didn't work when i did this. SWITCH those 2 around. put your external address in the internal section, and your 192.168.1.x in the external section. i did this, and boom, everyone can ping each other, could connect to teamspeak(UDP) by its private address. it works.
i always read though, that you have to have it the other way around, but when i switched them just for fun, it worked. I don't know exactly how it works, but my guess is that since im using my internet address in my NIC itself, then it is basically perceived as my internal address too since its in my NIC. i dont really understand how my loopback address(192.168.1.x) is external, maybe its because being 192.168.1.x is my ultimate destination. i dont know. i dont know how it works really, maybe the way i explained this will make ark laugh, and maybe theres another easier way, but well, this works and its the only way i could find.
since i did this from remote desktop, i could only test teamspeak, which worked from private ip to private ip.
----ADDENDUM----
ok, see i knew this would happen, i found an easier way to do it. instead of an ms loopback adapter, all i had to do for PC2 was add the private IP in the existing NIC under Advanced in TCP/IP properties. you don't even need to alter source IP if you do it this way. and teamspeak and pinging that i tested worked all the same.
[/b]