Outlooks 2003 connection probs w/ Exchange server 2003

[BrooksAD]

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!

 

[dlw]

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]

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!

 

[Leonid S. Knyshov // SBS Expert]

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

 

[BrooksAD]

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]

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

 

[BrooksAD]

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.

 

[BrooksAD]

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]

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

 

[BrooksAD]

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

 

[Leonid S. Knyshov // SBS Expert]

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