Outlooks 2003 connection probs w/ Exchange server 2003

Hello,

I need some assistance.  I have researched and researched but can't get some 
resolve on this problem.

I helped a business move office locations.  The business had a Win 2003 
server that is the company web server and Exchange 2003 server.  

The network structure was a DSL internet connection, a Linux (generic) 
firewall, the 2003 server and a few client PCs on the network.

In brief the move required a provider change so now the company is using a 
cable provider for phone and INET. When we finally got online we had some 
problems connecting.

Not knowing the Linux firewall setup and how it was interacting with the 
company (I'm familiar but not a pro in the Linux world) I pulled it and am 
using a Linksys router as the new firewall.  

The new structure is the cable company data modem, the Linksys router, the 
Widows server and the clients - simple setup.

I opened ports 25, 80, 100, and a couple of others on the firewall (for LDAP 
and something else - I can't remember right now).

I cannot connect to the mail server via Outlook 2003.  OWA works fine.  We 
can see the website fine but the clients cannot connect via Outlook.

One other thing:  I messed up.  When setting up the Linksys firewall I 
enabled DHCP on the firewall and disabled it on the Win server.  I found out 
that that was a mistake and reversed that move.  The Win server is now the 
DHCP server.

Not sure what is wrong at this point.  The error message on the client side 
says that the server is unavailable.  I can't make them find the server (by 
removing and re-setting up the user's email box in Outlook).

From what I can find, the 2003 server needs to be DHCP in order to provide 
all DNS information on the network.  I originally put in the DNS servers on 
the clients themselves before the server was back online so I could 
troubleshoot INET problems.  Would this be my sole snag?  I'm not convinced 
that it is because one of the 3 client PCs never had this DNS information 
added to it.

Any help would be appreciated.

Thanks!
0
Utf
3/10/2010 3:29:02 PM
outlook.general 7254 articles. 4 followers. Follow

10 Replies
780 Views

Similar Articles

[PageSpeed] 15

the win2003 server has to be the DNS server, anything can be the DHCP server, 
as long as it it giving out the win2003 server IP as the DNS server

"BrooksAD" wrote:

> Hello,
> 
> I need some assistance.  I have researched and researched but can't get some 
> resolve on this problem.
> 
> I helped a business move office locations.  The business had a Win 2003 
> server that is the company web server and Exchange 2003 server.  
> 
> The network structure was a DSL internet connection, a Linux (generic) 
> firewall, the 2003 server and a few client PCs on the network.
> 
> In brief the move required a provider change so now the company is using a 
> cable provider for phone and INET. When we finally got online we had some 
> problems connecting.
> 
> Not knowing the Linux firewall setup and how it was interacting with the 
> company (I'm familiar but not a pro in the Linux world) I pulled it and am 
> using a Linksys router as the new firewall.  
> 
> The new structure is the cable company data modem, the Linksys router, the 
> Widows server and the clients - simple setup.
> 
> I opened ports 25, 80, 100, and a couple of others on the firewall (for LDAP 
> and something else - I can't remember right now).
> 
> I cannot connect to the mail server via Outlook 2003.  OWA works fine.  We 
> can see the website fine but the clients cannot connect via Outlook.
> 
> One other thing:  I messed up.  When setting up the Linksys firewall I 
> enabled DHCP on the firewall and disabled it on the Win server.  I found out 
> that that was a mistake and reversed that move.  The Win server is now the 
> DHCP server.
> 
> Not sure what is wrong at this point.  The error message on the client side 
> says that the server is unavailable.  I can't make them find the server (by 
> removing and re-setting up the user's email box in Outlook).
> 
> From what I can find, the 2003 server needs to be DHCP in order to provide 
> all DNS information on the network.  I originally put in the DNS servers on 
> the clients themselves before the server was back online so I could 
> troubleshoot INET problems.  Would this be my sole snag?  I'm not convinced 
> that it is because one of the 3 client PCs never had this DNS information 
> added to it.
> 
> Any help would be appreciated.
> 
> Thanks!
0
Utf
3/10/2010 3:54:01 PM
OK, that makes sense.  So, the DNS servers that our provider gave us should 
be identified on the DHCP server (whatever box does that) but the actual IP 
settings on the client PCs and the Win server itself should reflect the DNS 
of the internal static IP that I set up on that Win server?

Thanks again!

"dlw" wrote:

> the win2003 server has to be the DNS server, anything can be the DHCP server, 
> as long as it it giving out the win2003 server IP as the DNS server
> 
> "BrooksAD" wrote:
> 
> > Hello,
> > 
> > I need some assistance.  I have researched and researched but can't get some 
> > resolve on this problem.
> > 
> > I helped a business move office locations.  The business had a Win 2003 
> > server that is the company web server and Exchange 2003 server.  
> > 
> > The network structure was a DSL internet connection, a Linux (generic) 
> > firewall, the 2003 server and a few client PCs on the network.
> > 
> > In brief the move required a provider change so now the company is using a 
> > cable provider for phone and INET. When we finally got online we had some 
> > problems connecting.
> > 
> > Not knowing the Linux firewall setup and how it was interacting with the 
> > company (I'm familiar but not a pro in the Linux world) I pulled it and am 
> > using a Linksys router as the new firewall.  
> > 
> > The new structure is the cable company data modem, the Linksys router, the 
> > Widows server and the clients - simple setup.
> > 
> > I opened ports 25, 80, 100, and a couple of others on the firewall (for LDAP 
> > and something else - I can't remember right now).
> > 
> > I cannot connect to the mail server via Outlook 2003.  OWA works fine.  We 
> > can see the website fine but the clients cannot connect via Outlook.
> > 
> > One other thing:  I messed up.  When setting up the Linksys firewall I 
> > enabled DHCP on the firewall and disabled it on the Win server.  I found out 
> > that that was a mistake and reversed that move.  The Win server is now the 
> > DHCP server.
> > 
> > Not sure what is wrong at this point.  The error message on the client side 
> > says that the server is unavailable.  I can't make them find the server (by 
> > removing and re-setting up the user's email box in Outlook).
> > 
> > From what I can find, the 2003 server needs to be DHCP in order to provide 
> > all DNS information on the network.  I originally put in the DNS servers on 
> > the clients themselves before the server was back online so I could 
> > troubleshoot INET problems.  Would this be my sole snag?  I'm not convinced 
> > that it is because one of the 3 client PCs never had this DNS information 
> > added to it.
> > 
> > Any help would be appreciated.
> > 
> > Thanks!
0
Utf
3/10/2010 9:32:02 PM
On 3/10/2010 7:29 AM, BrooksAD wrote:
> Hello,
>
> I need some assistance.  I have researched and researched but can't get some
> resolve on this problem.
>
> I helped a business move office locations.  The business had a Win 2003
> server that is the company web server and Exchange 2003 server.
>
> The network structure was a DSL internet connection, a Linux (generic)
> firewall, the 2003 server and a few client PCs on the network.
>
> In brief the move required a provider change so now the company is using a
> cable provider for phone and INET. When we finally got online we had some
> problems connecting.
>
> Not knowing the Linux firewall setup and how it was interacting with the
> company (I'm familiar but not a pro in the Linux world) I pulled it and am
> using a Linksys router as the new firewall.
>
> The new structure is the cable company data modem, the Linksys router, the
> Widows server and the clients - simple setup.
>
> I opened ports 25, 80, 100, and a couple of others on the firewall (for LDAP
> and something else - I can't remember right now).
>
> I cannot connect to the mail server via Outlook 2003.  OWA works fine.  We
> can see the website fine but the clients cannot connect via Outlook.
>
> One other thing:  I messed up.  When setting up the Linksys firewall I
> enabled DHCP on the firewall and disabled it on the Win server.  I found out
> that that was a mistake and reversed that move.  The Win server is now the
> DHCP server.
>
> Not sure what is wrong at this point.  The error message on the client side
> says that the server is unavailable.  I can't make them find the server (by
> removing and re-setting up the user's email box in Outlook).
>
>  From what I can find, the 2003 server needs to be DHCP in order to provide
> all DNS information on the network.  I originally put in the DNS servers on
> the clients themselves before the server was back online so I could
> troubleshoot INET problems.  Would this be my sole snag?  I'm not convinced
> that it is because one of the 3 client PCs never had this DNS information
> added to it.
>
> Any help would be appreciated.
>
> Thanks!

Is the machine remote, configuring Outlook Anywhere, or local?

Sounds like the DNS entry to for the domain is potentially pointing to 
the old IP.

You are confusing me.

1. Server and PC are on the same network
2. PC is being configured for Outlook Anywhere through firewalls

Please choose the correct scenario.
-- 
Leonid S. Knyshov
Crashproof Solutions
510-282-1008
Twitter: @wiseleo
http://crashproofsolutions.com
Microsoft Small Business Specialist
Try Exchange Online http://bit.ly/free-exchange-trial
Please vote "helpful" if I helped you :)
0
Leonid
3/11/2010 9:29:47 AM
Sorry, when I used the OWA I meant Outlook Web Access.  Sorry for the 
confusion.  The clients can see their email via a web browser, not by using 
Outlook at this time.

The machines are on the same network; one server, two client PCs.

Just to be clear.  I'm just a bit confused on getting the DNS thing correct. 
 It sounds to me like the the Win server needs to provide the DNS services 
for the network.  I guess that this is where my problem is.  The PCs and the 
server all have the DNS of the provider configured on the network card 
directly.  I did that originally to get on the net because we had other 
issues that I needed to resolve. 

So, for me, I suppose I need to understand if that is where my conflict is.  
Should the PCs and the server reflect the DNS server as being the Win server 
(using the internal static IP to that Win server)?

I'm not sure but you may be right about an old IP.  I'll have to check the 
DNS server settings on the Win server to see what it has listed.  It may not 
have the new DNS (from our provider) servers.  It sounds like that may be the 
deal, right?

It's a tad confusing to me because I don't know how that would keep Outlook 
from seeing the server on the same network, you know?

Thanks again.

"Leonid S. Knyshov // SBS Expert" wrote:

> On 3/10/2010 7:29 AM, BrooksAD wrote:
> > Hello,
> >
> > I need some assistance.  I have researched and researched but can't get some
> > resolve on this problem.
> >
> > I helped a business move office locations.  The business had a Win 2003
> > server that is the company web server and Exchange 2003 server.
> >
> > The network structure was a DSL internet connection, a Linux (generic)
> > firewall, the 2003 server and a few client PCs on the network.
> >
> > In brief the move required a provider change so now the company is using a
> > cable provider for phone and INET. When we finally got online we had some
> > problems connecting.
> >
> > Not knowing the Linux firewall setup and how it was interacting with the
> > company (I'm familiar but not a pro in the Linux world) I pulled it and am
> > using a Linksys router as the new firewall.
> >
> > The new structure is the cable company data modem, the Linksys router, the
> > Widows server and the clients - simple setup.
> >
> > I opened ports 25, 80, 100, and a couple of others on the firewall (for LDAP
> > and something else - I can't remember right now).
> >
> > I cannot connect to the mail server via Outlook 2003.  OWA works fine.  We
> > can see the website fine but the clients cannot connect via Outlook.
> >
> > One other thing:  I messed up.  When setting up the Linksys firewall I
> > enabled DHCP on the firewall and disabled it on the Win server.  I found out
> > that that was a mistake and reversed that move.  The Win server is now the
> > DHCP server.
> >
> > Not sure what is wrong at this point.  The error message on the client side
> > says that the server is unavailable.  I can't make them find the server (by
> > removing and re-setting up the user's email box in Outlook).
> >
> >  From what I can find, the 2003 server needs to be DHCP in order to provide
> > all DNS information on the network.  I originally put in the DNS servers on
> > the clients themselves before the server was back online so I could
> > troubleshoot INET problems.  Would this be my sole snag?  I'm not convinced
> > that it is because one of the 3 client PCs never had this DNS information
> > added to it.
> >
> > Any help would be appreciated.
> >
> > Thanks!
> 
> Is the machine remote, configuring Outlook Anywhere, or local?
> 
> Sounds like the DNS entry to for the domain is potentially pointing to 
> the old IP.
> 
> You are confusing me.
> 
> 1. Server and PC are on the same network
> 2. PC is being configured for Outlook Anywhere through firewalls
> 
> Please choose the correct scenario.
> -- 
> Leonid S. Knyshov
> Crashproof Solutions
> 510-282-1008
> Twitter: @wiseleo
> http://crashproofsolutions.com
> Microsoft Small Business Specialist
> Try Exchange Online http://bit.ly/free-exchange-trial
> Please vote "helpful" if I helped you :)
> .
> 
0
Utf
3/11/2010 3:43:01 PM
On 3/11/2010 7:43 AM, BrooksAD wrote:
> Sorry, when I used the OWA I meant Outlook Web Access.  Sorry for the
> confusion.  The clients can see their email via a web browser, not by using
> Outlook at this time.
>
> The machines are on the same network; one server, two client PCs.
>
> Just to be clear.  I'm just a bit confused on getting the DNS thing correct.
>   It sounds to me like the the Win server needs to provide the DNS services
> for the network.  I guess that this is where my problem is.  The PCs and the
> server all have the DNS of the provider configured on the network card
> directly.  I did that originally to get on the net because we had other
> issues that I needed to resolve.
>
> So, for me, I suppose I need to understand if that is where my conflict is.
> Should the PCs and the server reflect the DNS server as being the Win server
> (using the internal static IP to that Win server)?
>
> I'm not sure but you may be right about an old IP.  I'll have to check the
> DNS server settings on the Win server to see what it has listed.  It may not
> have the new DNS (from our provider) servers.  It sounds like that may be the
> deal, right?
>
> It's a tad confusing to me because I don't know how that would keep Outlook
> from seeing the server on the same network, you know?
>
> Thanks again.

You are still confused as OWA has nothing to do with a local 
configuration problem.

In other words, this is a scenario with local PCs accessing a local 
Exchange server.

Unless your workstations talk to the right DNS server, you will continue 
to experience problems.

If all this is too confusing, a consultant familiar with Active 
Directory troubleshooting can correct such issues pretty quickly. A 
support ticket with Microsoft might be cheaper, however.

In a nutshell, this is how this works:

1. Domain controller hosts a DNS server.
2. DNS server may or may not be configured to forward unresolved 
requests to your ISP server. If it's not configured that way, it will 
use Root Hints.
3. The domain controller's NIC points to itself as the DNS server
4. The domain controller acts as a DHCP server. It is configured with 
the IP address of your router, the local domain name etc. You may also 
configure the network device to be a DHCP server, but a Microsoft 
solution is far more flexible.
5. The network device DHCP server is disabled.
6. Workstations receive IP addresses dynamically from the DHCP server 
and so do the printers. For pseudo-static IP addressing, use MAC address 
reservations feature of the DHCP server.

My networks have zero static addresses assigned, except for the router 
and the DHCP servers.

Bonus points - check the Exchange server's health with Exchange BPA. 
Check the File Replication Services log on your domain controller to 
make sure Active Directory is functioning properly.
-- 
Leonid S. Knyshov
Crashproof Solutions
510-282-1008
Twitter: @wiseleo
http://crashproofsolutions.com
Microsoft Small Business Specialist
Try Exchange Online http://bit.ly/free-exchange-trial
Please vote "helpful" if I helped you :)
0
Leonid
3/11/2010 8:41:03 PM

"Leonid S. Knyshov // SBS Expert" wrote:

> On 3/11/2010 7:43 AM, BrooksAD wrote:
> > Sorry, when I used the OWA I meant Outlook Web Access.  Sorry for the
> > confusion.  The clients can see their email via a web browser, not by using
> > Outlook at this time.
> >
> > The machines are on the same network; one server, two client PCs.
> >
> > Just to be clear.  I'm just a bit confused on getting the DNS thing correct.
> >   It sounds to me like the the Win server needs to provide the DNS services
> > for the network.  I guess that this is where my problem is.  The PCs and the
> > server all have the DNS of the provider configured on the network card
> > directly.  I did that originally to get on the net because we had other
> > issues that I needed to resolve.
> >
> > So, for me, I suppose I need to understand if that is where my conflict is.
> > Should the PCs and the server reflect the DNS server as being the Win server
> > (using the internal static IP to that Win server)?
> >
> > I'm not sure but you may be right about an old IP.  I'll have to check the
> > DNS server settings on the Win server to see what it has listed.  It may not
> > have the new DNS (from our provider) servers.  It sounds like that may be the
> > deal, right?
> >
> > It's a tad confusing to me because I don't know how that would keep Outlook
> > from seeing the server on the same network, you know?
> >
> > Thanks again.
> 
> You are still confused as OWA has nothing to do with a local 
> configuration problem.
> 
> In other words, this is a scenario with local PCs accessing a local 
> Exchange server.
> 
> Unless your workstations talk to the right DNS server, you will continue 
> to experience problems.
> 
> If all this is too confusing, a consultant familiar with Active 
> Directory troubleshooting can correct such issues pretty quickly. A 
> support ticket with Microsoft might be cheaper, however.
> 
> In a nutshell, this is how this works:
> 
> 1. Domain controller hosts a DNS server.
> 2. DNS server may or may not be configured to forward unresolved 
> requests to your ISP server. If it's not configured that way, it will 
> use Root Hints.
> 3. The domain controller's NIC points to itself as the DNS server
> 4. The domain controller acts as a DHCP server. It is configured with 
> the IP address of your router, the local domain name etc. You may also 
> configure the network device to be a DHCP server, but a Microsoft 
> solution is far more flexible.
> 5. The network device DHCP server is disabled.
> 6. Workstations receive IP addresses dynamically from the DHCP server 
> and so do the printers. For pseudo-static IP addressing, use MAC address 
> reservations feature of the DHCP server.
> 
> My networks have zero static addresses assigned, except for the router 
> and the DHCP servers.
> 
> Bonus points - check the Exchange server's health with Exchange BPA. 
> Check the File Replication Services log on your domain controller to 
> make sure Active Directory is functioning properly.
> -- 
> Leonid S. Knyshov
> Crashproof Solutions
> 510-282-1008
> Twitter: @wiseleo
> http://crashproofsolutions.com
> Microsoft Small Business Specialist
> Try Exchange Online http://bit.ly/free-exchange-trial
> Please vote "helpful" if I helped you :)


I see what you're saying, Leonid.  I think you hit it on the head for me in 
your line item #3.  I have the external DNS address assigned to the NICs for 
all three machines instead of letting the DHCP do that; this includes the Win 
server.  I thought about this way back but it seemed circular to me and 
didn't make sense.

Every thing else is running as is before the move.  The only real difference 
is the box that is the firewall (which is working) and the DNS settings on 
the NICs.  SO, I'm going to make that changes and go from there.  I'll post a 
response.

And, yes you've been very helpful.  I'll hit yes when I get out of this.

BTW, my only reference to the web access was to note that the Exchange 
server is working so I knew that the problem wasn't directly that server app 
since we can send and receive email.  So, I'm good.  I'm gettin' it.  I 
appreciate it.
0
Utf
3/12/2010 10:36:01 PM
Got onto this network and made the changes.  Outlook did work!  The clients 
on the LAN do send and recieve via Outlook.

One snag:  After the changes, the client PCs cannot see the website on this 
web server/Exchange server.  I've I'm in IE on the clients (Win XP) or in IE 
on the server I cannot see the web site that is hosted there.  If I put in 
the IP address I can get to it but by name I cannot.  Users in the outside 
world can see this web site. Not sure what happened but this has an affect on 
a remote PC (one that is not on this LAN).  That machine needs to connect via 
Outlook as well.  It can see the web site, it uses the Outlook Web Access but 
does not connect via Outlook directly.

Any ideas?  Does the DNS change on the server take some time to update 
internally?  I rebooted since I had some updates to install to the O/S but 
that didn't resolve anything.

Thanks again!

Brooks

"Leonid S. Knyshov // SBS Expert" wrote:

> On 3/11/2010 7:43 AM, BrooksAD wrote:
> > Sorry, when I used the OWA I meant Outlook Web Access.  Sorry for the
> > confusion.  The clients can see their email via a web browser, not by using
> > Outlook at this time.
> >
> > The machines are on the same network; one server, two client PCs.
> >
> > Just to be clear.  I'm just a bit confused on getting the DNS thing correct.
> >   It sounds to me like the the Win server needs to provide the DNS services
> > for the network.  I guess that this is where my problem is.  The PCs and the
> > server all have the DNS of the provider configured on the network card
> > directly.  I did that originally to get on the net because we had other
> > issues that I needed to resolve.
> >
> > So, for me, I suppose I need to understand if that is where my conflict is.
> > Should the PCs and the server reflect the DNS server as being the Win server
> > (using the internal static IP to that Win server)?
> >
> > I'm not sure but you may be right about an old IP.  I'll have to check the
> > DNS server settings on the Win server to see what it has listed.  It may not
> > have the new DNS (from our provider) servers.  It sounds like that may be the
> > deal, right?
> >
> > It's a tad confusing to me because I don't know how that would keep Outlook
> > from seeing the server on the same network, you know?
> >
> > Thanks again.
> 
> You are still confused as OWA has nothing to do with a local 
> configuration problem.
> 
> In other words, this is a scenario with local PCs accessing a local 
> Exchange server.
> 
> Unless your workstations talk to the right DNS server, you will continue 
> to experience problems.
> 
> If all this is too confusing, a consultant familiar with Active 
> Directory troubleshooting can correct such issues pretty quickly. A 
> support ticket with Microsoft might be cheaper, however.
> 
> In a nutshell, this is how this works:
> 
> 1. Domain controller hosts a DNS server.
> 2. DNS server may or may not be configured to forward unresolved 
> requests to your ISP server. If it's not configured that way, it will 
> use Root Hints.
> 3. The domain controller's NIC points to itself as the DNS server
> 4. The domain controller acts as a DHCP server. It is configured with 
> the IP address of your router, the local domain name etc. You may also 
> configure the network device to be a DHCP server, but a Microsoft 
> solution is far more flexible.
> 5. The network device DHCP server is disabled.
> 6. Workstations receive IP addresses dynamically from the DHCP server 
> and so do the printers. For pseudo-static IP addressing, use MAC address 
> reservations feature of the DHCP server.
> 
> My networks have zero static addresses assigned, except for the router 
> and the DHCP servers.
> 
> Bonus points - check the Exchange server's health with Exchange BPA. 
> Check the File Replication Services log on your domain controller to 
> make sure Active Directory is functioning properly.
> -- 
> Leonid S. Knyshov
> Crashproof Solutions
> 510-282-1008
> Twitter: @wiseleo
> http://crashproofsolutions.com
> Microsoft Small Business Specialist
> Try Exchange Online http://bit.ly/free-exchange-trial
> Please vote "helpful" if I helped you :)
> .
> 
0
Utf
3/18/2010 12:43:02 AM
On 3/17/2010 5:43 PM, BrooksAD wrote:
> Got onto this network and made the changes.  Outlook did work!  The clients
> on the LAN do send and recieve via Outlook.
>
> One snag:  After the changes, the client PCs cannot see the website on this
> web server/Exchange server.  I've I'm in IE on the clients (Win XP) or in IE
> on the server I cannot see the web site that is hosted there.  If I put in
> the IP address I can get to it but by name I cannot.  Users in the outside
> world can see this web site. Not sure what happened but this has an affect on
> a remote PC (one that is not on this LAN).  That machine needs to connect via
> Outlook as well.  It can see the web site, it uses the Outlook Web Access but
> does not connect via Outlook directly.
>
> Any ideas?  Does the DNS change on the server take some time to update
> internally?  I rebooted since I had some updates to install to the O/S but
> that didn't resolve anything.

That is likely to be a "feature" of your router. Packets are not allowed 
to leave and come back on the same interface.

You did not explain whether you used internal IP or external IP in your 
tests. That's vital.

Do me a favor and open a command prompt.
Now "ping www.YourSiteName.com"

If the name gets resolved to external IP but goes nowhere, blame your 
firewall or router.

If the name does not get resolved at all, look at external DNS issues.

It is a common concern. The clumsy workaround is typically to re-create 
the external domain's DNS zone in dnsmgmt.msc with internal IP addresses.

In any event, this question has nothing to do with Outlook. :)
-- 
Leonid S. Knyshov
Crashproof Solutions
510-282-1008
Twitter: @wiseleo
http://crashproofsolutions.com
Microsoft Small Business Specialist
Try Exchange Online http://bit.ly/free-exchange-trial
Please vote "helpful" if I helped you :)
0
Leonid
3/18/2010 9:41:56 AM
"Leonid S. Knyshov // SBS Expert" wrote:

> On 3/17/2010 5:43 PM, BrooksAD wrote:
> > Got onto this network and made the changes.  Outlook did work!  The clients
> > on the LAN do send and recieve via Outlook.
> >
> > One snag:  After the changes, the client PCs cannot see the website on this
> > web server/Exchange server.  I've I'm in IE on the clients (Win XP) or in IE
> > on the server I cannot see the web site that is hosted there.  If I put in
> > the IP address I can get to it but by name I cannot.  Users in the outside
> > world can see this web site. Not sure what happened but this has an affect on
> > a remote PC (one that is not on this LAN).  That machine needs to connect via
> > Outlook as well.  It can see the web site, it uses the Outlook Web Access but
> > does not connect via Outlook directly.
> >
> > Any ideas?  Does the DNS change on the server take some time to update
> > internally?  I rebooted since I had some updates to install to the O/S but
> > that didn't resolve anything.
> 
> That is likely to be a "feature" of your router. Packets are not allowed 
> to leave and come back on the same interface.
> 
> You did not explain whether you used internal IP or external IP in your 
> tests. That's vital.
> 
> Do me a favor and open a command prompt.
> Now "ping www.YourSiteName.com"
> 
> If the name gets resolved to external IP but goes nowhere, blame your 
> firewall or router.
> 
> If the name does not get resolved at all, look at external DNS issues.
> 
> It is a common concern. The clumsy workaround is typically to re-create 
> the external domain's DNS zone in dnsmgmt.msc with internal IP addresses.
> 
> In any event, this question has nothing to do with Outlook. :)

Hello again.

Got it working!  Thank you for all the help!  It was a combination, 
apparently.  Our provider tells us that the data modem (router) won't let 
traffic in and out as you stated above.  I did add a new A record in the 
forward lookup zone to tie the server to our external IP address.  It took!  

I really appreciate it, Leonid.

Take care,

Brooks
0
Utf
3/19/2010 9:23:02 PM
On 3/19/2010 2:23 PM, BrooksAD wrote:
> Hello again.
>
> Got it working!  Thank you for all the help!  It was a combination,
> apparently.  Our provider tells us that the data modem (router) won't let
> traffic in and out as you stated above.  I did add a new A record in the
> forward lookup zone to tie the server to our external IP address.  It took!
>
> I really appreciate it, Leonid.
>
> Take care,
>
> Brooks
You are welcome. :)

-- 
Leonid S. Knyshov
Crashproof Solutions
510-282-1008
Twitter: @wiseleo
http://crashproofsolutions.com
Microsoft Small Business Specialist
Try Exchange Online http://bit.ly/free-exchange-trial
Please vote "helpful" if I helped you :)
0
Leonid
3/19/2010 10:31:51 PM
Reply:

