I do not have a DNS server set up in my NT 4.0 environment, which I inherited from the previous network administrator....
By submitting your email address, you agree to receive emails regarding relevant topic offers from TechTarget and its partners. You can withdraw your consent at any time. Contact TechTarget at 275 Grove Street, Newton, MA.
In order to connect to Exchange Server 5.5, I have to have the private address of the Exchange Server in a hosts file, or change the RPC_Binding_Order so that 'ncacn_spx' comes before 'ncacn_tcp.' I have created a WINS server, but that didn't help. The Microsoft publication for Exchange Server 5.5 Resource Guide talks about setting up a DNS server for my internal network and blocking it at the firewall, so that it functions as an internal-only DNS server, but I can't seem to find information on how to configure DNS to make this happen. Help! You don't need to use ncacn_spx in your binding order unless you are using IPX/SPX to connect to Exchange. Since you said you were using a HOSTS file, I will assume that you are using TCP/IP. As such, you only need/want the following entries in your RPC_Binding_Order: ncacn_tcp,netbios.
This will use basic TCP/IP first and, if that fails, it will revert to NetBIOS. You'll need DNS for SMTP e-mail, and not for regular Exchange usage. You could get away with using NetBIOS name resolution only and still use Outlook and Exchange. As long as the Outlook client can resolve the Exchange server's name, you should be fine.
DNS is used to locate mail servers that can accept SMTP e-mail. These servers are designated in DNS as mail exchangers (aka MX records). If you are receiving Internet (or other SMTP e-mail), the sending servers will need to resolve an MX record for your domain. If you are sending SMTP e-mail, then your e-mail server will need to resolve an MX record for each domain to which mail is sent.
Dig Deeper on Microsoft Exchange Server Mailbox Management
Related Q&A from SearchExchange Staff
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.