My client called me for an operation in the network of his study. There was to do the upgrade of two systems from Windows 2000 to Windows XP, domain re-copy them back in the old system data and reconfigure the mail. The network is structured as follows (very basic): A Windows 2000 Server Domain with DNS and WINS services and a dozen XP clients. Smoothly except when configuring e-mail: Outlook can not resolve the domain name pop.DOMINIOCLIENTE.it and even the outgoing SMTP mail server ... I'll check the public DNS server (Provider Tiscali) and I Everything looks okay if you do not open all sites except the site www.DOMINIOCLIENTE.it and consequently not even the third-level domains, pop and smtp. I'll check the server domain and I realize that the local domain has the same name as the public and therefore the only solution to resolve the name is to provide the client with external DNS servers, but in so doing have a hard time to log in domain as they do not find it.
ANSWER: I entered in the various mail clients directly to the ip of the mail servers of the provider and the client as I entered the dns server ip dns procedure. So the login is immediate without errors applicazone local policy in the event log and the mail is working properly.
MORAL: Never use an extension for public local domains (. Com,. Com, etc.) but always use the extension. Or similar premises in order to avoid these unpleasant drawbacks.
ANSWER: I entered in the various mail clients directly to the ip of the mail servers of the provider and the client as I entered the dns server ip dns procedure. So the login is immediate without errors applicazone local policy in the event log and the mail is working properly.
MORAL: Never use an extension for public local domains (. Com,. Com, etc.) but always use the extension. Or similar premises in order to avoid these unpleasant drawbacks.
0 comments:
Post a Comment