Similar Artilces:

Outlook 2003 keeps crashing #2
I get this message when I look in System information. Outlook keeps crashing quite often. I cannot for example delete two messages without outlook crashing. My colleagues do not have this problem. We are using the Microsoft mail exhange server. Faulting application outlook.exe, version 11.0.5510.0, stamp 3f1380f0, faulting module mso.dll, version 11.0.5606.0, stamp 3f334cce, debug? 0, fault address 0x003b6e16. Does anyone has a solution?=20 Best regards/ Bj=F6rn 1) I would definitely apply Service Pack 2for Office 2003 + applicable critical security updates. 2) Have you tried starting O...

Password Issue with MS Money 2003
Hello, I am not familiar with newsgroups but I hope it is a forum to seek assistance. I am unable to reach MS support via email from my home computer on this issue. My Money 2003 requires a net passport password to open my account in Money that I have successfully accessed for approximately 12 months. It does not recognize my password now. I have attempted several times with my existing password, changed my net passport password, even uninstalled and re- installed MS Money 2003 to gain access to my account. Nothing has worked. Each time it states I have failed to enter the corr...

Exchange 2003 new install can not receive external email.
I have just setup a new Windows Server 2003 standard edition with Exchange 2003 standard edition on it. I have been working for a while trying to get it to receive external email. I can send out and send/ receive internal messages, but when someone trys to send me a message from outside our network they get the following returned mail message This Message was undeliverable due to the following reason: Each of the following recipients was rejected by a remote mail server. The reasons given by the server are included to help you determine why each recipient was rejected. Recipient: <**...

