Welcome to ISAserver.org

What exactly do I have to configure to run Kazaa on ONE client pc.

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [ISA Server 2000 Firewall] >> SecureNAT Client >> What exactly do I have to configure to run Kazaa on ONE client pc.

Page: [1]

Message

<< Older Topic Newer Topic >>

What exactly do I have to configure to run Kazaa on ONE... - 20.Mar.2003 10:42:00 AM

smartsys

Posts: 36
Joined: 5.Sep.2001
Status: offline

I use two servers on my home network.
One W2K Active Directory enabled domain controller running DNS, DHCP, Exchange 2000 and IIS5. I refer to this server as Server1
The other one is a W2K member server running ISA Server 2000. I refer to this server as Server2

I created publishing rules for three different websites and for a ftp site. I used the Secure Mail Server Wizard to publish the Exchange server. All of this is working fine.
I also created some basic Packet Filter rules to allow Norton Antivirus LiveUpdates and a DNS Lookup rule.

The external IP adress = 100.100.100.100
The IP adress of Server1 = 192.168.1.1
The IP adress of Server2 = 192.168.1.10

My DNS server is not configured as a root server. The DNS servers of my ISP are configured as Forward DNS servers. The WPAD entry is created and is refering to Server2
My DHCP server is configured with one scope.
The range is 192.168.1.100 to 192.168.1.200
A "router" is configured with adress: 192.168.1.10
A "DNS Server" is configured with adress: 192.168.1.1
The DNS Domain name is configured with: mydomain.com

A Client DHCP IP configuration looks like this:
ip: 192.168.1.100
subnet mask: 255.255.255.0
default gateway: 192.168.1.10
dns servers: 192.168.1.1
dns suffix: mydomain.com
Wins: "blank"

I created Protocol rules for Kazaa: port 1214 inbound for all requests and port 1214 outbound for all requests.
I installed the latest version of KazaaLite on one of my desktops. After starting Kazaa, it just keeps "connecting", but never gets connected. The option to use port 80 or another port doesn't seem to work either.

I tried opening up the ENTIRE firewall. By creating a Packet Filter Rule for ALL protocols and a Protocol rule for all protocols and every request, but still it won't connect.
My firewall log don't shows me any usefull information.

In the end of all frustration I installed Kazaalite directly on my ISA Server. Is seems to work there, but only after I created a Packet Filter rule allowing ALL TCP data in both ways for every remote computer. Disabeling this rule will cause Kazaa to stop function again.

I also tried giving a fixed IP and DNS adres to one of my clients: IP 192.168.1.5 and DNS 192.168.1.1. I didn't gave this client a default gateway. I also installed the firewall client to this machine, but still no positive results.

I tried turing of Authentication for outgoing requests, also this doesn't help.

All my clients are able to browse the web and play online games etc. Except the f*cking Kazaa won't connect.

What is wrong with my setup. I'll understand it's rather strange i want a P2P sharing app. to function in my network, but if I know how to ENABLE it, i also know how to EFFECTIVELY block it in case this is needed.

Can it be some sort of DNS problem???

Please help!

[ March 20, 2003, 10:42 AM: Message edited by: smartsys ]

Post #: 1

Featured Links*

RE: What exactly do I have to configure to run Kazaa on... - 20.Mar.2003 12:38:00 PM

benny

Posts: 16
Joined: 27.Feb.2003
From: Pacific Island U.S.
Status: offline

on server1 isa management create a protocol definition named kazaa, port1214, protocol type tcp, direction outbound.
then create a packet filter, choose custom, tcp protocol number=6, directions outbound, local port all ports, remote ports all ports.
i use this setup but i only have one domain controller, when you fired up kazaa it takes a little longer to connect but it will i say around a minute or so.

(in reply to smartsys)

Post #: 2

RE: What exactly do I have to configure to run Kazaa on... - 20.Mar.2003 12:50:00 PM

smartsys

Posts: 36
Joined: 5.Sep.2001
Status: offline

quote:
Originally posted by bluescreen:
on server1 isa management create a protocol definition named kazaa, port1214, protocol type tcp, direction outbound.
then create a packet filter, choose custom, tcp protocol number=6, directions outbound, local port all ports, remote ports all ports.
i use this setup but i only have one domain controller, when you fired up kazaa it takes a little longer to connect but it will i say around a minute or so.

Why should I do this on Server1. ISA is installed on Server2 ???
I already created two protocol rules for Kazaa. One inbound and one outbound, both TCP port 1214.
I also created a Packet Filter for all TCP ports and both direction. I'll try stripping down the protocol rules and the packet filter, but I don't think it will work.
I have Kazaa running directly on Server2 at this moment, but it won't run on ANY of my clients.

I think it's some kind of DNS problem, but I don't know where to look.

(in reply to smartsys)

Post #: 3