Re: Cross Post from ActiveSync Newsgroup - Problem Resolving Internal and FQDN Addresses when Using Pocket PC

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



Thanks, Gumby. That seemed to do the trick. I just used the defaults when
adding the zone, but didn't know which "same as parent" entry to add, so I
just added an (A) entry. Will that cause any problems elsewhere?

caz


"SuperGumby [SBS MVP]" <not@xxxxxxxxxxx> wrote in message
news:O1n2mXlEHHA.4024@xxxxxxxxxxxxxxxxxxxxxxx
create a DNS zone on SBS for mail.thread.com, do not create a zone for
thread.com with a host 'mail' as this would necessitate maintaining
records for the whole thread.com domain. The zone mail.thread.com needs
one 'same as parent' entry pointing to the internal IP of the server. This
will allow you to use the public name (mail.thread.com) internally.

start, all programs, administrative tools, dns, expand the server, rt-clk
'forward lookup zones', new zone.


"Craig Zawada" <craig.zawada@xxxxxxxxxxxxxx> wrote in message
news:eWzJ9ikEHHA.3600@xxxxxxxxxxxxxxxxxxxxxxx
The conversation below from another NG illustrates a problem I'm having
with a Windows Mobile device in our SBS 2003 network.

To back up a bit, if I use the FQDN of our server for the Proxy name in
the WM5 device, the device will not find the server to ActiveSync. If I
use the internal netbios name, it works OK, but of course will not work
when I'm away from the office.

My role as "SBS Administrator" is a completely unpaid adjunct to my real
job, so I don't pretend to understand the networking issues that may be
at play here. It may be something that is by design, for all I know. But
if not, does anyone have tips on where I can start to check my SBS
configuration to reference the FQDN? Is it an ISA 2004 issue that has to
be opened up? Any and all comments gratefully received.

Thanks

Craig A. Zawada


Thanks, Chris. Perhaps you know, or maybe I'll crosspost this thread in
the SBS newsgroup to find out how I can get the FQDN to respond from
within the network. I expect it's something simple and stupid on my part,
so I'll need someone with more networking experience to show me the error
of my ways.

The issue is that internally, our users see the server named "crock" (all
names have been changed to protect the innocent). The FQDN is
"mail.thread.com". In other words, there is no commonality between the
internal server name and the FQDN.

Thanks again for your help.

Craig A. Zawada

"Chris De Herrera" <spam@xxxxxxxxxxxxxxxx> wrote in message
news:O1f$hoQEHHA.4952@xxxxxxxxxxxxxxxxxxxxxxx
Hi Craig,
ActiveSync does not support multiple profiles for ActiveSync. The
concept
that Microsoft used was to use the FQDN all the time to sync. So this
assumes that you can access the FQDN from within the AP and desktop
rather
than hitting the server directly. This way you can sync anywhere.


--
Chris De Herrera
http://www.pocketpcfaq.com
http://www.tabletpctalk.com
http://www.pocketpctalk.com
http://www.mobilitytalk.com

ActiveSync 4.x Troubleshooting Guide -
http://www.pocketpcfaq.com/faqs/activesync/tshoot-as4x.htm

"Craig Zawada" <craig.zawada@xxxxxxxxxxxxxx> wrote in message
news:e%23saKz0DHHA.572@xxxxxxxxxxxxxxxxxxxxxxx
This may be something completely obvious and I'm overlooking it, but
here's what I want to do:

I have a WM5 device (HTC Tytn) that syncs at work. Our work network is
based on MS SBS 2003, and thus includes ISA 2004 Premium as a
proxy/firewall.

We also have a wireless AP at the office, which is inside the ISA
firewall, but is secured in a reasonable fashion (knock on wood).

Within the office, I can sync via USB no problem. After some
experimenting, I am also able to sync wirelessly within the office. To
do
so, I have to set up the AP to use Work network connection, and for the
proxy, I use the internal Netbios name of the server (rather than the
FQDN). For example, I use "server", instead of "mail.server.com".

Same thing within ActiveSync 4.1, in the Configure Server Source, I use
the Netbios name instead of FQDN, and I can sync wirelessly, as well as
over USB.

So far so good. My issue is this. When I am outside of the office, and
using a different access point (or GPRS), it will of course not see the
internal server name, and wants the FQDN so it can get there via the
internet. To do so, I can change the proxy to use the FQDN, and
ActiveSync
to use the FQDN, but it's a bit of a pain to have to re-enter passwords
and such.

Is there any way of simplifying this process, to in effect create a
different "profile" for instances of ActiveSync on the PPC, one when
I'm
in the office, and one when I'm not?

Hope I've explained this well enough. Anyone have ideas, or whether
it's
at all possible?

caz









.



Relevant Pages

  • Re: Unable to obtain a server assigned IP address
    ... In any case, though, when communicating via ActiveSync to the Internet, ... server it's trying to talk to. ... open the Control Panel | Connections | Network Cards applet and tap ...
    (microsoft.public.pocketpc.activesync)
  • RE: FQDN
    ... > You must run CEICW and specify the FQDN that you will use to access the ... On the SBS 2003 Server open the Server Management console. ... Click the "Connect to the Internet" link. ... On the "Web Server Certificate" page, choose to create a new Web server ...
    (microsoft.public.windows.server.sbs)
  • RE: FQDN
    ... > You must run CEICW and specify the FQDN that you will use to access the ... On the SBS 2003 Server open the Server Management console. ... Click the "Connect to the Internet" link. ... On the "Web Server Certificate" page, choose to create a new Web server ...
    (microsoft.public.windows.server.sbs)
  • RE: Push Email not working
    ... 501/505 "Not Implemented" during ActiveSync via internal network. ... This could cause problems as I using the current certificate for Outlook ... entire Web site from the Internet" is selected. ... On the "Web Server Certificate" page, choose to create a new Web server ...
    (microsoft.public.windows.server.sbs)
  • Re: How is .local Used?
    ... The CEICW (connect to the internet item, ... list) accepts your internet FQDN as input and modifies Exchange to handle ... > namespace definitions and the implications associated with their setup. ... >> The Domain Name System name recommendations for Small Business Server ...
    (microsoft.public.windows.server.sbs)