Runtime Error when closing OUTLOOK 2k
What's this mean and how to fix? in error dialogue box: "c:\program~1\micro~2 \office\outlook.exe" Abnormal program termination ...

Sony HDR-XR200V 120GB HDD High Definition Camcorder w/15x Optical Zoom
Price:$999.99 Image: http://specialdealfinder.info/image.php?id=B001QBM9EM Best deal: http://specialdealfinder.info/index.php?id=B001QBM9EM In my opinion, the camcorder deserves 4/5 stars. The HD picture quality outdoors (rain or shine) is PHENOMAL. I got a similar picture in SD. It wasn't quite as sharp as HD but still an EXCELLENT picture. The sound quality is amazing. I had no problem with wind noise when outside on windy days. The camcorder itself is lightweight and I found the menus and buttons to be user-friendly. I read several negative reviews on the included Sony softwa...

Outlook needs Outlook Express to work
I've installed my Outlook 2002 on my new Vista PC (I had Xp before). Now when I start Outlook it says "requires Outlook Express 4.01 or greater". I've been looking for Outlook Express to download and install but no joy. No CD came with my new Vista PC. Any ideas, short of buying a more modern Outlook? Vista doesn't actually support Outlook 2002 or older. Outlook Express is part of Internet Explorer but with the advent of Vista, it was switched to Windows Mail. There is no more Outlook Express. You could attempt however to create a profile using workgroup or c...

