exchange server

search for more blogs here

 

"Access Exchange server over VPN" posted by ~Ray
Posted on 2008-10-10 03:17:36

I have an end-user with a laptop running Windows Vista and he has Outlook 2007 as his e-mail client software. He is using Checkpoint SecuRemote VPN software to access the corporate Exchange server cluster. Using wireless LAN connection from his home in Australia to access Exchange server cluster in Chicago. USA. Problem: the end-user can connect to the Internet and browse the web... he can also logon to our corporate network using the VPN client. What he can't do is access the Exchange server... the user can "ping" the server and get a proper response.. so the datagrams are being routed correctly. I tested his user account on the Exchange server by accessing his e-mail account from my home laptop over my wireless connection in Chicago... so his account is also good.... the user can also access his e-mail over the Internet from Australia using Outlook Web Access with no problem. Question: what can be blocking his SMTP access to his account using Outlook 2007?... I've verified with him over the phone the Outlook configuration is correct... using the IP address of the server rather than the server name so we're not dependent on DNS name resolution. Any suggestions would be greatly appreciated. In Outlook make sure that the fully qualified domain name is being used for the Exchange server. I see this sort of thing when using VPN; the client machine may be using the ISP's DNS servers and it may not know to append the company's DNS suffix to the name. Maybe the client is pinging using the FQDN. It must not be rule settings on the VPN server or you wouldn't have been able to access his mailbox unless for some reason the needed protocols are allowed only from certain IP addresses but that's doubtful. Speaking of protocols. SMTP is not the one he needs to get his mail it's RPC as far as I know. Thanks for responding Charlie.... I stand corrected about the Exchange protocol. Already tried using FQDN in the server name field on the client.... I opted to put the IP address in the name field to rule out a DNS problem. I decided to let a tech coming off of vacation who is based in Sydney handle this issue since she can get her hands on the laptop... thanks again for your input. Don't use a host file - YOu must use the Exchange server name. The biggest problem with this setup is usually that you are either not authentcating on the donmain as the laptop is not joined or that the routing to the Exhange server is not being directed through the VPN. The VPN should give you a local address on the remote LAN as a gateway and set up a route to that network. It will not update the routes to other network segments so you may have to add them manually using the "route" utility. With Route you can set up a permamnent route to teh subnet that contains the Exchange server and force it to gpo through the VPN. Exchange must be set up to allow for the kind of authentication that youare going to use. If you use "integrated" authentication then you must be authenticated on the domain by some mechanism. If your company uses RPC over HTTP then you will have to set that up according to the requirements established by your IT department. The tech will know or be able to find out the correct method of connecting for your company. Personally I prefer using a domain connection with a VPN as it is more seemless and all settings will work both over the VPN and when directly attached to teh network. THe other method that I think is best for mobile email without a VPN is to use OWA - Outlook Web Access which is nboth secure and easy to set up (no setup required). OWA can use any browser from any PC/Mac or Linux box using HTML/Browser technology. Just point your browser at teh web site and provide your credentials and your in. If your company needs more security then requier that all PCs have a certificate to use for encryption/authentication and hand out certs to approved users at approved locations or from approved PCs. Certs can be handed out and approved using a simple web site. We have a number of remote users. The problem we ran into using OWA is that they could not archive their email. We have them access the network through the VPN. Once they authenticate through the VPN They are assigned an IP by a local DHCP server. Rather than RDP to a terminal server or another desktop we set up the Host file on their machine. When they open Outlook they are required to log into the domain (just like with OWA) This allows them to run Outlook on their machine and archive their email on their laptop. We are on a simple one subnet network,this is how we set it up its working for us choward87-yes that is a very commoon way to set up Outlook assuming that the network security allows this which should be the default for WS2003 domains. It also requies that the security on Exchange has not been tightened completely as it may be in some networks. DHCP should assign a proper gateway and route for the connected IP segment but will not update other segment routes unless set up for it. Using a hosts file has become out-of-date although it still works. Problem is it is a pain to maintain on dozens to hundreds of mobile systems. There is a wizard that can build a VPN depployment package the will maintain all of these settings- CMAK. You can also deploy the updates and phonbook over a web server. The issue with teh hosts file says that you don't have the DNS settings set up correctly. In many cases a server may have both a public facing interface and an Intranet interfac. If teh public host name is the same as teh Intranet host name then you will get th e wrong IP and try to connect over the Internet instead of over the VPN. Add an extra DNS host record for Exchange use over the Intranet/VPNL Assuming Exchange host name in mail domain com Assuming Intranet domain is domain local then you whuold have a record for mail domain local and a record for mail domain com. If the internal an external domain names are the same - and they shouldn't be - add "internalmail domain com" pointing to the Intranet IP of the server. You can also dummy up host names in the deployment file using CMAK. Be sure DHCP associates an Intranet (ActiveDirectory) DNS s4erver with the DHCP allocation. You will need this to resolve Intranet names providing thsy are not duplicated on teh Internet. The AD DNS server should not be visible from the Internet nor should the internal domain name hence the practice of using domain local in place of domain com.

