MS SBS 2003 Exchange Server Name

pts.
Tags:
Microsoft Exchange
Microsoft Windows
SBS 2003, Exchange Server 2003 I have an external domain 'name.org' and an internal domain 'name.local' I can't connect to exchange from Outlook 2003 from the internel (OWA works). Running ipconfig /displaydns I see the internal name of the exchange server 'machine.name.local' which can not be resolved. Any help would be greatly appreciated, thanks!

Answer Wiki

Thanks. We'll let you know when a new response is added.

Hi,

PLease check one OR all below

1) Is local m/c joined in domain?
2) IMAP service is running on exchange servcer OR not?
3) DNS servcer configuration/

Please revert for any queries.

Regards
-Amrik
91-9971127634

Discuss This Question: 6  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • Knritk
    1) Is local m/c joined in domain? Yes 2) IMAP service is running on exchange servcer OR not? It is not running 3) DNS servcer configuration/ yes
    0 pointsBadges:
    report
  • Dwiebesick
    In configuring your SBS, did you use the wizards that are part of the SBS, or did you manually configure the server? According to Microsoft, use of the SBS wizards in configuring the server is not optional, it is a 'must' in order to properly configure all the settings. Microsoft made the SBS to be 'maintained' by the business owner and to not 'require' system administrator. If you did not use the wizards, I highly suggest you try that first. dmw
    2,235 pointsBadges:
    report
  • Knritk
    I did use the wizards.
    0 pointsBadges:
    report
  • Dwiebesick
    From what you said "ipconfig /displaydns I see the internal name of the exchange server 'machine.name.local' which can not be resolved" This is an indication that your DNS is not properly setup. I would go back to the 'Connect to the Internet' wizard. Else you can use dnsdiag from W2k3 resource kit and troubleshoot what when wrong in your configuration of DNS. dmw
    2,235 pointsBadges:
    report
  • Knritk
    I re-ran the connect to internet wizard and discovered the mail server setting was set to name.org but according to the help it should be the name in the MX record so I changed it to mail.name.org. The configuration then completed with an an error "an error occurred while configuring a component ..." I had to restart the exchange Info store, smtp and had to start all web sites. I reran the wizard several times and still got the same error. Funny thing is, exchange still works with OWA and internal outlook clients. The remote outlook client fails to check the name in the Mail configuration (from control pannel) now stating it can not connect with exchange (this occurs when I specified mail.name.org). I've run dnsdiag and saw nothing peculiar and I also ran smtpdiag.exe with no errors. I did read a couple of things: one about FE/BE servers and that the remote Outlook was looking for mail boxes on the FE and resorting to the BE which is the local machine. The other article (which I can't find now) stated something about setting up the MX record in the forward lookup zones? Thanks for all your help and I greatly appreciate further assistance.
    0 pointsBadges:
    report
  • Shadyj
    In order to connect to Exchange from offsite, you need to enable RPC or connect through VPN (Connect to Small Business Server). See http://www.petri.co.il/configure_outlook_2003_to_use_rpc_over_http.htm for more info.
    0 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following