Standalone LAN Server Issues

[fragdemuerte 1]

Cannot see DayZ server from one computer(account) in network, but can see and join from another(account).

Setting up standalone VM server to play on house LAN and maybe open up to community.

Here is network layout: I'm using two routers that are connected to my main Verizon modem/router. Both routers are set to access point, so the Verizon modem/router assigns all IP Addresses. Gaming PC is connected to the router/access point that is also connected to the VM box.

Following these steps to make sure that there are not issues with using two steam accounts:

1. Wiped all Steam client data from the VM Server. Wiped all Steam cache from gaming PC. Relogged in and could not see or join the VM Server.

2. Logged in as family member Steam ID on VM Server - redownloaded all server files. Logged out of VM server Steam client, deleted client. Kept all DayZ server files. Launch server with bat file.

3. Family member was able to see new server and was able to join.

4. Uninstalled all DayZ client info from gaming PC as well as all cache and logs. Revalidated the game files and erased all cache.

Still cannot see or join the server from the one PC.
Not sure if the issue is with networking. Turned off all firewall settings on VM box and PC that cannot see the server. Still cannot detect.

[Sid Debian 134]

23 minutes ago, fragdemuerte said:

Cannot see DayZ server from one computer(account) in network, but can see and join from another(account).

Setting up standalone VM server to play on house LAN and maybe open up to community.

Here is network layout: I'm using two routers that are connected to my main Verizon modem/router. Both routers are set to access point, so the Verizon modem/router assigns all IP Addresses. Gaming PC is connected to the router/access point that is also connected to the VM box.

Following these steps to make sure that there are not issues with using two steam accounts:

1. Wiped all Steam client data from the VM Server. Wiped all Steam cache from gaming PC. Relogged in and could not see or join the VM Server.

2. Logged in as family member Steam ID on VM Server - redownloaded all server files. Logged out of VM server Steam client, deleted client. Kept all DayZ server files. Launch server with bat file.

3. Family member was able to see new server and was able to join.

4. Uninstalled all DayZ client info from gaming PC as well as all cache and logs. Revalidated the game files and erased all cache.

Still cannot see or join the server from the one PC.
Not sure if the issue is with networking. Turned off all firewall settings on VM box and PC that cannot see the server. Still cannot detect.

Hm interesting but did you try to connect through the direct connection? By IP & Port...

Have you try to set the highest router IP as the "DNS" server with levels layout?

I mean your "Verizon" has ip 192.168.0.1, other router has IP 192.168.1.1, the "Verizon" shall be the DNS server for bottom layers, your 2nd routher shall has the setted up as bridge with redirection to the 192.168.0.* network, and yours PCs shall has the IPs in line 192.168.1.(2;3...). with refering to the DNS server 192.168.0.1 (your "Verizon" router), mask for the network (255.255... find in the network).

 

On that setup you can give opened access & assignments map for your network.

I'm sorry I really guessing right now, but try out, hell knows maybe it will rollin... 

I'm thinking the open network map within open assignment map shall open enough information for recreation of correct package paths and resolving the issues but as I said b4 I'm not the network guru so the best what do i can do is only wish you luck with that 🙂

[fragdemuerte 1]

Hi Sid - Thanks for trying to help. This is stumping me pretty bad... 

"Hm interesting but did you try to connect through the direct connection? By IP & Port..."

Yes, I tried direct connection... nothing happens.

"I mean your "Verizon" has ip 192.168.0.1, other router has IP 192.168.1.1, the "Verizon" shall be the DNS server for bottom layers, your 2nd routher shall has the setted up as bridge with redirection to the 192.168.0.* network, and yours PCs shall has the IPs in line 192.168.1.(2;3...). with refering to the DNS server 192.168.0.1 (your "Verizon" router), mask for the network (255.255... find in the network)."

The Verizon modem is set to 192.168.1.1. The VM box is 192.168.1.13. The bridge is like 192.168.1.15. Everything is set pretty simply. It set the other routers as access points so there's no extra DNS servers. 

I'm drawing blanks of why one PC can see the server and the other PC cannot.