Forex Groups - Tips on Trading

Related article:
http://redmondmag.com/forums/forum_posts.asp?tid=3978#2

comments | Add comment | Report as Spam


"Access Exchange server over VPN" posted by ~Ray
Posted on 2008-10-10 03:16:12

I have an end-user with a laptop running Windows Vista and he has Outlook 2007 as his e-mail client software. He is using Checkpoint SecuRemote VPN software to access the corporate Exchange server cluster. Using wireless LAN connection from his home in Australia to access Exchange server cluster in Chicago. USA. Problem: the end-user can connect to the Internet and browse the web... he can also logon to our corporate network using the VPN client. What he can't do is access the Exchange server... the user can "ping" the server and get a proper response.. so the datagrams are being routed correctly. I tested his user account on the Exchange server by accessing his e-mail account from my home laptop over my wireless connection in Chicago... so his account is also good.... the user can also access his e-mail over the Internet from Australia using Outlook Web Access with no problem. Question: what can be blocking his SMTP access to his account using Outlook 2007?... I've verified with him over the phone the Outlook configuration is correct... using the IP address of the server rather than the server name so we're not dependent on DNS name resolution. Any suggestions would be greatly appreciated. In Outlook make sure that the fully qualified domain name is being used for the Exchange server. I see this sort of thing when using VPN; the client machine may be using the ISP's DNS servers and it may not know to append the company's DNS suffix to the name. Maybe the client is pinging using the FQDN. It must not be rule settings on the VPN server or you wouldn't have been able to access his mailbox unless for some reason the needed protocols are allowed only from certain IP addresses but that's doubtful. Speaking of protocols. SMTP is not the one he needs to get his mail it's RPC as far as I know. Thanks for responding Charlie.... I stand corrected about the Exchange protocol. Already tried using FQDN in the server name field on the client.... I opted to put the IP address in the name field to rule out a DNS problem. I decided to let a tech coming off of vacation who is based in Sydney handle this issue since she can get her hands on the laptop... thanks again for your input. Don't use a host file - YOu must use the Exchange server name. The biggest problem with this setup is usually that you are either not authentcating on the donmain as the laptop is not joined or that the routing to the Exhange server is not being directed through the VPN. The VPN should give you a local address on the remote LAN as a gateway and set up a route to that network. It will not update the routes to other network segments so you may have to add them manually using the "route" utility. With Route you can set up a permamnent route to teh subnet that contains the Exchange server and force it to gpo through the VPN. Exchange must be set up to allow for the kind of authentication that youare going to use. If you use "integrated" authentication then you must be authenticated on the domain by some mechanism. If your company uses RPC over HTTP then you will have to set that up according to the requirements established by your IT department. The tech will know or be able to find out the correct method of connecting for your company. Personally I prefer using a domain connection with a VPN as it is more seemless and all settings will work both over the VPN and when directly attached to teh network. THe other method that I think is best for mobile email without a VPN is to use OWA - Outlook Web Access which is nboth secure and easy to set up (no setup required). OWA can use any browser from any PC/Mac or Linux box using HTML/Browser technology. Just point your browser at teh web site and provide your credentials and your in. If your company needs more security then requier that all PCs have a certificate to use for encryption/authentication and hand out certs to approved users at approved locations or from approved PCs. Certs can be handed out and approved using a simple web site. We have a number of remote users. The problem we ran into using OWA is that they could not archive their email. We have them access the network through the VPN. Once they authenticate through the VPN They are assigned an IP by a local DHCP server. Rather than RDP to a terminal server or another desktop we set up the Host file on their machine. When they open Outlook they are required to log into the domain (just like with OWA) This allows them to run Outlook on their machine and archive their email on their laptop. We are on a simple one subnet network,this is how we set it up its working for us choward87-yes that is a very commoon way to set up Outlook assuming that the network security allows this which should be the default for WS2003 domains. It also requies that the security on Exchange has not been tightened completely as it may be in some networks. DHCP should assign a proper gateway and route for the connected IP segment but will not update other segment routes unless set up for it. Using a hosts file has become out-of-date although it still works. Problem is it is a pain to maintain on dozens to hundreds of mobile systems. There is a wizard that can build a VPN depployment package the will maintain all of these settings- CMAK. You can also deploy the updates and phonbook over a web server. The issue with teh hosts file says that you don't have the DNS settings set up correctly. In many cases a server may have both a public facing interface and an Intranet interfac. If teh public host name is the same as teh Intranet host name then you will get th e wrong IP and try to connect over the Internet instead of over the VPN. Add an extra DNS host record for Exchange use over the Intranet/VPNL Assuming Exchange host name in mail domain com Assuming Intranet domain is domain local then you whuold have a record for mail domain local and a record for mail domain com. If the internal an external domain names are the same - and they shouldn't be - add "internalmail domain com" pointing to the Intranet IP of the server. You can also dummy up host names in the deployment file using CMAK. Be sure DHCP associates an Intranet (ActiveDirectory) DNS s4erver with the DHCP allocation. You will need this to resolve Intranet names providing thsy are not duplicated on teh Internet. The AD DNS server should not be visible from the Internet nor should the internal domain name hence the practice of using domain local in place of domain com.

