Re: Client cannot connect Outlook with Exchange while VPN'n

Tech-Archive recommends: Fix windows errors by optimizing your registry

On Nov 24, 6:07 pm, Sean <seanda...@xxxxxxxxx> wrote:
On Nov 24, 1:06 pm, "Cris Hanna [SBS MVP]"





<crisnospamha...@xxxxxxxxxxxxxxxxxxxxx> wrote:
1.  Are you talking about an inplace upgrade, or upgrade to SBS 2003 on a
new server?

2.  Regarding the email/vpn issue.   When the remote computer is connected
to the SBS server, can he ping the server by name?  if he does an nslookup
on the SBS server name, does it resolve?    is WINS information being
populated?

--
Cris Hanna [SBS - MVP]
Co-Author, Windows Small Business Server 2008 Unleashedhttp://www.amazon.com/Windows-Small-Business-Server-Unleashed/dp/0672...
------------------------------------
MVPs do not work for Microsoft
Please do not submit questions directly to me.

"Sean" <seanda...@xxxxxxxxx> wrote in message

news:5b425ea7-e3f7-41a2-a775-a6032a525e1a@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On Nov 24, 11:11 am, "Cris Hanna [SBS MVP]"

<crisnospamha...@xxxxxxxxxxxxxxxxxxxxx> wrote:
Is he able to get to Outlook Web Access?

Does the Exchange server receive mail directly on port 25 or is Exchange
collecting mail via POP3 from an ISP with the POP3 connector?

--
Cris Hanna [SBS - MVP]
Co-Author, Windows Small Business Server 2008
Unleashedhttp://www.amazon.com/Windows-Small-Business-Server-Unleashed/dp/0672...
------------------------------------
MVPs do not work for Microsoft
Please do not submit questions directly to me.

"Sean" <seanda...@xxxxxxxxx> wrote in message

news:af82f9b1-1d22-44a3-ac7d-7c3c1227358c@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On Nov 24, 7:00 am, "Cris Hanna [SBS MVP]"

<crisnospamha...@xxxxxxxxxxxxxxxxxxxxx> wrote:
This is usually an issue with name resolution over VPN
You don't mention which version of SBS?

--
Cris Hanna [SBS - MVP]
Co-Author, Windows Small Business Server 2008
Unleashedhttp://www.amazon.com/Windows-Small-Business-Server-Unleashed/dp/0672...
------------------------------------
MVPs do not work for Microsoft
Please do not submit questions directly to me.

"Sean" <seanda...@xxxxxxxxx> wrote in message

news:047ab123-f19f-46ca-ba1f-e37406a5c5bc@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Hi there.

I have a client who can connect to exchange just fine when he is on
the corperate network, but when he vpn's in he cannot connect to
exchange through Outlook.

He can access other network resources just fine. Just cannot connect
to Exchange.

Any ideas are welcome!

Thanks guys.

S- Hide quoted text -

- Show quoted text -

Sorry about that... I hate when people dont add the information
needed. :)

I have a client who is running Outlook 2003 on a Windows XP SP3 laptop
trying to connect to his Exchange (MS SBS 2000). He VPN's in and can
easly access his network drives as he normally does. These shares are
on the same server as the Excahnge server. I can ping the server by
its name on this laptop. I tried the TELNET suggestion to try to
connect to the server via port 25 with no luck.
When the user brings his laptop into the office, and logs in.. no
issues at all. I guess this has been an issue for some time and I am
uncertain about when it started happening.- Hide quoted text -

- Show quoted text -

Exchange is using port 25.  We do not have OWA enabled on the 2000
SBS. What blows me away is that he can still access shares that are on
the same server as Exchange.

. Reason why I was going from 2000 to 2003 was because I head that
they upgrade from 2000 directly to 2008 can be complicated. Since we
already own 2003 (and have a licence to upgrade to 2008 whenever we
want) I thought that going to 2003 would be a good idea. Once we are
stablized on 2003, then make the jump up to 2008.- Hide quoted text -

- Show quoted text -

So the client (while on the local network) can ping the exchange
server by the name. (ie ping our-pdc). Also, when I submit NSLOOKUP on
the client machine while on the network, it returns the SBS "ourserver-
pdc.mydomain.com with an internal ip address 192.168.168.2.

I am at the office now looking through some logs. I am curious why the
drive could be accessed but Exchange couldnt. I did notice that when
VPN'd in the "Connection-specific DNS Suffix" was not ourdomain.com
but invlaid IP or something to that effect.

I have to undock his laptop now and drive around the neighborhood to
find a wireless network to test the VPN. :(

THanks again for your time.

S- Hide quoted text -

- Show quoted text -

So, I am at a Tully's (need another network to test this on) and I am
VPN'd into our office and when I type NSLOOKUP MYSERVER at this point
I get the following:

nslookup
Server: ns.nnu.com
Address: 63.79.12.161

Non-authoritative answer:
Name: nslookup.ourdomain.com
Address: 68.178.xxx.xx


When I ping our SBS (which is Exchange and DC) I return the correct IP
address. I can also remote desktop from the laptop to the server no
problem.

Totally bamboozled.

S


.

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)