Can't connect to server in LAN network

[Vietlubu 8]

 

I'm trying to connect client to my server on LAN network.

1. I have 2 computers.

 - A Windows PC for client - 192.168.1.6

- A Macbook I used as Server- 192.168.1.5

- Both of them, I has set static IP.

2. Try to ping client to server. - Success

 

3. Config server and client

conf/network.conf

lan_subnets: (
    // "127.0.0.1:255.0.0.0",
    "192.168.1.5:255.255.255.0",
)

conf/import/char-server.conf

char_configuration: {
    inter: {
        char_ip: "192.168.1.5"
    }

conf/import/map-server.conf

map_configuration: {
    inter: {
        map_ip: "192.168.1.5"
    }
}

clientinfo.xml

<address>192.168.1.5</address>

 

4. Start server. - Success

 

5. Login from client - 2018-12-12bRagexe

char_server log don't update any log when I login

6. I'm try check network with Microsoft Network Monitor 3.4

 

I cannot connect the Client to the server and don't know why! If you have experiences please help 😂

Edited June 15, 2019 by Vietlubu
Add ragexe date

[cookie-rae 6]

1 hour ago, Vietlubu said:

 

I'm trying to connect client to my server on LAN network.

1. I have 2 computers.

 - A Windows PC for client - 192.168.1.6

- A Macbook I used as Server- 192.168.1.5

- Both of them, I has set static IP.

2. Try to ping client to server. - Success

 

3. Config server and client

conf/network.conf

lan_subnets: (
    // "127.0.0.1:255.0.0.0",
    "192.168.1.5:255.255.255.0",
)

conf/import/char-server.conf

char_configuration: {
    inter: {
        char_ip: "192.168.1.5"
    }

conf/import/map-server.conf

map_configuration: {
    inter: {
        map_ip: "192.168.1.5"
    }
}

clientinfo.xml

<address>192.168.1.5</address>

 

4. Start server. - Success

 

5. Login from client - 2018-12-12bRagexe

char_server log don't update any log when I login

6. I'm try check network with Microsoft Network Monitor 3.4

 

I cannot connect the Client to the server and don't know why! If you have experiences please help 😂

you dont need to edit lan_subject as long you connect in router.

make it default.

Thus check your firewall if there is any blocking incoming outgoing.

try also use in windows pping application to check the ip:port is available and active outside.

pping serverip:6900* sample check 3 ports.

 

 

 

[Vietlubu 8]

18 minutes ago, hikashin said:

you dont need to edit lan_subject as long you connect in router.

make it default.

Thus check your firewall if there is any blocking incoming outgoing.

try also use in windows pping application to check the ip:port is available and active outside.

pping serverip:6900* sample check 3 ports.

 

 

 

I have tried with no change config on network.conf. But still not working

I don't know ping commands can use with a special post. I think maybe I'm missing something with configurations.

[cookie-rae 6]

39 minutes ago, Vietlubu said:

I have tried with no change config on network.conf. But still not working

I don't know ping commands can use with a special post. I think maybe I'm missing something with configurations.

This is pping command

 https://github.com/codingfreak/pping
https://github.com/codeliveroil/pping

I usually double check if port is alive tho if i cant connect on my servers. also check firewall as i said and ports.

[Vietlubu 8]

2 hours ago, hikashin said:

This is pping command

 https://github.com/codingfreak/pping
https://github.com/codeliveroil/pping

I usually double check if port is alive tho if i cant connect on my servers. also check firewall as i said and ports.

Thank you!

I check it again with pping and see client cannot connect to server

dial tcp 192.168.1.5:6900: connectex: No connection could be made because the target machine actively refused it. for seq=46

On the Server PC while Hercule on runing, I try to start a web server with Port 6900 and that success. It mean port 6900 not used before that, so strange.

On client, I connect http://192.168.1.5:6900/ with browser, that connects success and pping get this message.

64 bytes to 192.168.1.5:6900 tcp_seq=0 time=50.932 ms

My Firewall has turn off!

[cookie-rae 6]

6 hours ago, Vietlubu said:

Thank you!

I check it again with pping and see client cannot connect to server

dial tcp 192.168.1.5:6900: connectex: No connection could be made because the target machine actively refused it. for seq=46

dial tcp 192.168.1.5:6900: connectex: No connection could be made because the target machine actively refused it. for seq=46

On the Server PC while Hercule on runing, I try to start a web server with Port 6900 and that success. It mean port 6900 not used before that, so strange.

On client, I connect http://192.168.1.5:6900/ with browser, that connects success and pping get this message.

64 bytes to 192.168.1.5:6900 tcp_seq=0 time=50.932 ms

64 bytes to 192.168.1.5:6900 tcp_seq=0 time=50.932 ms

My Firewall has turn off!

Do you use wireless router? set to the router a open port so they broadcast open port on the whole server and they can meet.

[Vietlubu 8]

6 hours ago, hikashin said:

Do you use wireless router? set to the router a open port so they broadcast open port on the whole server and they can meet.

My Server used network cable, Client use wireless. From a router. Of course, I had tried to connect both PC to wire network but still not working.

In the file login-server.conf I changed

login_configuration: {
	inter: {
		// The login server listens on the interface with this IP address.
		// NOTE: This allows you to run multiple servers on multiple interfaces
		// while using the same ports for each server.
		bind_ip: "192.168.1.5"
	}
}

I know it not correct config, just for test. But pping can send packets.

About client I logged with 123123_M/123123 Server has received the packet and create account success but still cannot login

[cookie-rae 6]

23 hours ago, Vietlubu said:

My Server used network cable, Client use wireless. From a router. Of course, I had tried to connect both PC to wire network but still not working.

In the file login-server.conf I changed

login_configuration: { inter: { // The login server listens on the interface with this IP address. // NOTE: This allows you to run multiple servers on multiple interfaces // while using the same ports for each server. bind_ip: "192.168.1.5" } }

login_configuration: {
	inter: {
		// The login server listens on the interface with this IP address.
		// NOTE: This allows you to run multiple servers on multiple interfaces
		// while using the same ports for each server.
		bind_ip: "192.168.1.5"
	}
}

I know it not correct config, just for test. But pping can send packets.

About client I logged with 123123_M/123123 Server has received the packet and create account success but still cannot login

Why did you enable bind_ip: on login-server.conf you dont need to change these lines.

Revert the change on login-server.conf and then try this

char-server.conf

// Login Server IP
        // The character server connects to the login server using this IP address.
        // NOTE: This is useful when you are running behind a firewall or are on
        // a machine with multiple interfaces.
       login_ip: "192.168.1.5"

        // The character server listens on the interface with this IP address.
        // NOTE: This allows you to run multiple servers on multiple interfaces
        // while using the same ports for each server.
        //bind_ip: "127.0.0.1"

        // Login Server Port
        login_port: 6900

        // Character Server IP
        // The IP address which clients will use to connect.
        // Set this to what your server's public IP address is.
        char_ip: "192.168.1.5

        // Character Server Port
        char_port: 6121

 

map-server.conf

// Character Server IP
        // The map server connects to the character server using this IP address.
        // NOTE: This is useful when you are running behind a firewall or are on
        // a machine with multiple interfaces.
        char_ip: "192.168.1.5"

        // The map server listens on the interface with this IP address.
        // NOTE: This allows you to run multiple servers on multiple interfaces
        // while using the same ports for each server.
        //bind_ip: "127.0.0.1"

        // Character Server Port
        char_port: 6121

        // Map Server IP
        // The IP address which clients will use to connect.
        // Set this to what your server's public IP address is.
      map_ip: "192.168.1.5"

        // Map Server Port
        map_port: 5121
    }

Now you should able to ping these ports on your client pc.

 

 

Edited June 17, 2019 by hikashin

[Vietlubu 8]

@hikashin, Thank you! That working for me.

Final configuration

1. login-server: Keep the default

2. char-server:

char_configuration: {
	inter: {
		login_ip: "192.168.1.5"
		login_port: 6900

		char_ip: "192.168.1.5"
		char_port: 6121
	}
}

3. map-server:

map_configuration: {
	inter: {
		char_ip: "192.168.1.14"
		char_port: 6121

		map_ip: "192.168.1.14"
		map_port: 5121
	}
}

 

[cookie-rae 6]

5 hours ago, Vietlubu said:

@hikashin, Thank you! That working for me.

Final configuration

1. login-server: Keep the default

2. char-server:

char_configuration: { inter: { login_ip: "192.168.1.5" login_port: 6900 char_ip: "192.168.1.5" char_port: 6121 } }

char_configuration: {
	inter: {
		login_ip: "192.168.1.5"
		login_port: 6900

		char_ip: "192.168.1.5"
		char_port: 6121
	}
}

3. map-server:

map_configuration: { inter: { char_ip: "192.168.1.14" char_port: 6121 map_ip: "192.168.1.14" map_port: 5121 } }

map_configuration: {
	inter: {
		char_ip: "192.168.1.14"
		char_port: 6121

		map_ip: "192.168.1.14"
		map_port: 5121
	}
}

 

Glad that works on you