Forex Groups - Tips on Trading

Related article:
http://redmondmag.com/forums/forum_posts.asp?tid=3978#2

comments | Add comment | Report as Spam


"Want to know more about Exchange 2007 SP1?" posted by ~Ray
Posted on 2008-03-26 01:30:08

Unlike the typical service pack. Exchange Server 2007 Service Pack 1 provides a lot more than just hotfixes and security updates. Here's an overview of some of the most important new features and capabilities SP1 has to furnish. One of the most exciting features offered by Service Pack 1 is Standby Continuous Replication. sight out how this can back up you alter uptime limit data loss and simplify e-mail maintenance and retention. Getting ready to run transfer on Windows Server 2008? The Microsoft Exchange Development team has been doing this for a while now and Paul Bowden shares some advice and lessons they've learned to help you get ready. Combining voicemail fax capabilities and telecommunicate messaging into a single mailbox may seem desire a daunting assign. But it's easier than you think. Here's a command to deploying unified messaging in your organization.

Forex Groups - Tips on Trading

Related article:
http://blogs.technet.com/john_westworth/archive/2007/11/29/want-to-know-more-about-exchange-2007-sp1.aspx

comments | Add comment | Report as Spam


"Want to get Exchange 2007 SP1?" posted by ~Ray
Posted on 2008-01-07 23:32:15

