Now then. I have a weird error. I'm trying to log into my friend's server. I know it's possible to - I have done it before. But, I went on holiday, and they told me that they had updated to 1.7.4. I tried coming onto the server, but, after a wait of 10 minutes while it pinged (not normal), it quickly flashed Cannot connect to server, then it said it was out of date and required 1.7.2 in the server list. I tried 1.7.2, and this greeted me. I would love an explanation as to how this happened, and a solution. The server is whitelisted: sovremenny.homeunix.org. The server owners believe that the fault is on my side. If you need any more details, just ask. However, I cannot give you everything. I don't own the server, and I don't control the Internet in my house.
Now then. I have a weird error. I'm trying to log into my friend's server. I know it's possible to - I have done it before. But, I went on holiday, and they told me that they had updated to 1.7.4. I tried coming onto the server, but, after a wait of 10 minutes while it pinged (not normal), it quickly flashed Cannot connect to server, then it said it was out of date and required 1.7.2 in the server list. I tried 1.7.2, and this greeted me. I would love an explanation as to how this happened, and a solution. The server is whitelisted: sovremenny.homeunix.org. The server owners believe that the fault is on my side. If you need any more details, just ask. However, I cannot give you everything. I don't own the server, and I don't control the Internet in my house.
It's a bug I experience as well, you should still be able to connect (or at least I am able to).
Oh. I get a ReadTimeoutException when I try. I haven't been able to connect for the last week. It's constant. This error only applies to this one server.
If the DNS record isn't updated properly, or your computer has a stale cached entry then the mapping from sovremenny.homeunix.org to an IP address would be wrong and you would see this behavior.
in an Administrator cmd shell run the command "ipconfig /flushdns" if that doesn't fix it, the issue is likely with the dyndns record.
If the DNS record isn't updated properly, or your computer has a stale cached entry then the mapping from sovremenny.homeunix.org to an IP address would be wrong and you would see this behavior.
in an Administrator cmd shell run the command "ipconfig /flushdns" if that doesn't fix it, the issue is likely with the dyndns record.
What do you mean by "issue with the dyndns record"? Is that for the server or my pc? And how do I fix such an error?
>The server owners believe that the fault is on my side. If you need any more details, just ask. However, I cannot give you everything. I don't own the server, and I don't control the Internet in my house.
...so, I'm not sure how we can help.
The problem is, the internet connection between your PC and the server.
If you can't control the way that works, I'm not sure how we can help.
I can ask the person who does to try things. I just can't reveal specific details (the person is afraid of hackers, spammers, etc.). You know. But, all of this has definitely narrowed down my search for answers. Any more ideas?
Yeah, I have ideas. But I can't reveal specific details, you know.
Well, that's nice. But, don't blame me for my internet admin (i.e. my dad) being paranoid. I think I am pretty much at square one. This topic is closed, since nothing can be done.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumIt's a bug I experience as well, you should still be able to connect (or at least I am able to).
If the DNS record isn't updated properly, or your computer has a stale cached entry then the mapping from sovremenny.homeunix.org to an IP address would be wrong and you would see this behavior.
in an Administrator cmd shell run the command "ipconfig /flushdns" if that doesn't fix it, the issue is likely with the dyndns record.
What do you mean by "issue with the dyndns record"? Is that for the server or my pc? And how do I fix such an error?
I can ask the person who does to try things. I just can't reveal specific details (the person is afraid of hackers, spammers, etc.). You know. But, all of this has definitely narrowed down my search for answers. Any more ideas?
Well, that's nice. But, don't blame me for my internet admin (i.e. my dad) being paranoid. I think I am pretty much at square one. This topic is closed, since nothing can be done.
If the server is still not up for you, then the issue is with your PC, network or ISP.