"The connection to the Exchange server is unavailable. Outlook must be online or connected to complete this action"
I have setup a number of user accounts and the relative mailboxes without any problem. However, since this afternoon, if I try and connect to a newly mailbox through the email accounts wizard I get the following error message: "The connection to the Exchange server is unavailable. Outlook must be online or connected to complete this action". This also occurs when I go to File>Open>Other User's Folder... and I try and lookup an existing account/mailbox that I know I have permission to. I know Outlook is connected to the Exchange server (I can ping, send and receive emails) ...

Crash on 'Send"
My wife's Intel Celeron running ME started having this problem sporadically - now constantly. Outlook 2000 receives OK - everything seems fine until you hit the 'Send' button then Outlook crashes giving an error message that says 'Outlook has caused an error in <unknown> and has to shut down. If the problem persists you may have to restart your computer.' Re-starting however has no effect. I have re-installed Office. Used 'Detect & Repair' under the 'Help' tab, and installed all patches/updates from the Office site. But this error continues, now...

Exchange update problem
I have tried to upgrade exch2k3 sp1 to sp2, but the update fails with "the file pcproxy.dll is in use, and setup cannot identify the app or srvc. setup cannot continue" Any clues/ideas/suggestions? Please. -- ----------------------------------------------------------------------------------------------------------------------- This message has been checked for all known viruses. The information contained in this e-mail and any attachments is confidential and may be the subject of legal, professional or other privilege. It is intended for the named addressee only and may not ...