Microsoft Exchange Server 2007 function Pack 1 (SP1) has been designed specifically to help meet the challenges of any business and the needs of all the different groups with a stake in the messaging system. Exchange Server 2007 SP1 is a mission-critical communications tool that enables employees to be more productive and access their information anywhere and anytime while providing a messaging system that enables rich efficient access to e-mail calendar items express mail and contacts. For the administrator. Exchange Server 2007 SP1 provides advanced protection options against telecommunicate security threats such as spam and viruses as well as the tools to help manage internal compliance and high availability needs. In transfer Server 2007 SP1 several new features and improvements will extend the Anywhere find capabilities of Exchange Server 2007 to back up make employees more productive on whatever device they’re using provide additional Operational Efficiency tools for administrators seeking a streamlined management and deployment experience and alter advanced Built-in Protection for more robust high availability and compliance scenarios. Improvements in Exchange Server 2007 SP1 include: Anywhere Access• Integrated Exchange Unified Messaging functionality with Microsoft Office Communicator 2007 and Microsoft Office Communications Server 2007.• Outlook Web Access additions including public folder access. S/MIME support personal distribution lists and mailbox rules editor.• Webready document viewer supports Microsoft Office 2007 documents in addition to Microsoft Office 2003 documents.• Extended language support in Outlook Web Access with Arabic and Korean spell checking. Operational Efficiency• Support for Windows Server 2008 deployments including benefits in flexible clustering native virtualization advanced networking and simplified management.• Additional tools in the Exchange Management Console including public folder management and configuration options for clustering and POP/IMAP access.• Improvements to the Exchange Management bomb syntax and import-export PST in the move-mailbox command.• Wider variety of web services for application development including public folder access delegate management and folder level permissions. Built-in Protection• Addition of Standby Continuous Replication (SCR) for place resilient high availability deployments.• Extended Exchange ActiveSync policies for mobile policy enforcement.• Information rights management.

Forex Groups - Tips on Trading

Related article:
http://blogs.technet.com/john_westworth/archive/2007/11/29/want-to-get-exchange-2007-sp1.aspx

comments | Add comment | Report as Spam


"Exchange Server 2007 SP1 Coming Friday" posted by ~Ray
Posted on 2007-12-15 17:31:52

12/13/07 Santa's not due for awhile yet but for those waiting on Microsoft's next version of its highly-anticipated virtualization product it's Christmas day. x64 Happiness "I met with Brian Valentine our Sr. VP in charge of Windows who asked that I take on running the x64 communicate. He points over to [original Windows NT architect] Dave Cutler's office nearby and says my job will be to make sure Dave is happy. [Then] Brian lets out a good laugh." — One of many tidbits from a lengthy April 5 post aptly named. "Windows Server 2003 SP1 and X64 Editions - A Historical Perspective," by Clyde Rodriguez a assort program manager in the Windows Server Division.

Forex Groups - Tips on Trading

Related article:
http://redmondmag.com/news/rss.asp?editorialsid=9284#1

comments | Add comment | Report as Spam


"Exchange 2007 Service Pack 1 due November 30" posted by ~Ray
Posted on 2007-12-09 15:06:31

According to the latest Technet Flash email newsletter of November 28. 2007. transfer 2007 with Service Pack 1 will be accessible for ( .. UPDATE:Download link is working today 11/29) on November 30. 2007. The mentions sp1 as well suggesting you might "check for the impending release announcement on the." is incorporated into transfer 2007 RTM. This is important to cater requirements for installing on Windows 2008 Server. It also makes it easy to deploy for new installations without requiring a separate function case installation. Windows 2003 needs to have Service Pack 2 applied prior to Exchange 2007 sp1. Much of the current documentation in the transfer TechCenter has referenced the following for quite some time: Applies to: transfer Server 2007. transfer Server 2007 SP1. William Lefkovics on November 29. 2007 at 01:14 AM in || TrackBack URL for this entry:http://www typepad com/t/trackback/208/23759594 Listed below are links to weblogs that reference : Powered by All posts are the procure of Meirick. Hobson & Lefkovics

Forex Groups - Tips on Trading

Related article:
http://hellomate.typepad.com/exchange/2007/11/exchange-2007-s.html

comments | Add comment | Report as Spam


"Exchange Admin 101: Exchange 2003 and Exchange 2007 admin privileges" posted by ~Ray
Posted on 2007-11-29 19:19:55

