Forum Moderators: phranque
When I try to ftp to one of my Web hosts using the domain name (ftp.mydomainname.com), I receive the (dreamweaver) message: "An ftp error occurred - cannot make connection to host. The remote host cannot be found." I get similar results with prishtinaFTP: "Host not found."
If I ftp with the IP address, I get in. I have been having intermittent problems with both http (browser) and ftp to this site, and others located at the site, but the problems have mainly been with ftp recently. By that I mean that at times I could access via FTP but not by HTTP, or vice versa.
When I check the site from those services that let you know if they can reach it from 5 spots around the world, like alertra.com, it's generally available. This tells me that the host is probably okay, but my ISP or my machine is causing the problem. Have I missed something?
I've tried ipconfig /flushdns from the command line. No change.
I've tried rebuilding the tcp/ip settings. No change.
I have parked the domain names, and then reset them for my Web host after waiting 15 minutes. Since sites around the world can find the site, I can't imagine that resetting the DNS again would help, am I wrong?
The ISP told me that they changed dns servers a few days ago, but I'm still having trouble. Is there something they could do to flush my domain name, or?
What more can I try? This is pretty darn frustrating. Does any one have ideas?
TIA,
zw
[edited by: zollerwagner at 9:36 pm (utc) on Feb. 13, 2003]
just use mydomainname.com
Windows 9x: C:\WINDOWS\hosts
Win NT/2k/XP: C:\WINNT\system32\drivers\etc\hosts
Instructions on how to add entries are provided within the hosts file.
I see now that I can't access my other domain names on this site with www. or ftp.
I can ping www.mydomainname.com, but not other domain names on the same host, and none of them can I ping for ftp.mydomainname.com.
Until I find the reason behind these problems, I won't feel sure that I'm the only one having trouble accessing the site.
Thanks for the help, at least I can get in!
Sounds like DNS issues. Add entries to your local hosts files and you can reliably associate IPs to a domain. This will bypass the remote DNS servers for those IPs.
Windows 9x: C:\WINDOWS\hosts
Win NT/2k/XP: C:\WINNT\system32\drivers\etc\hostsInstructions on how to add entries are provided within the hosts file.
In XP's help, there's a paragraph that may be related to this that seems to reflect what you're saying:
You can use ping to test both the computer name and the IP address of the computer. If pinging the IP address is successful, but pinging the computer name is not, you might have a name resolution problem. In this case, ensure that the computer name you are specifying can be resolved through the local Hosts file, by using Domain Name System (DNS) queries, or through NetBIOS name resolution techniques.
Following your suggestion, I have added entries for the three domains on that Web host's server. They appear when I run ipconfig /displaydns a the command line.
In the browser, I am able to reach one page with www.mydomain.com or mydomain.com
I am able to reach the other two with mydomain.com, but not www.mydomain.com
I get the same results using ping from the command line.
In fact, these are exactly what is listed in the ipconfig /displaydns listing. (i.e. there are no entries for the two www.mydomain.com's that I can't access with www.)
For FTP, I can reach all of them with mydomain.com, but none of them ftp.mydomain.com, even with the additions to the hosts file.
I read the instructions in the IMHOST file, too, but wasn't sure this related to my issue. The following made me think it could be useful:
# Following any entry in the file with the characters "#PRE" will cause
# the entry to be preloaded into the name cache. By default, entries are
# not preloaded, but are parsed only after dynamic name resolution fails.
From another computer that I haven't done any adjustment of the hosts file, I can't do much of anything besides access the first domain name with
Where do you think this problem lies? Is it likely to be in the ISP's dns server? with the Web host? with my computer?
I'll log off and try AOL to see what a different ISP does tonight.
What would you do about it. Beyond my frustrations getting to the site, is this important for other users of the site?
Thanks!
I got on to all three domain names, with www. or without it. I got into FTP with ftp.mydomain.com.
Doesn't that say that the ISP I'm using has a problem?
What do I ask them to do for me?
TIA!
Doesn't that say that the ISP I'm using has a problem?
I'd agree. If you requested any DNS changes to your accounts, I'd give it 72 hours to allow complete migration of the DNS entries to all the other servers. If you still encounter these issues after that time, put in a ticket to your ISP describing again what you described here. I doubt you'll get much help on Level 1, but you'll have to jump through the hoops before being transfered up to senior person who can help you with this.
It's miserable not knowing if I'm going in the right direction here in the desert....
I really appreciate the help.
What concerns me more is that I often can't get to my sites in my browser. If I can't, then I assume that anyone else who is hooked up to whatever this weak link is can't see the sites, either. I'm hoping it's my ISP, because that will be a smaller subsection of viewers, but there are people on this ISP that will want to visit the sites.
Thanks for the feedback.
ZW
I also realized--perhaps a little slowly--that if I add all three forms to the host file, I c an use www.mydomain.com or mydomain.com in the browser and ftp.mydomain.com in the FTP client. Earlier I had added just the mydomain.com to the hosts file.
All of that tells me, again, that I'm able to get to the site only if I force my way past the ISP's problems.
I've talked to my ISP, who says their DNS server updates very slowly (I believe that!) and that I should wait 2 weeks! My goodness.....
make sure that image compression is set to "never"
set your browser cache to 0
quit aol
restart aol
Most of the www "enhancements" in the Internet properties are just aol cache settings (not local).
That's interesting, I was wondering whether it was possible to turn of the AOL image compression. I can see why they'd want to do the compression, given that newbies often post huge files, but it's no good for those of us who have already compressed an image before uploading it.
I'll check those other settings, too, although I only use AOL for testing.
Thanks!
