Humor Me

OK. I realize that this is going to be resolved once I give the domain name hosts time to get it set up, but.....I've got to ask.

I've set up a FTP server. I have the domain name registered with network solutions and is repointed by earthlink's services.

Oddly I can connect using the address when on an OSX machine using this new domain name. OS9 and windows machines do not see it yet. Again I realize the setup by earthlink and NetworkSolutions isn't quite done but any guesses why my OSX machines are happy to figure it out?
(obviously if I type in the 64.xx.xx.xx all of them connect)

(I'd love to post my domain name but that just seems like I'm asking for trouble)
Who is Participating?
davebytesConnect With a Mentor Commented:
is 64.xx.xx.xx an internal address (behind a firewall/router) or the external-facing address?

If all machines have the same DNS, they should all be resolving to the same IP address.  That would seem to indicate you have routing problems or other protocol-access problems.

Sounds like the DNS isn't yet set up properly, or that you have a firewall somewhere interfering.

Are the OS X machines using different DNS servers than the others?
catmarlsonAuthor Commented:
all have the same DNS. OS9 and OSX.

OSX off site (called another friend) cannot use the domain name to enter the FTP server either.

The really odd part is that if he opens safari and types in the domain name as if it was a webpage address. He gets an error "cannot connect to 64.xx.xx.xx" Which is the right # address. Yet if he puts it in as an ftp it won't connect either.

I realize this is a really dumb problem and that earthlink and network solutions will get it fixed. I'm just really curious how it all works and things like this confuse the issue.
I'm wondering if rendezvous has a part in the local network. Or if my router's port forwarding somehow picks it up. (this is on my 2 router setup and the port forwarding router is not the "gateway" for the comptuers).
Anyhow I'm confusing the issue. As always a little knowledge is dangerous.
Never miss a deadline with

The revolutionary project management tool is here!   Plan visually with a single glance and make sure your projects get done.

To find out where the OSX resolve the name, go to Terminal, and type in 'nslookup ftp.<mydomainname>.com'  or 'dig ftp.<mydomainname>.com'
It will show you which DNS SERVER that translate the domain name.

The OSX that can connect to ftp.<domainname>.com = OSX that serve as FTP server?  If so, then it is possible that your ftp.<domainname>.com = host name of the machine?

If your OSX machine is in the same subnet (which is controlled by your router) as the FTP server, then just entering in the domain that your FTP server is answering will get you there. But if you're on a different subnet you won't see it unless the router has been configured to let it happen. People on the outside would not see it for the same reason, as well as the info not being entered correctly at Network Solutions and Earthlink. Also, be aware that after they have made their changes, it may take several days for the domain to propagate and appear properly by name.
catmarlsonAuthor Commented:
Sorry this took so long.

As it turns out our Provider turned on firewall settings at their setup in their office. So that was blocking any of the port mapping I had done. So the in house stuff would work ok but nobody from outside.

As for the osX os9. I'm pretty close to saying OS9 who???
(isn't it great to get really good at a system just to have it replaced every year)

Thanks all
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.