[661] Client hangs 'Now processing' at server select; No exceptions at the consoles.

[elmasmalo1]

Hey guys!

I fiddling with the versions 661 server files along with the 661 client... found here: http://forum.ragezone.com/f1000/torr...4/#post8909870 - and I have done nothing to it.. been using it straight from the torrent download (client).

Now for the server, I have configured everything correctly (or as I would like to think so) following this guide: http://forum.ragezone.com/f1001/guid...nline-1143140/ and when I get to the server selection going to the character selection it just hangs in there showing the `'Now processing' message.

This is my configuration files (the most important ones)

..realmserver\configs\network.properties

# Rmi connection host.
network.rmi.host = 127.0.0.1

# Rmi connection port.
network.rmi.port = 9000

# Rmi connection password.
network.rmi.password = 1234

# Server version supported
# NA-EU: 4635 - 491
# NA-EU 4861 - 661
network.server.version = 4861

# Client support european.
network.encrypt.packets = true

# Host for server binding.
# Default: 0.0.0.0
network.host = 192.168.1.117

# Port for server binding.
# Default: 8888
network.port = 8888

# Show debug messages.
# Default: false
network.debug = true

# Packet executing mode.
# DIRECT - The worst. Income packets are directly executed after receiving and decrypting. As packets here implemented terribly, it not only increases latency, but decrease overall performance significant.
# OFFLOAD - Offloads execution to a ThreadPool. Good option with POOLED IOExec mode. Increases throughput but also may increase context switch count.
# Default: OFFLOAD
network.packet.exec.mode = OFFLOAD

# Receive buffer size.
# Default: 32768
network.recv.buffer.size = 32768

# Send buffer size.
# Default: 65536
network.send.buffer.size = 65536

# NetworkThread socket backlog size.
# See: http://www.linuxjournal.com/files/linuxjournal.com/linuxjournal/articles/023/2333/2333s2.html
# Default: 50
network.server.socket.backlog = 50

# Client socket options.
# SO_SNDBUF - the size of the socket's send buffer. On most systems this the size of a kernel buffer so be careful! See RFC1323.
# SO_RCVBUF - the size of the socket's receive buffer. On most systems this the size of a kernel buffer so be careful! See RFC1323.
# TCP_NODELAY - The Nagle algorithm. Enabling it increases throughput but also increases latency. See RFC1122.
# Default: SO_SNDBUF(8192);SO_RCVBUF(8192);TCP_NODELAY(true)
network.client.socket.options = SO_SNDBUF(8192);SO_RCVBUF(8192);TCP_NODELAY(true)

# NetworkThread socket options.
# SO_REUSEADDR - if true, prevents socket from usage until all opened sockets are really closed. See RFC793.
# Default: SO_REUSEADDR(true);SO_RCVBUF(4096)
network.server.socket.options = SO_REUSEADDR(false);SO_RCVBUF(4096)

# IO Network thread execution mode.
# POOLED - All IO operations are executed in a special thread IO execution pool
# FIXED - All IO operations execution is spread across fixed number of treads
# Default: POOLED
network.io.execution.mode = POOLED

# Number of IO Network threads.
# Default: -1 (Processor count)
network.io.execution.thread.num = -1

# Income packet header size.
# Default: 3
network.income.packet.header.size = 3

# Max income packet size.
# Default: 16384
network.max.income.packet.size = 16384

# Outcome packet header size.
# Default: 3
network.outcome.packet.header.size = 3

# Max outcome packet size.
# Default: 16384
network.max.outcome.packet.size = 16384

..worldserver\configs\network.properties

# Rmi connection host.
network.rmi.host = 127.0.0.1

# Rmi connection port.
network.rmi.port = 9000

# Rmi connection password.
network.rmi.password = 1234

# Server version supported
# NA-EU: 4635 - 491
# NA-EU 4861 - 661
network.server.version = 4861

# Client support european.
network.encrypt.packets = true

# Host for server binding.
# Default: 0.0.0.0
network.host = 192.168.1.117

# Port for server binding.
# Default: 8889
network.port = 8889

# Show debug messages.
# Default: false
network.debug = true

# Packet executing mode.
# DIRECT - The worst. Income packets are directly executed after receiving and decrypting. As packets here implemented terribly, it not only increases latency, but decrease overall performance significant.
# OFFLOAD - Offloads execution to a ThreadPool. Good option with POOLED IOExec mode. Increases throughput but also may increase context switch count.
# Default: OFFLOAD
network.packet.exec.mode = OFFLOAD

