RE: Strange Mail Problems with SBS 2003[Scanned]

  • From: "Simon Bound" <simon.bound@xxxxxxxxxxxxxxxxxxxx>
  • To: "[ExchangeList]" <exchangelist@xxxxxxxxxxxxx>
  • Date: Thu, 22 Jul 2004 12:14:10 +0100

I have also been having issues with SBS 2003, more specifically Outlook 2003 
clients lose connection to the Exchange server after about a day..
Make sure that your have installed Exchange 2003 SP1 (99mb download). If you 
have more than 1gb RAM on the server use the /3gb switch - yes that's more than 
1gb. I am advised that if you only have 1gb (in my case) the 3gb switch is not 
Go the Windows Update site for SBS and download all the patches there. One of 
those addresses an OWA issue.
Make sure DNS has been configured correctly by your "consultants". Look on the 
Internet re. naming/domain issues where SBS Exchange uses a "local" extension 
even though the actual domain e-mail address is in your case is There 
may of course be an underlying issue with Outlook 2003 so make sure you go the 
Office update site and get all those updates for your 

As you might have guessed I am not impressed with SBS 2003 and Exchange where 
as SBS 2K with Exchange was just fine. 


-----Original Message-----
From: Technical [mailto:tech@xxxxxxxxxxxxxxxxxx]
Sent: Thursday, July 22, 2004 9:53 AM
To: [ExchangeList]
Subject: [exchangelist] Strange Mail Problems with SBS 2003[Scanned]

Hi All

I am having lots of strange problems with mail on SBS 2003.

These include:

1) Activesync not working against the server

2) Outlook Web Mail not working on any client other running it on the

3) Outlook 2003 users (randomly) being unable to send mail to each other
with the error "You do not have permission to send to this recipient" These
mails are mainly internal to internal.

When the server was sent up by the consultants the domain was set as where as all email addresses are actually

The users email addresses are firstname.surname@xxxxxxxxxxxxx and their
logins are initialsurname.

So the server name is

user email addresses are john.doe@xxxxxxxxxxxxx ( is
not used anywhere and does not exist)

Could all these problems be caused by this mismatch between domain names????

My gut feel is to reinstall the server using the correct domain etc...

Any thoughts (including a large hammer) welcomed.

A very frustrated administrator.

List Archives:
Exchange Newsletters:
Exchange FAQ:
Other Internet Software Marketing Sites:
World of Windows Networking:
Leading Network Software Directory:
No.1 ISA Server Resource Site:
Windows Security Resource Site:
Network Security Library:
Windows 2000/NT Fax Solutions:
You are currently subscribed to this Discussion List as: 
To unsubscribe visit

Other related posts: