This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

I just don't get it...

I'm trying to access battle.net to play Warcraft 3 with a couple of friends but my ASL just won't let me in. When I click on the battle.net button to login, I get the message "Unable to connect to battle.net".

The following are port information from battle.net:
    * Allow port 6112 TCP out and allow established sessions in
    * Allow port 6112 TCP in (hosting custom games)
    * Allow port 6113-6119 TCP out and in (hosting custom games if you’ve changed the default port in the Options/Gameplay screen)

I've setup two services, WC-1(6112) and WC-2(6113-6119) both set at TCP/UDP.

The following are my NAT Rules:
WC3-1   Any->inwall(Address)/WC3-1   None   amedm
WC3-2   Any->inwall(Address)/WC3-2   None   amedm

Where inwall is my external interface and amedm is my game PC.

The following are my Packet Filter Rules:
Any   0.0.0.0/0   WC3-1   --->   0.0.0.0/0   Any
Any   0.0.0.0/0   WC3-2   --->   0.0.0.0/0   Any

When I run a port scan from the internet, the ports(6112 through 6119) is shown as green, Accept, when viewing the Packet filter live log. So, that tells me(I think) that communication between my local PC with a remote system(Internet host) is open through those ports.

But why is it that I'm still unable to login to battle.net even with the ports they requested is already opened?

I'm certain it's something very simple to the expert but not to me... [:(]

Any suggestion is much appreciated.

Thanks,
jav

This thread was automatically locked due to age.

Parents

0 javelin over 20 years ago

Sorry but I have to get back to this. I don't know why I'm getting such a hard time configuring this thing when some have actually done it.

The port in question is 6112.

When I look at the "Packet filter live log", it shows my network connection is being Drop as shown in Pink:
Code:


22:55:42 	192.168.1.30 	6112 	-> 	255.255.255.255 	6112 	UDP 	20 	24 	128

If I look at my "Current System Packet Filter Rules" from the Advance tab, it does not show any networks being dropped for port 6112.

The only drop entry is in the SPOOFING_PROTECTION:
Code:


Chain SPOOFING_PROTECTION (2 references)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 SPOOF_DROP  all  --  eth2   *       24.107.57.208        0.0.0.0/0           
    0     0 SPOOF_DROP  all  --  eth2   *       192.168.1.0/24       0.0.0.0/0           
    0     0 SPOOF_DROP  all  --  eth0   *       192.168.1.1          0.0.0.0/0           
    0     0 SPOOF_DROP  all  --  eth0   *       24.107.32.0/19       0.0.0.0/0

This seems to be normal as it provides security against network spoofing. Is it?

I have temporarily disabled all "blocked" networks from my "Packet Filter Rules" but still the same. I'm lost!

Any suggestion anyone?

Jav

Reply

0 javelin over 20 years ago


22:55:42 	192.168.1.30 	6112 	-> 	255.255.255.255 	6112 	UDP 	20 	24 	128

If I look at my "Current System Packet Filter Rules" from the Advance tab, it does not show any networks being dropped for port 6112.

The only drop entry is in the SPOOFING_PROTECTION:
Code:


Chain SPOOFING_PROTECTION (2 references)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 SPOOF_DROP  all  --  eth2   *       24.107.57.208        0.0.0.0/0           
    0     0 SPOOF_DROP  all  --  eth2   *       192.168.1.0/24       0.0.0.0/0           
    0     0 SPOOF_DROP  all  --  eth0   *       192.168.1.1          0.0.0.0/0           
    0     0 SPOOF_DROP  all  --  eth0   *       24.107.32.0/19       0.0.0.0/0

Children

No Data