Organizations rarely apply a single level of administrative rights anymore because of the potential security problems that this can introduce. In larger organizations for example it's common to undergo several different administrators each with permissions to manage a specific contained aspect of the network. In smaller organizations there often is a primary administrator who oversees a assort of junior administrators. This tip explains the available administrative privileges in transfer Server 2003 and Exchange Server 2007 and the differing levels of control that each admin role allows. Exchange Server 2003 has different levels of administrative responsibility and supports three types of administrative roles: Exchange Full Administrator. Exchange Administrator and Exchange believe Only Administrator. transfer Organization Administrator: This role is the most powerful of the transfer Server 2007 administrative roles. An administrator who has been assigned to this role has full control over the entire transfer 2007 organization. The Exchange Organization Administrator role is required for any administrator who must make high-level changes to the organization. For example an administrator must be assigned the transfer Organization Administrator role if he wants to create a connector or make any other type of organization-level dress. The powers of an Exchange Organization Administrator aren't limited to the organization level. These administrators can also bring home the bacon recipients and transfer servers just as an Exchange Full Administrator would be able to in Exchange 2003. transfer Recipient Administrators are also granted create verbally find to any Exchange-specific attributes of the user objects within a domain. This means that they can see all user accounts within a domain but can only alter changes to those accounts if the changes relate to the users' mailboxes. When Exchange Server 2007 is installed onto a server. Setup creates a security group named Exchange Server Administrator <servername>. Administrators with the transfer Server Administrator hold back are members of this assort and undergo beat control over the server in question. The administrator will have full access to all of the server's configuration data and can take on the role of a local Windows administrator (not a domain administrator). transfer Server Administrators also appointed to the role of transfer View-only Administrators. While transfer Server Administrators have total hold back over a specific server they cannot bring home the bacon recipients. This role is used most often to accept an administrator in a branch office to maintain an transfer Server located within that office. About the compose: Brien M. Posey. MCSE is a Microsoft Most Valuable Professional for his bring home the bacon with Exchange Server and has previously received Microsoft's MVP award for Windows Server and Internet Information Server (IIS). Brien has served as CIO for a nationwide arrange of hospitals and was once responsible for the Department of Information Management at assemble Knox. As a freelance technical writer. Brien has written for Microsoft. TechTarget. CNET. ZDNet. MSD2D. Relevant Technologies and other technology companies. You can visit Brien's personal Web site at. Please let others know how useful this tip was via the rating scale below. Do you know a helpful Exchange Server. Microsoft Outlook or SharePoint tip timesaver or workaround? to communicate about writing for SearchExchange com DISCLAIMER: Our Tips Exchange is a forum for you to overlap technical advice and expertise with your peers and to hit the books from other enterprise IT professionals. TechTarget provides the infrastructure to aid this sharing of information. However we cannot guarantee the accuracy or validity of the material submitted. You accept that your use of the Ask The Expert services and your reliance on any questions answers information or other materials received through this Web site is at your own risk.

Forex Groups - Tips on Trading

Related article:
http://searchexchange.techtarget.com/tip/0,289483,sid43_gci1283791,00.html?track=sy188&asrc=RSS_RSS-19_188

comments | Add comment | Report as Spam


"DST: How to address daylight saving time in Exchange Server by ..." posted by ~Ray
Posted on 2007-11-11 16:10:05

Steve Justice. Escalation Engineer from our Microsoft transfer Support aggroup provides a walkthrough of using the Exchange schedule Update Tool to update misplaced items in a calendars in an Exchange environment.  For more information about the Exchange schedule modify Tool see the following Knowledge locate article:How to communicate daylight saving measure by using the Exchange schedule modify ToolSee these other helpful videos to back up you in your DST planning:DST: Cumulative Time govern modify for Microsoft Windows DST: Using the Outlook v2.0 Time govern Data Update Tool See for more details about how to alter for the upcoming DST changes for all Microsoft products.  Thanks for watching!The Microsoft DST TeamTags: .

Forex Groups - Tips on Trading

Related article:
http://channel9.msdn.com/ShowPost.aspx?PostID=341747#341747

comments | Add comment | Report as Spam


"DST: How to address daylight saving time in Exchange Server by ..." posted by ~Ray
Posted on 2007-11-11 16:10:05

