Re: Connecting to Exchange...

On 2008-06-24 13:41:11 -0500, "Cliff Galiher" <cgaliher@xxxxxxxxx> said:

Just to make sure I have my facts straight (if they aren't then correct them please):

1) If I read your statement correctly, you *can* ping on the LAN.

Yes.

2) Pinging from outside fails.

Yes.

3) The outside connection is, in fact, an internet connection and not a private leased line.

Yes, we have a T1 with 16 static IP's.

4) SBS cannot run DHCP because another device is. That means that SBS has a static *private* IP on your LAN.

Correct. In reality, it's not another device. We run a mixed network and have another operating system handling DHCP. In reality, there seems to be no reason for this LAN connection as it is never connected to by this method. Always by the static IP. If there were some way to not configure it, I would.

5) Your public IP is held by another device (router, gateway, firewall appliance.)

Yes. A gateway.

6) Traffic is routed to SBS via this appliance.

Yes.

If all of those things are correct then I'll make a few observations:

1) Not being able to ping "the server" is probably not a sign of a problem...and is also technically inaccurate. The device that holds the public IP is responsible for answering pings, not SBS. In many cases, particularly with consumer-grade routers, they are specifically configured to ignore pings. You can dig into this and fix it, but it probaby is not the cause of, or related to, your outlook issue.

Our gateway is configured by our T1 provider to pass through everything. We have 6 other servers on this same connection, all of them respond to pings. The ability to respond to pings is configurable on each server. Only the SBS server does not respond which leads me to believe that something not set right in SBS. There is no firewall in between at the moment other than what may have been installed by SBS during installation.

2) You mentioned in your original post that you reconfigured the SBS page to redirect to OWA. This is very likely your problem. Outlook RPC over HTTP(s) requires the "RPC" virtual directory in IIS. This is configured by default for you with SBS, but if you are redirecting all incoming traffic to another virtual directory then outlook cannot reach that RPC virtual directory. And if it can't reach it, it cannot use that functionality to tunnel to exchange via HTTP. You can verify this by temporarily disabling your redirection.

This makes sense. I will try this and let you know the results. This at least logically separates the two problems into a ping problem and an Exchange access problem.


On 2008-06-24 10:42:39 -0500, "Cliff Galiher" <cgaliher@xxxxxxxxx> said:

First, you *really* should let SBS be the DHCP server. DHCP is a complicated beast that does more than just assign IP addresses. It also has various option flags that, in SBS-land, make other components work. Your router doesn't know and doesn't care about these flags...and you will end up having problems.

For example, The SBS DHCP server will make it the NTP time server for clients. Your router won't. If the clock on the client skews too much, you get kerberos problems....can't log in. And that is just an example off the top of my head. I understand the desire to keep your server minimalist and only run exchange, but DNS and DHCP should be considered "essential" SBS components.

Unfortunately, this is not an option.


Now, on to your other questions:

1) Are you pinging and trying to connect on the LAN or across a WAN link?

Pings on LAN, does not on WAN.

2) What is the client OS?

WinXP Pro

3) Was the computer joined to the domain using the connect computer wizard?

Do you mean the server computer itself? No. If you are talking about the client computer, no, because it is never at the server location an only needs Outlook Exchange.

4) Have you applied all service packs and updates to the server AND the client?

Yes.

5) Does the server or client have any third-party security products installed? If so, what are they?

No.

Not being able to ping sounds like a firewall issue, but pinpointing where that problem lies requires answers to one or more of the questions above...

-Cliff


"Ethon Bridges" <ethonbridges@xxxxxxxxx> wrote in message news:2008062408351416807-ethonbridges@xxxxxxxxxxx
I have recently installed SBS2003 on a Dell PowerEdge server.

I cannot ping my server or connect to Exchange with Outlook, however, I can log in to Exchange/OWA via a web browser using the server's static IP or DNS name.

I am not using anything else about SBS except Exchange at this point. I have another router providing DHCP and don't want anything else running except Exchange.

I currently have the main SBS page redirected to only the OWA page.

Can anyone help me through the process of figuring out why I can't ping or access the server with Outlook?


.

Relevant Pages

  • Re: So why SBS?
    ... Public folders will be in the next version.. ... The sad part of most of us is that we haven't even tried or practiced a backup/restore and we freak out over a 'single" SBS box when we haven't even tried to restore it from a harddrive. ... Exchange seems to mix its words and titles, the global/generic use of POP and SMTP for just about every Exchange function is dumb, MailEnable understands post office protocol and simple mail transfer protocol in a "meaningfull" way. ... The standard profiles in Server are quite effective assuming you add new users to the correct account in the first place and your note running more than 1 file server. ...
    (microsoft.public.windows.server.sbs)
  • Re: Easy to use second 2000 Server for Exchange?
    ... Existing Exchange 2000 server - therefore have the CALs - so no new ones are ... Frank McCallister SBS MVP ...
    (microsoft.public.windows.server.sbs)
  • Re: So why SBS?
    ... Public folders will be in the next version.. ... If SBS isn't for you...that's fine. ... Mailenable is an example of a freeware or pay for extra's, mail server. ... It is infinitly simpler to configure than Exchange once installed. ...
    (microsoft.public.windows.server.sbs)
  • Re: Email for second domain
    ... The Microsoft Exchange MTA Stacks service is normally disabled on Exchange 2003 Servers on SBS 2003. ... You can safely ignore the MTA warning messages on the SBS 2003 server. ...
    (microsoft.public.windows.server.sbs)
  • RE: Configuring exchange 2003 in SBS
    ... As I know, this is not related to per user mailbox, it refer to the mailbox ... store on the whole Exchange server. ... This newsgroup only focuses on SBS technical issues. ... What minimum requirement if I want this server for a fileserver? ...
    (microsoft.public.windows.server.sbs)
Loading