Transferring over outlook data to new XP machine
How do I transfer over my old emails, address book to my new XP machine? I have looked over the internet and found nothing the tells me EXACTLY how to do this, any help would be greatly appreciated. senior_tech@yahoo.com If your using MS Outlook copy your .PST file across and import it into the new install. >If your using MS Outlook copy your .PST file across and import it into the new install. No, don't import it. Simply use "File">"Open" -- Brian Tillman Smiths Aerospace 3290 Patterson Ave. SE, MS 1B3 Grand Rapids, MI 49512-1991 Brian.Tillman is the nam...

Outlook 2003 and "Check Names"
Hi, We are testing Outlook 2003 at our office now and there is one very frustrating "feature" that is bugging all of us. When we create a new e-mail message and type in the first name of a person from the global address book and hit ctrl- k to check the name...we get a response that Outlook doesn't recognize the name and there are "no suggestions". The only way Check Name will successfully resolve the name is if we type it last name first (ie, Gates, Bill). This was not the case in Office XP or Outlook 2000. You could search by first name (or partial first name)...

Exchange 2k3 imap VS startup
I have an E2k3 SP1 enterprise edition server. Whenever I reboot, the IMAP4 Virtual server does not start back up. I have to go into Exchange System Manager and manually start it. How do I make it start automatically? Tim How is the service set up - to start manually or automatically? Also, I'd check the dependencies the service has. It may be that it's trying to start before the other services have completed starting. Missy "Tim" <tjc7546@yahoo.com> wrote in message news:u14PBseFFHA.3120@TK2MSFTNGP12.phx.gbl... I have an E2k3 SP1 enterprise edition serve...