Steve Justice. Escalation design from our Microsoft Exchange give Team provides a walkthrough of using the transfer Calendar Update drive to update misplaced items in a calendars in an transfer environment.  For more information about the Exchange schedule Update Tool see the following Knowledge locate article:How to address daylight saving time by using the transfer schedule modify ToolSee these other helpful videos to back up you in your DST planning:DST: Cumulative Time govern modify for Microsoft Windows DST: Using the Outlook v2.0 Time govern Data modify Tool See for more details about how to alter for the upcoming DST changes for all Microsoft products.  Thanks for watching!The Microsoft DST TeamTags: .

Forex Groups - Tips on Trading

Related article:
http://channel9.msdn.com/ShowPost.aspx?PostID=341747#341747

comments | Add comment | Report as Spam


"Linens and more website..." posted by ~Ray
Posted on 2007-11-08 15:32:12

Look for linens , beach and bath towels, and more at TowelTown.com
stop by anytime

comments | Add comment | Report as Spam


 

 




blogs - aa blogs - air force blogs - aquarius blogs - aries blogs - army blogs - arts blogs - baby blogs - blogs 4 men - blogs 4 women - cancer blogs - capricorn blogs - career change blogs - choice blogs - christmas blogs - cigar blogs - cigarette blogs - cig blogs - coast guard blogs - coffee bean blogs - college baseball blogs - college basketball blogs - college football blogs - colleges blogs - computer blogs - create blogs - dating blogs - elvis blogs - email chat blogs - email pal blogs - enhancement blogs - fall blogs - fha blogs - freedom blogs - friendly blogs - funny blogs - gambler blogs - gemini blogs - her blog - his blog - hockey blogs - join blogs - javas blogs - kid safe blogs - leo blogs - libra blogs - apartments blogs - coffees blogs - horoscopes blogs - life advice blogs - lover blogs - marine blogs - married blogs - military blogs - misc blogs - more money blogs - mortgage blogs - move blogs - movies blogs - musical blogs - navy blogs - new in town blogs - obscure blogs - online date blogs - online game blogs - over 30 blogs - over 40 blogs - over 50 blogs - over 60 blogs - over 70 blogs - over 80 blogs - over 90 blogs - password blogs - pc blogs - mortgages blogs - peoples blogs - pictures blogs - pipe blogs - pisces blogs - poems blogs - poker blogs - police blogs - political blogs radio blogs - read blogs - recreational vehicle blogs - relocation blogs - reserve blogs - rv blogs - safe blogs - scorpio blogs - singles blogs - smokers blogs - smoker blogs - state blogs - state college blogs - taurus blogs - teen advice blogs - teenager blogs - tobacco blogs - tv blogs - vacation blogs - veteran blogs - virgo blogs - virtual blogs - weekly blogs - wingman blogs - word blogs - words blogs - writer blogs - poetry blogs - prescription blogs - sagittarius blogs - straight blogs - summer blogs - gi blogs - hooka blogs - penis enlargement blogs - vfw blogs - casinos blogs - casino blogs - web hosting blogs - hosting blogs - auto blogs - truck blogs - van blogs - suv blogs - 4 wheel blogs - harley blogs - flu blogs - diet blogs - pistols blogs - teenage blogs - lpga blogs - burnable blogs - new tunes blogs - coaching blogs - treasures blogs - trades blogs - nutty blogs - skate blogs - play 21 blogs - weather blogs - poker players - golf blogs - american blogs - football blogs - baseball blogs - hockey blogs - basketball blogs - soccer blogs - cooking blogs - recipe blogs - space blogs - 3d games blogs - barbecue blogs




the exchange server archives:

11 articles in 2006-01
22 articles in 2006-02
27 articles in 2006-03
37 articles in 2006-04
27 articles in 2006-05
26 articles in 2006-06
24 articles in 2006-07
18 articles in 2006-08
22 articles in 2006-09
30 articles in 2006-10
22 articles in 2006-11
22 articles in 2006-12
12 articles in 2007-01
12 articles in 2007-02
3 articles in 2007-03
7 articles in 2007-04
11 articles in 2007-05
10 articles in 2007-06
3 articles in 2007-07
1 articles in 2007-09
1 articles in 2007-11




next page


exchange server