 




<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Accessing Mail Server</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/itanswers/accessing-mail-server/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/itanswers/accessing-mail-server/</link>
	<description></description>
	<lastBuildDate>Tue, 21 May 2013 12:07:11 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: dwiebesick</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/accessing-mail-server/#comment-37619</link>
		<dc:creator>dwiebesick</dc:creator>
		<pubDate>Thu, 30 Nov 2006 09:38:51 +0000</pubDate>
		<guid isPermaLink="false">#comment-37619</guid>
		<description><![CDATA[You really need to provide more information.
When you ping the SBS from the wireless, does it by IP AND by name?  Since we don?t have a lot of information, to be simple, ping by IP shows connectivity; ping by NAME show name resolution.
How do they connect to obtain their email while on the outside?  If you have RPC over HTTP then it should work regardless of where they are working. If they are using Outlook Web Access, then it could be name resolution and you will have to adjust your internal DNS, might be as simple as placing a host record for example mail with the internal IP address. 

If you will provide greater detail, it would help us in trying to assist you with the correct path to try.

Best of luck

dmw
]]></description>
		<content:encoded><![CDATA[<p>You really need to provide more information.<br />
When you ping the SBS from the wireless, does it by IP AND by name?  Since we don?t have a lot of information, to be simple, ping by IP shows connectivity; ping by NAME show name resolution.<br />
How do they connect to obtain their email while on the outside?  If you have RPC over HTTP then it should work regardless of where they are working. If they are using Outlook Web Access, then it could be name resolution and you will have to adjust your internal DNS, might be as simple as placing a host record for example mail with the internal IP address. </p>
<p>If you will provide greater detail, it would help us in trying to assist you with the correct path to try.</p>
<p>Best of luck</p>
<p>dmw</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: stevesz</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/accessing-mail-server/#comment-37620</link>
		<dc:creator>stevesz</dc:creator>
		<pubDate>Wed, 29 Nov 2006 23:51:47 +0000</pubDate>
		<guid isPermaLink="false">#comment-37620</guid>
		<description><![CDATA[More information on how the users normally connect to the exchange server would be most helpful here. Each of the various methods has its pluses and minuses and little tricks depending upon the situation.]]></description>
		<content:encoded><![CDATA[<p>More information on how the users normally connect to the exchange server would be most helpful here. Each of the various methods has its pluses and minuses and little tricks depending upon the situation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mortree</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/accessing-mail-server/#comment-37621</link>
		<dc:creator>mortree</dc:creator>
		<pubDate>Wed, 29 Nov 2006 17:34:59 +0000</pubDate>
		<guid isPermaLink="false">#comment-37621</guid>
		<description><![CDATA[I assume these people are trying to connect via Outlook Web Access or POP3 and that they can normally do so from elsewhere.

Take a look at your Exchange machine. Are the wireless IP ranges allowed to connect to the OWA Web Server? I think that is the directory security page. Check all the places in Exchange where you can restrict/authorize service via IPs for OWA and POP3.

Finally check the firewall settings both on your dedicated (hardware) firewall and on Exchange. Are the HTTP/POP3 and SSL ports open for the wireless IP range?



]]></description>
		<content:encoded><![CDATA[<p>I assume these people are trying to connect via Outlook Web Access or POP3 and that they can normally do so from elsewhere.</p>
<p>Take a look at your Exchange machine. Are the wireless IP ranges allowed to connect to the OWA Web Server? I think that is the directory security page. Check all the places in Exchange where you can restrict/authorize service via IPs for OWA and POP3.</p>
<p>Finally check the firewall settings both on your dedicated (hardware) firewall and on Exchange. Are the HTTP/POP3 and SSL ports open for the wireless IP range?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using memcached
Database Caching 3/10 queries in 0.036 seconds using memcached
Object Caching 294/300 objects using memcached

Served from: itknowledgeexchange.techtarget.com @ 2013-05-21 12:11:25 -->