Reminders in Outlook
Since upgrading to Great Plains 9.0, several users are not getting their appointment reminders in Outlook 2003. They all show up at once after rebooting computer. Outlook settings are set appropriately. Any ideas? -- Steve ...

Outlook default to paragraph
To whom ever can help, > > When using Microsoft Outlook, and starting a new E- Mail, The default > format is to "paragraph" which double spaces. Is there anyway to > select under a New Message, Format, Style, "Normal" as the default? > > Thank you in advance > > Dave daveandivy@netidea.com >-----Original Message----- >To whom ever can help, >> >> When using Microsoft Outlook, and starting a new E- >Mail, The default >> format is to "paragraph" which double spaces. Is there >anyway to >> select unde...

Install Exchange 2003 Server on new Hardware with same name
I got a new server to move my Exchange Server Installation. I want to keep the name I'm using now for my Server. Already read TechNet Article "How to Move Exchange Server 2003 to New Hardware and Keep the Same Server Name". Is there anything else that I should be aware of that is not on this TechNet article? I'm using a different Disk Configuration, does this matters? Should this be a smooth process? Thanks for any help you can give. The drive letters MUST match, because the paths of the databases are at the Active Directory. The disks can have different sizes than the or...

how do I connect an object from one page to a different page?
I am trying to connect an object from one page to a seperate object on a different page. The instructions say to hold down your mouse button then click on the point you want it connected too. My problem is that is doesn't allow you to select the starting point of the connector, then select a different page, then click on your end point of the connector. Please help! try using a hyperlink. al "Pepper" <Pepper@discussions.microsoft.com> wrote in message news:3F5657F4-48EA-4681-A21E-D33FC7030401@microsoft.com... >I am trying to connect an object from one page to...

