Got Git working... file sharing?

Gamer's Internet Tunnel, formerly Gamer's IPX Tunnel

Got Git working... file sharing?

Postby neil wallace » Mon Jun 13, 2005 2:19 pm

I recently got GIT working after sometime. I realised that I had configured my firewall on my router to only allow outgoing services for ports 1-65535 which I changed to ALL. This seemed to do the trick an now can play DOW, Ghost Recon and Pro Evo 4 easily.. excellent. :D

I can now see his workgroup under explorer and he can see mine, although we can not see each others PC that is running GIT (can see other PCs though, from each workgroup).. is there an option I have turned on that may cause this?

Neil
neil wallace
 
Posts: 1
Joined: Mon Jun 13, 2005 2:01 pm

Postby sumeetkpatel » Sun Aug 07, 2005 9:13 pm

Windows uses some *censored* ports 135 -137, 139 something like that.. for filesharing, one ports for like authentication etc.. maybe thats what you need, or your software firewall on each machine may be blocking the other side.
sumeetkpatel
 
Posts: 11
Joined: Sat Jul 02, 2005 11:30 am

about windows filesharing (netbios etc)

Postby karma » Mon Aug 08, 2005 4:31 pm

the ports for filesharing are 135-139 and 445. the 'ipx packet types' options in advanced config also affect file sharing (NetBIOS) so if you want to disable file sharing, uncheck netbios or exclude those ports.
karma
 
Posts: 69
Joined: Mon Mar 14, 2005 7:42 am
Location: yokosuka japan

Postby sumeetkpatel » Tue Aug 09, 2005 11:34 am

filesharing shouldnt be using IPX

this is pretty clear as if someone is DMZ'ed or not behind routing equipment (in their home obviously), then they're file shares can be access directly over internet tcp/ip -without-git- ie explorer: \\xxx.xxx.xxx.xxx perhaps \\220.139.11.22 (of course if proper ports are allowed through any firewalls), if that is possible (it is proven already), ipx is clearly redundant or not even used lets not waste this fellas time with IPX netbios shibby dibby.

Forget IPX for windows filesharing. it concerns with tcp ports 135-139 clearly, and possibly 445, i doubt 136 is necessary either.. be careful when selecting these ports also, some of them have windows RPC vulnerabilities if you arent service packetz0red
sumeetkpatel
 
Posts: 11
Joined: Sat Jul 02, 2005 11:30 am


Return to GIT

Who is online

Users browsing this forum: No registered users and 1 guest

cron