# Receive buffer size.
# Default: 32768
network.recv.buffer.size = 32768

# Send buffer size.
# Default: 65536
network.send.buffer.size = 65536

# NetworkThread socket backlog size.
# See: http://www.linuxjournal.com/files/linuxjournal.com/linuxjournal/articles/023/2333/2333s2.html
# Default: 50
network.server.socket.backlog = 50

# Client socket options.
# SO_SNDBUF - the size of the socket's send buffer. On most systems this the size of a kernel buffer so be careful! See RFC1323.
# SO_RCVBUF - the size of the socket's receive buffer. On most systems this the size of a kernel buffer so be careful! See RFC1323.
# TCP_NODELAY - The Nagle algorithm. Enabling it increases throughput but also increases latency. See RFC1122.
# Default: SO_SNDBUF(8192);SO_RCVBUF(8192);TCP_NODELAY(true)
network.client.socket.options = SO_SNDBUF(8192);SO_RCVBUF(8192);TCP_NODELAY(true)

# NetworkThread socket options.
# SO_REUSEADDR - if true, prevents socket from usage until all opened sockets are really closed. See RFC793.
# Default: SO_REUSEADDR(true);SO_RCVBUF(4096)
network.server.socket.options = SO_REUSEADDR(false);SO_RCVBUF(4096)

# IO Network thread execution mode.
# POOLED - All IO operations are executed in a special thread IO execution pool
# FIXED - All IO operations execution is spread across fixed number of treads
# Default: POOLED
network.io.execution.mode = POOLED

# Number of IO Network threads.
# Default: -1 (Processor count)
network.io.execution.thread.num = -1

# Income packet header size.
# Default: 3
network.income.packet.header.size = 3

# Max income packet size.
# Default: 16384
network.max.income.packet.size = 16384

# Outcome packet header size.
# Default: 3
network.outcome.packet.header.size = 3

# Max outcome packet size.
# Default: 16384
network.max.outcome.packet.size = 16384

running out of ideas... also I'm available for TeamViewer connections if possible.

[MentaL]

[Yurdead69]

Hello !
Do you have put in here :
worldserver\configs\server.properties

Your ip external or ip WAN ? Open all Ports :
Tcp / Udp : 9000,8888,8889,27017 ?
Say me if works !
Yurdead

[elmasmalo1]

Hello !
Do you have put in here :
worldserver\configs\server.properties

Your ip external or ip WAN ? Open all Ports :
Tcp / Udp : 9000,8888,8889,27017 ?
Say me if works !
Yurdead

Hi! thanks for helping me out...

this is my server.properties content:

# Server id.
server.id = 1

# Server short name (Must be in UPPER case.)
server.short.name = NA

# Channel id.
server.channel.id = 1

# External server IP for client connections
server.ip = 192.168.1.117

# Game server service type.
# Options: DEV, KOR_REAL, NA_REAL, RUS_REAL, JPN_REAL
server.game.service.type = NA_REAL

# Game server resource type.
# Options: DEV, KR, EN, JP, CN, RU, FR, DE, ES
server.game.resource.type = EN

# Enable PC Cafe bonuses for players.
server.enable_pc_cafe_bonus = false

# Server busy state limit values.
server.busy_state_limit_inspection = 0

server.busy_state_limit_smooth = 100

server.busy_state_limit_busy = 500

server.busy_state_limit_very_crowded = 1500


server.admin_only = false

and I hadn't previously opened my ports, didn't thought that matter since I was testing locally.. but I opened them... and I will re-test now..

**EDIT**

tested, with fresh files and no modifications, only those you mentioned, like setting the IPs in the configs and such...

Now it doesn't even wanna login.. it says "Failed to connect" at login screen. Don't know if it's because of the XC, or something, but I used the 'alternateXC' that comes packaged along with the files and it's not working.. no errors on the console or anything... packets are coming through as I can see them though..

[Yurdead69]

Hi ...
Can you put ip like IP dedicated or other then local ip ?
like 127.0.0.1 or 178.XX.XXX.XX
try this and say me ...
Yurdead

[elmasmalo1]

Hi ...
Can you put ip like IP dedicated or other then local ip ?
like 127.0.0.1 or 178.XX.XXX.XX
try this and say me ...
Yurdead

Still Failed to Connect