Search results for query: *

Thanks, Andy.

I was curious if anyone has had difficulty running BES with Exchange 2003 SP1. I am planning the upgrade and was curious to find if any others have had difficulties with this.

You can setup a static IP and have your DNS host resolve a domain name to this IP (might want to make sure that it is a different server name than your POP3 hosted server.. i.e. if your POP3 server is mail.domain.com, then have your FQDN name to the IP, be mail1.domain.com). Then have your POP3...

Uncertain, but you can try using the IP address rather than the DNS name.

I have one Exchange 2003 user that has NDR messages from only one source (an external e-mail account). I receive NDR reports that have this error message "The e-mail account does not exist at the organization this message was sent to. Check the e-mail address, or contact the recipient directly...

To use all/most of the features of Exchange 2003, Outlook client/OWA is only way I know. POP3 would defeat the purpose of this upgrade, since the online collaboration tools, public folder features, disaster recovery options, etc. would all be lost. Might want to poke around...

You could upgrade your Exchange from 2000 to 2003. Exchange 2003 will run on Windows 2000 Server (with SP3). Windows 2000 SP3 or later is also a prerequisite for running the Exchange 2003 Active Directory Connector. Easiest/recommended (and of coarse most expensive) is a full upgrade. (check...

Since you mentioned that "All mail sent out..." is being stopped at the que, it is unlikely that black listing is your problem (simple check is mentioned above). If you are being used as a mail relay... you will get black listed, and would also cause your que to remain full, as you might be...

Change the IP range on the remote site. Internal to my lan I use 10.0.X.X with a subnet of 255.255.0.0 VPN users ususally have 192.168.0.X or 192.168.1.X

Generally, there are several ways to setup a VPN. A device/firewall, with another device or client on the other end (I have not used Fortinet 50 Firewall). This method, the users are authenticated to connect to the internal LAN, but will not be authenticated on the Windows Domain. I suggest...

See if you can use the internal IP address, when setting up the Outlook client... In OWA, are you using the the internal server name?

Make sure that you have a good antivirus engine and that it is properly configured (for exchange and pattern updates). Some of the newer viruses give NDR error messages (W32.Netsky.P@mm is one example... which just came out 3/21). Make sure that you are not an open relay...

http://www.mxlogic.com/ Spam, is it's best solution, runs about $1/user and requires minimal maintenance (runs on their servers)... they do have AV software, but it is on their server. This would not protect your internal mail. I have used Trend and Norton (both of the latest versions) and...

Does Smooth wall have VPN client software (not "pass through")? Looking for an alternative to Cisco PIX.

I believe you can have only one database (though you can also have the recovery database). That DB is limited to 16 GB.

Another resource I had used. http://enterprise.state.wi.us/home/directory_strategy_proj/Working%20Documents/How%20to%20set-up%20an%20Exchange%20Resource%20Forest.pdf

This can be done with the Microsoft Office Resouce Kit. I recommend against using *.pst files to store e-mail for users (though I have seen this done in a large 900+ user enviroment).

Yep. Create trust, then create user in exchange forest, then disable account, then "associate with external account" (seem to remember this in "Exchange Tasks", though has been awhile). Keep in mind, Microsoft does not recommend this (perhaps not even supported), as well as the...

One of our users have difficulty with OWA loading her mail box, while others are fine. Could be the 6,600 items of mail in her main inbox. I have encourage her to move them to sub folders, but she has yet to.

I have installed OWA/SSL two times. Both times, was with only one Exchange server. SSL cert. was installed on Exchange server (both times). First time, was with a Cisco PIX. Just did port forwarding through 443 (on PIX). Second time was with an ISA server. Required SSL cert to be installed...