Results 1 to 4 of 4

Thread: Using other p2p apps with a LAN?

  1. #1
    The Man Who's Avatar

    ZeroPaid Regular

    Join Date
    Nov 2003
    Posts
    30

    Using other p2p apps with a LAN?

    Hi, I am studying at University at the moment and I have been using KaZaA Lite on the Local Area Network, without problem. however, i have became bored of the app and would like to use other apps such as WinMX, however i can't seem to get them to connect. The original KaZaA I also know cannot connect using my LAN connection. So how would be the best way, or apps to use to connect to my LAN.

    I thought of trying to track the TCP and UDP ports that KaZaA Lite was using and configuring the other apps, such as WinMX to use these, but as you can see Im a newbie and am just not sure how to do this properly.

    Thanks in Advance
    The Man Who
    Screaming Angel Returns...

  2. #2
    d-koolest's Avatar

    Registered User

    Join Date
    Sep 2002
    Location
    Seattle(ish), WA
    Posts
    342
    I'm having a similar problem with my home LAN. I tried to connect with Piolet, WinMX, can't seem to configure them to go through.

  3. #3
    Wolfie's Avatar

    Aku Soku Zan

    Join Date
    Apr 2002
    Location
    USA
    Posts
    3,179
    Unlike Kazaa, you need open ports (two to be exact) on a firewall or router for winmx.

    Home LAN should be easy to get around but not sure about university network firewall.
    Insert sig image here

    Since its inception almost 30 years ago, the internet has been transformed from a primitive device for sharing thoughts and ideas, into a massive network where people pay to connect and read advertisements they don't want, while calling each other "asshats".

  4. #4

    Alpha Geek

    Join Date
    Dec 2002
    Posts
    724
    Winmx works fine with incoming connections blocked.
    Connection sharing routers normally allow outgoing connections to any port on a remote host and block all incoming connections. Winmx goes a bit faster with port forwarding enabled for its tcp and udp ports but it's not vital.

    Kazaa may connect if let open for an hour or so.

    It is likley that all incoming connections to a machine on a university lan are blocked.

    If kazaa does not connect it means that _outgoing_ connections are blocked.

    By default a winmx client listens on 6699 for TCP and 6257 for UDP.
    By default kazaa listens on 1214 tcp, 80 tcp and 1214 udp.

    >I thought of trying to track the TCP and UDP ports that >KaZaA Lite was using and configuring the other apps, >such as WinMX to use these

    You can only connet to ports that a program is listening on. If you want to connect to another winmx user then you have to connect to the port that winmx client is listening on. You can't change the remote port number used for that connection.

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •