[Help] Not able to ping outside network

IPv4/6, Port, VPN, proxy, SSH, remote access and more.
User avatar
Gremlin
Gold Member
Posts: 1625
Joined: 02 Dec 2022, 22:31
Great Britain

Re: [Help] Not able to ping outside network

Post by Gremlin »

shahmanank wrote: 01 Jun 2025, 04:59 Yes the model number is F4-423. ...... and IP address for the NAS was made static from router end and its dynamic from NAS end.
How many NAS ports are connected to LAN? (Try just one to trouble shoot). When setting NAS port 'at router end' did you set an IP address that was within the DHCP "pool"? Did you check you had the correct MAC address for the connected NAS port when setting? Try removing DHCP setting from Router and just set a static address on the NAS - Use an IP address from outside the router's DHCP pool (adjust the DHCP pool if needed to have an available set of addresses that can be static within the LAN segment.)

{Do you happen to have any TP-Link devices on network? Some of these were manufactured with a DHCP server that would automatically start to issue DHCP addresses if no other DHCP server was detected on LAN. This could be random depending on speed of boot up of particular devices and would cause intermittent conflicts. Firmware updates were available for most (some?) TP-Link devices affected. Set the DHCP server in these devices to OFF if possible to be certain.}
F5-221 TOS7.0.0777 - 4x4TB (Ironwolf) Traid
F2-424 TOS7.0.0777 - 2x500GB nvme (P3) Traid, 2x6TB HDD (HGST) Traid
F2-221 TOS7.0.0777 - 1x3TB Ext4, 1x4TB Btrfs
F2-425+ TOS7.0.0777 - 2x500GB nvme (P3) Traid, 2x6TB HDD (EXOS) Traid
User avatar
shahmanank
Posts: 7
Joined: 31 May 2025, 06:28
Canada

Re: [Help] Not able to ping outside network

Post by shahmanank »

Looks like the network connectivity issue is resolved. Found a firewall rule for port 8080 added for Guacamole causing this issue. Removing this FW rule resolved the concern. FYI
Post Reply

Return to “Network”