Gnutella Forums

Gnutella Forums (https://www.gnutellaforums.com/)
-   NapShare (Cross-platform) (https://www.gnutellaforums.com/napshare-cross-platform/)
-   -   adding hosts (https://www.gnutellaforums.com/napshare-cross-platform/14441-adding-hosts.html)

joehill August 11th, 2002 08:25 PM

adding hosts
 
Napshare is not connecting to any hosts, and I am hoping someone can help me
narrow down the problem.

I am on a small LAN with a router/NAT/firewall providing my internet connection.
I have configured my router to allow connections through port 6346. I have
tried using the default Napshare configuration, but that shows my IP as
192.168.0.2, so as the Readme suggested I tried forcing my IP to the address of
my router, but still no connections are made by Napshare.

I can browse the internet and am experiencing no other network problems. I can ping the hosts which I see Napshare trying to connect to with no difficulty.

Any help really appreciated!

Thanks all,

J.

Crashdamage August 12th, 2002 10:14 PM

Have you read the ReadMe file section on "Push"? Gives some good info.

In Napster>Config, do you have a reflected IP shown? You can ping others, but can you ping your machine from outside the LAN? Of course other Napster clients don't need to know your IP to work, and if you're behind a firewall running IP masq (hope you are) Napster should work with a reflected external IP like 65.XX.XX.XXX. but you should be able to ping your local 192.XXX.X.X IP. If not, maybe check your router's NAT config.

I use Napster from behind Bastille firewall running both IP masq and NAT with no problem from this machine, which doubles as a router/firewall for a small LAN. I don't even have to force the IP, so it'll work, ya just might have to play around some to find what's not setup quite right.

joehill August 13th, 2002 09:39 AM

hmmmmmm...
 
hey there! thanks for the info. however, when i went to look at the client again to check it against the info you gave me...well, it just sort of started working. it found a whole slew of hosts while i was reading the readme about Push.


weeeeeeeird...but i won't complain.

thanks again!

J.

edit: just in case this is useful for anyone, the config that worked for me (eventually...heh) was to force the local IP to my router's WAN interface and to allow the router to forward port 6346 to the wkstn. i personally don't think that last part is necessary, since in the read me it says that Napshare uses randon ports to connect, 6346 is only neede for other people to connect to you.

Crashdamage August 13th, 2002 04:42 PM

Glad Napshare started working...who knows why...

I don't know why you had to force IP, should work anyway like mine does unless you've got some restrictive settings in your router. But you probably will have to leave port 6346 available to allow uploads. I did have to do that in Bastille>config or no uploads.

Unregistered August 28th, 2002 06:49 AM

nothing can connect to a 192.168.x.x from outside, think about it, no outside routers will pass on a packet to a 192.168 destination, and it looks like your box has gotten a ip assigned from dhcp from your setup cable modem/nat, this is good for your protection and push will have to be used I may be wrong, so you wont get as many files as if you had your own ip though
there should be no problem getting hosts to connect to, even with a 192.168 ip, once you get a few good ones to start with so I think that was your problem at first
if the nat box passes packets on to your ip and same port, that would seem to work right and forcing the ip would then work, monitor with tcpdump and post back this is interesting to see if it works this way


All times are GMT -7. The time now is 05:27 AM.

Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2024, vBulletin Solutions, Inc.
SEO by vBSEO 3.6.0 ©2011, Crawlability, Inc.

Copyright © 2020 Gnutella Forums.
All Rights Reserved.