Addressing within Exchange 2003
We are running Exchange 2003 SP2. We setup an MX record for a external email(alumni.cup.edu) these mailboxes do not exist within our exchange org. But when we send email to these externals email mailboxes we are getting the following NDRs: #5.5.0 smtp;550 Mailbox unavailable. #5.4.0 Is there a way in exchange to ignore these email address so that we don't get the NDR from within our Exchange Org? On Fri, 4 Aug 2006 08:08:02 -0700, Sabo, Eric <sabo_e@cup.edu> wrote: >We are running Exchange 2003 SP2. We setup an MX record for a external >email(alumni.cup.edu...

how do i add "Software Digrams" Folder in my Visio 2003
how do i add software diags folder in visio 2003 version. Like if i go to File->New it shows folders like brainstorming, project schedule, block diagrams but in my case its missing the Software Diags folder which contains activity diags, web mock ups, use case diags etc. please let me know how to get that template. thanks. Ankur What edition of Visio are you using? Check by going to the About Microsoft Office Visio dialog from the Help menu. "Ankur" <Ankur@discussions.microsoft.com> wrote in message news:F0D10BF0-A059-4A9C-B615-B99F3916F4E5@microsoft.com... > how...

How to restore entire server?
This is a long post. Its that time of year again where I practise some disaster recovery skills. I set up a completely seperate physical network from the production network. Its got one Win2000 server (DC + all the Operations Master roles, DNS, WINS, etc) with SP4 (different AD/DNS root forest) and running Exchange 2000 with SP3 (same org name as production server, admin group, storage group, logical and physical database names, legacyexchangeDN, etc). As a result, I can successfully restore our production Exchange 2000 w/SP3 Storage Group/Information Store database without problems. Outlook...

