Search results for query: *

Then the first thing to look at is your internal DNS and DNS setting for your Exchange and DC. For your Exchange and DC servers, make sure it is pointing to your internal DNS server? On your DNS server, you need to check if it has an A record for your DC, according to the article.

You could try creating an SMTP Connector and see if it solves your problem. Normally you don't require creating one and can just rely on the smpt virtual server, but since you are having this problem, it doesn't hurt to try. You can search microsoft website on how to create an smtp connector.

Have you referred to this? http://support.microsoft.com/default.aspx?scid=kb;en-us;294222&Product=exch2k

What error do you get? is it a user authentication problem?

Does this FAQ help? Configuring Exchange for multiple domains http://www.tek-tips.com/faqs.cfm?fid=3788

I'd say you deleted something you shouldn't have. If your Exchange transaction logs are filling up the space on your server, then you need to do a full backup of the server to clear the log files. To solve your internal mail problem, you could try reapplying the Exchange 2000 service pack to...

One possibility is DNS problems. Go to www.dnsreport.com and run the tests there. If necessary, take any remedial actions reported. Your DNS server settings for the mail may not be reporting to your ISP correctly. Are you experiencing high internet traffic for your network? This can also affect...

I'm assuming you are able to send/receive emails generally, and only want to clear those queues that are stuck. You could delete away those queues with messages from the postmaster if you think it is alright.Sometimes stuck queues can be due to one email in the queue (usually the oldest)...

You need to determine whether these are legitimate emails or others using your server to relay. Open SM, scroll down to the SMTP protocol queues, enumerate all the queues and see where the messages are sent from. If from your own users, then you are not an open relay. If from other users, then...

I once had a problem where new users created could not connect to their mailbox in Outlook. What I did was to enter the following commands at the cmd prompt of the Exchange Server - IPCONFIG/FlushDNS and IPCONFIG/RegisterDNS. After a while in the Event log it asked me to reboot my Global Catalog...

I would guess that something hapended to the recipient update service. Have a check on your recipient policy and recipient update service in System Manager. Recreate if necessary.

Are the new mailboxes residing on the same exchange server as the old mailboxes?

Click "Update Now" under Recipient Update Policy

I just found I have the same problem, but I believe it is with all attachments. I think this happened after I set up SSL on the IIS to enable the Change Password Option in OWA last week. Microsoft Knowledge base soultion to this problem is to apply the latest Exchange 2000 service pack. Although...

My advise is gather all your Software Medias (CDs etc) and paper licenses, count them and put them in one safe place. Check through the purchasing records to determine what has been purchased. I'm not sure how big your company is, and whether your company is on any select program with Microsoft...

Microsoft Outlook works fine for my SQL Server

Very simple. If your management is concerned about software piracy, just buy licenses for the shortages.

From what I unnderstand, Win2003 has a differnet licensing from Win2000. For 2003, there's per user licensing and there's per device licensing. From what I was told, ,if you have less users than device, than you choose per user licensing, or vice versa. You might want to post in Win2003 forum...

One possibility could be the security settings in the IE Browser. In IE, click on Tools->Internet Options->Security->Internet->Custom Level-User Authentication. One possible option is select "Automatic logon in Intranet only.

yes