[Help] Not connect Channel

[En3rgik]

Look at the photos, what was wrong, why not connect the Channel?

Client:


IP- Client :



Config CentOS 2.8 chumpy i used this :CentOS 5.4 Install with TDP 2.8 pack

Config 1 :



Config 2 :



Ping whit Putty = VMware - CentOS :



Firewall Windows :



Firewall II°



VMware Network :



Router Firewall :



Windows IP :




LOGS si here : Logs Files.txt

[MentaL]

[emi]

we need to see the logs:)
We can't tell you nothing without the logs:)

[En3rgik]

update posts

[cypher]

check with http://www.canyouseeme.org/ ports: 38101 and 38121

[En3rgik]

is ON port all

[cypher]

Here try this:

In the inner network make your client connect to server`s lan ip and use the wan ip only for outbound access.

[En3rgik]

SORRY Closed Port 38121 is closed on 93.146.240.130.

My client use 192.168.0.6 - Ip CentOS ?
For my Friend IP extern ( 93.146.240.130 ) ?

CentOS -Config Pack 2.8 chumpy WAN IP use this ( 93.146.240.130 ) or LAN ?

[emi]

i think the server don't let you connect LAN and WAN in the same time!:)

[En3rgik]

I do, was from ports, I opened and 40000 and I went ...Thank You all !!

[emi]

then have fun !D

[En3rgik]

External IP (93.xxx) does not work, only the internal IP (192.168.0.6)

[chumpywumpy]

If using the external ip in the server config and internal.txt doesn't work for you get somebody external to try. If it works for them you have a router that cannot host properly (not all can) and hamachi is your only choice.

What is happening (if it is this problem) is your router sees an incoming connection from outsite the network, sees it is on a port number it has a forwarding rule for and redirects the connection to the Centos lan IP. Just what we want it to do.

When it sees an incoming connection from inside the lan it just drops it as it doesn't know what to do with it. The router has only been told to apply port forwarding rules to external connections as technically internal communications should use the internal lan ip addresses instead of the external one. Doing it that way your connection is going out form the lan to the wan, then being looped back into the lan via port forwarding. Most home routers simply don't need that extra function (called "loopback support") so manufacturers leave it out to keep the cost of the router down. The only time you would ever need it is when hosting a server that cannot listen for players on 2 networks (lan and wan) like Cabal and there aren't many of these around.

In most cases even the router manual of technical specs won't tell you if the router has loopback support or not. The only way to test is set everything up using lan p and see if it works for you (so you know the config is correct), then set everything externally and both you and somebody else tries it. If they work but you don't then it is almost definitely this problem. You will see your login attempt in the logs but it simply doesn't get passed to the worldsvr as your computer is effectively told to connect to an ip address it can't connect to.

[En3rgik]

I have another option?

Only whit Hamachi .. ? omg

[cypher]

Or you can chose any other vpn solutions like openVPN.

[En3rgik]

not know this program

I can do a small demonstration

[cypher]

Just buy a new router!