![]() If you can't wait for the temporary block to be lifted then please open a ticket in a customer support department and we can manually remove your block. Run a FULL virus scan on your computer and secure your network. If the server blocked you then either you were purposefully doing something malicious a virus on your computer is doing something malicious or someone on your network is attacking our servers. TserverHQ has a unique security system that constantly monitors the activity of critical systems and will automatically block users that are performing malicious activities. If your are convinced the server blocked you: Most ISPs in the world hold a cached DNS on their servers as well and the reset can take between a few hours to a week. This will completely reset the DNS in your computer. type "ipconfig /flushdns" without the "".Open a command prompt as an administrator or the equivalent on your computer.If you know without a doubt that everything is typed in correctly, and that the server is up you may have the wrong information stored on your computer. If it is down there will be an issue open and being updated by the system admins continually. ![]() If it says running then there are no current problems with the server itself.Ĭheck the network issues page to see if there is an issue with the server. if it takes forever to load, or says "unknown" it is probably a server issue. Log into your control panel and see if your server is running. If you are not the original owner of the server ask the person that purchased the server the correct information.Ĭheck to make sure the server is running: Solutions:ĭouble check the server address you input, with the one you were given. Therefore the below solutions should solve your problem. There also is s a VERY UNLIKELY possibility that the server blocked you. Generally this means that you have a typo in the hostname that you are connecting with, there is an issue with your server or your ISP is using the wrong information to connect. Nothing has worked to resolve the issue, so if anyone has any ideas I would appreciate it! Also of note is that I can successfully ping Google’s DNS using the command prompt line “ping 8.8.8.8” on my computer and it works fine.Failed to resolve hostname 'xxxxxxxxxxx': Host not found I even attempted to give the QNAP a DHCP IP reservation and port reservation on my router. With a combination of guidance from tech support at Rogers, Google, and QNAP I’ve tried everything from rebooting and resetting our entire network to changing the DNS server to several varieties including Google’s server and my ISP’s server on both my router and the QNAP itself. I think at that time I was more focused on trying to get it connected properly and accessing the user interface again, lol! According to QNAP, they saw in my logs that this also happened the day we connected the new modem but I’m not sure as I never noticed it then if I’m honest. But as soon as the NAS rebooted after updating, all of sudden I got this message stating the DNS server cannot resolve hosts and some apps might not work properly. I did, and didn’t get any errors during the update (I watched it while I performed the update). It was then working fine until it asked me to go through a software update. With some chatting to QNAP support we were able to change the ports and IP address, which allowed it to connect again. Everything was working fine and dandy until we got the new modem a couple weeks back.Īt first, the Ethernet connection was not working at all with the NAS. It’s connected to our Google Wifi nest router, which is connected via hardwire using a plug and play Ethernet switch to my QNAP NAS TS 251+ and desktop computer running windows 10. I have a Rogers ignite wifi modem, which is currently in bridge mode. First time posting here, but I hope someone may be able to offer some guidance.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |