Nomidia 0 Posted February 20, 2021 Share Posted February 20, 2021 Hi guys. I discovered that my network name changed by itselff ,I am 100% sure I didn't changed its name into lan. 😀Maybe I clicked on something in the setup or something else I don't know.Help please🙏 how did this happen? Link to comment Share on other sites More sharing options...
itman 1,659 Posted February 21, 2021 Share Posted February 21, 2021 (edited) In Eset GUI firewall settings, mouse click on "Edit" for Known Networks setting per the below screen. This will show all network connections set up in Eset. Post a screen shot of what is shown. Normally, there should be only one connection shown in Known Networks which is associated with your network adapter. The network name assigned by Eset is normally the connection-specific DNS suffix assigned by your ISP during DHCP initialization at system startup time. Eset assignment of a "LAN" network name indicates to me you might have an ISP issue in regards to DHCP processing, or there is an issue with your router forwarding the correct DNS suffix. Edited February 21, 2021 by itman Link to comment Share on other sites More sharing options...
Nomidia 0 Posted February 21, 2021 Author Share Posted February 21, 2021 7 hours ago, itman said: In Eset GUI firewall settings, mouse click on "Edit" for Known Networks setting per the below screen. This will show all network connections set up in Eset. Post a screen shot of what is shown. Normally, there should be only one connection shown in Known Networks which is associated with your network adapter. The network name assigned by Eset is normally the connection-specific DNS suffix assigned by your ISP during DHCP initialization at system startup time. Eset assignment of a "LAN" network name indicates to me you might have an ISP issue in regards to DHCP processing, or there is an issue with your router forwarding the correct DNS suffix. from advanced setup to firewall >>known networks I clicked on Edit ,this is the screen, but can you explain what does that mean in a simple way because I didn't understand ( Eset assignment of a "LAN" network name indicates to me you might have an ISP issue in regards to DHCP processing, or there is an issue with your router forwarding the correct DNS suffix.) Link to comment Share on other sites More sharing options...
itman 1,659 Posted February 21, 2021 Share Posted February 21, 2021 Based on your posted screen shot, "lan" network does not exist. Repeat the same Eset GUI access process but this time, mouse click on "Connected Networks" and post a screen shot of what is displayed: Link to comment Share on other sites More sharing options...
Nomidia 0 Posted February 21, 2021 Author Share Posted February 21, 2021 1 hour ago, itman said: Based on your posted screen shot, "lan" network does not exist. Repeat the same Eset GUI access process but this time, mouse click on "Connected Networks" and post a screen shot of what is displayed: There is no "lan " because I erased it and re-write the name of my network (JiaxiLufeng),so instead of JiaxiLufeng yesterday there was lan . but I don't know if this will help you figure out the problem, there is here a "lan" that I didn't change it . Link to comment Share on other sites More sharing options...
itman 1,659 Posted February 21, 2021 Share Posted February 21, 2021 (edited) 3 hours ago, Nomidia said: but I don't know if this will help you figure out the problem, there is here a "lan" that I didn't change it . Eset populates the DNS suffix with whatever is established for connection-specific DNS suffix value established by DHCP initialization as I posted previously. You can determine the current connection-specific DNS suffix value by opening a command prompt window and entering the following: ipconfig /all Under each network adapter connection section in the display, note the value shown for connection-specific DNS suffix value : Quote Ethernet adapter Ethernet: Connection-specific DNS Suffix . : xxxlocal.net Description . . . . . . . . . . . : Realtek PCIe GbE Family Controller Physical Address. . . . . . . . . : xx-xx-xx-xx-xx-xx DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Above is shown DNS suffix assigned via my router and ISP for my Ethernet network connection. Note that the "lan" value you are observing is being assigned the same way. Eset is only populating its corresponding network connection fields with data received from your router/ISP. Edited February 21, 2021 by itman Nomidia 1 Link to comment Share on other sites More sharing options...
Recommended Posts