Outlook "Ruler" won't go away
I don't know how I turned this on so I don't know how to turn it off. It splits my emails so that I can only type so far over before it kicks me back to the left margin and makes me start a new line. Can anyone help me? ...

Outlook 2003
Hello, we have one client pc with Outlook 2003 where the following problem occurs: if a mail is replied from a user created sub folder of the inbox, the reply will not appear in sent mails, but will end up in the same sub folder, sender and recipient appear as identical. The mail goes out properly though, it's just that Outlook sets internally sender = recipient and bounces the reply back to the subfolder in which the original mail is stored. This happens on a Win 2000 machine with SP4 and all updates, the other clients use Outlook 2000 or XP and there is no such problem. There are no ru...

[Exchange 2003] Mail enabled public folder and sender address
I have a Windows 2003 domain with a native mode Exchange 2003 organization; there are some mail enabled public folders. When a user replies to a message in a public folder, the outgoing mail's sender address is the user's one; I want it to be the public folder's one, or at least I'd like the "reply-to" address to be set to the public folder's. How can I accomplish this? Thanks Massimo You would need to grant the user permissions to be able to Send As the public folder. By default, when you reply to a message that is in a PF, the PF is not composing the ...

cant start outlook pst file to large
Hi I hope somebody may be able to help im new to outlook and now I cant start outlook message says cannot open your default email folders pst file its too large as I cannot open outlook I cannot delete old folders See if this helps: http://support.microsoft.com/kb/296088 -- -Ben- Ben M. Schorr, MVP Roland Schorr & Tower http://www.rolandschorr.com http://www.officeforlawyers.com/outlook.html Author: The Lawyer's Guide to Microsoft Outlook 2007: http://tinyurl.com/ol4law-amazon "Ray" <Ray@discussions.microsoft.com> wrote in message news:B3B824DC-3C9B-4B1B-8EF3-61...

Import from Eudora 6 to Outlook 2003
I am trying to import messages from Eudora 6 to Outlook 2003. I am receiving the error message "The mail folder could not be opened. If another application is using this file, please close and try again. No other applications are running Thanks for any help see article 257354 of the microsoft knowledge base on http://support.microsoft.com: "Outlook Cannot Import Eudora Messages When Eudora Mail Is Stored in a Non-Default Location" ciaos >-----Original Message----- >I am trying to import messages from Eudora 6 to Outlook 2003. I am receiving the error message ...

Outlook OOF
The Out of Office Reply will not be sent outside the network. I have exchange 5.5 and have read the faqs but the only fix I found did not work. Here is the number for the fix that I found: Q176161. Thank you for your time and help, Larry 1. Make sure your Exchange server's Internet Mail Service is configured to allow Automatic Replies to the Internet; that's the most common reason it wouldn't work. 2. Reconsider if you really want to use it. You're going to automatically reply to every message you receive; including spam. That's a good way to confirm to the spammer...