DC++

Odd DNS/Connection Timeout Error

Asked by ktash

Ok, so I've read all of the other 'Connection Timeout' error questions, and none of them solve my problem. Ok, so I run a hub and connect to DC++ at the same time. I use No-ip.com for my DNS service, am on Windows XP Home, and am using DC++ .706 (Hub uses YnHub software, fyi). Alright, I know the hub is up, I know that it is working, but I can't connect using my DNS. It worked fine at the start, but then my ISP reset my IP so I got dropped from the server, and it went down until I switch the DNS. This is all fine and good and expected. Whats not expected is that DC++ won't connect to the server after the DNS switches to the new IP. I know its at the new IP and I know the DNS worked (first things I checked) because other users can connect using the DNS address. I can't seem to figure out why my computer and copy of DC++, though, won't switch to the new IP from the DNS. It just gives me a connection timeout. When I ping the DNS address with cmd, my system still uses the old IP, and I don't know why it does this. Oh, and connecting to localhost works, so that is how I know that other users are on. I think that DC++ is not letting my computer switch to the new IP somehow (if not, please correct me). Anyway, any help would be greatly appriciated. =)

Question information

Language:
English Edit question
Status:
Solved
For:
DC++ Edit question
Assignee:
No assignee Edit question
Solved by:
ktash
Solved:
Last query:
Last reply:
Revision history for this message
poy (poy) said : 		#1

from a command prompt, run:
ipconfig /flushdns
to empty your local DNS cache.

Revision history for this message
ktash (eni134) said : 		#2

I tried that on my command prompt to no avail. I even shutdown internet connected applications, and tried it, but still no result. Thank you though.

Revision history for this message
eMTee (realprogger) said : 		#3

I experienced the same when I temporarily hosted a hub of my friend on my hub server in my local network. It was an YNHub with no-ip DDNS address as well. I remember I also wasn't able to connect it through the DDNS address from a computer in my local network, I could use only my servers local ip:port.
This should be an YNHub related thing as at the same time I ran my permanent hub (PtokaX) on that server and I was (and am still) able to connect to my hub through its DDNS address (also no-ip) from the local network.
You may get an answer on the YN forum : http://www.ynhub.org/forum If so, please paste the link here, too :)

Revision history for this message
ktash (eni134) said : 		#4

http://www.ynhub.org/forum/showthread.php?t=7056 <-- Going to call this one a hiccup in my system. This is the thread on the YnHub forums I posted about it, but I was unable to recreate the issue, so I think it may have been a one time error. Thank you for your help.