RE: Publishing Exchange Server - Weird Problem

Hi David,

That is true. But you can send an email message or create a web page.
Anyone with an IQ above 80 should be able to do this. 

I've worked for companies with over 200,000 employees, and most of them
were able to fill out the paperwork that allowed them to receive their
paychecks and 401K and health benefits. Actually, those forms are a lot
harder than adding an entry to an LMHOSTS file.

However, if they have some psychological issues associated with editing
files, you can create the file, email it to them, and tell them where to
copy it to. If they can't copy a file, then they might want to consider
using a telephone and a typewriter instead of a computer.

:-)

HTH,
Tom
www.isaserver.org/shinder



-----Original Message-----
From: David Haam [mailto:DavidH@xxxxxxxxxxxx] 
Sent: Saturday, December 01, 2001 12:38 PM
To: [ISAserver.org Discussion List]
Subject: [isalist] RE: Publishing Exchange Server - Weird Problem

http://www.ISAserver.org


For smaller networks, that's not an issue. For larger ones, the
management of an LMHOSTS file is a very large pain. I've worked with
networks with over 5000 nodes and there are some techniques that can be
managed, but I'd avoid it.

David



-----Original Message-----
From: Thomas W. Shinder [mailto:tshinder@xxxxxxxxxxxxxxxxxx] 
Sent: Saturday, December 01, 2001 10:31 AM
To: [ISAserver.org Discussion List]
Subject: [isalist] RE: Publishing Exchange Server - Weird Problem


http://www.ISAserver.org


Hi David,

Just provide instructions to the users on how to configure their LMHOSTS
file.

If they are smart enough to fill out the job application, they are smart
enough to edit an LMHOSTS file.

HTH,
Tom

-----Original Message-----
From: David Haam [mailto:DavidH@xxxxxxxxxxxx] 
Sent: Saturday, December 01, 2001 11:33 AM
To: [ISAserver.org Discussion List]
Subject: [isalist] RE: Publishing Exchange Server - Weird Problem

http://www.ISAserver.org


From that you describe, it's pretty obvious that it's a problem with the
NETBIOS name.

Your options, if you don't want to us LMHOSTS:
* publish the NETBIOS name in your public DNS zone (I'm not positive if
this will help for your Win9x clients, but I think 98 is good). Remember
that MAPI really isn't a good WAN (read: slower-link) protocol.
* create a VPN scenario for those users, so they "dial-up" to the LAN
via VPN and then connect into their Exchange Server mailbox.
* have those Outlook users use IMAP rather that EXCHANGE SERVER in their
mail profiles.
* go to OWA for these users.

David



-----Original Message-----
From: Dave Morrow [mailto:David.Morrow@xxxxxxxxxxxx] 
Sent: Friday, November 30, 2001 5:47 AM
To: [ISAserver.org Discussion List]
Subject: [isalist] RE: Publishing Exchange Server - Weird Problem


http://www.ISAserver.org


I'll check out that Hotfix.  Thanks for the tip.  
You're right, it does seem to be the Win98 clients that mostly
experience the problem.  It's strange though, when the client connects
to resolve the hostname (entered as "exchange.mydomain.com") it
successfully connects, changes the servername to the NETBIOS name and
confirms the mailbox name. Then, when Outlook tries to actually connect
to the mailbox, it fails.  I tried using the LMHOSTS file and that does
cure the problem, but I really would rather not place LMHOSTS files on
all of my mobile users laptops....know what I mean?  I wonder if, for
some reason after connecting, and resolving the mailbox name, if the
client is placing the private IP address of the exchange server in the
profile somehow????

-----Original Message-----
From: Iain.Mclaren@xxxxxxxxxxxx [mailto:Iain.Mclaren@xxxxxxxxxxxx] 
Sent: Friday, November 30, 2001 4:41 AM
To: [ISAserver.org Discussion List]
Subject: [isalist] RE: Publishing Exchange Server - Weird Problem


http://www.ISAserver.org


This problem may be related to one of a few issues
What version of O/S are the Outlook clients running?
If its anything older than Windows2000 then you will 
need to apply MS Hotfix Q291000 to the ISA server, 
as the RPC connect packets from older MS O/S's (win95 through NT4) don't
comply with ISA server's RPC filter. 
However it could also be that the client isn't able to resolve the 
Netbios name of the exchange server (the server name displayed after a 
check mailbox name in the outlook client completes successfully) a quick
and easy way to test this is to enable the clients lmhosts file and add
an entry of the Netbios name of the exchange server being published and
the IP address of the ISA rule publishing it.

Iain



-----Original Message-----
From: Dave Morrow [mailto:David.Morrow@xxxxxxxxxxxx]
Sent: 29 November 2001 16:01
Subject: RE: Publishing Exchange Server - Weird Problem


Actually, I should have been more clear.  The problem exists with an
Exchange Server client using RPC communications

-----Original Message-----
From: Muqeem Syed [mailto:Syed.Muqeem@xxxxxxxxxxxx] 
Sent: Thursday, November 29, 2001 10:54 AM
To: [ISAserver.org Discussion List]
Subject: [isalist] RE: Publishing Exchange Server - Weird Problem


http://www.ISAserver.org


the outgoing connection form the server is made to a random port on the
client side.. check to see if you have any outgoing protocol rule that
denies outgoing traffice on certain ports.. .. the incoming traffic to
the server is on port 25 but outgoing port could be any random port..
you might want to check if there is any outgoing protol rule that
defines to deny traffic on those ports. 


-----Original Message-----
From: Dave Morrow [mailto:David.Morrow@xxxxxxxxxxxx]
Sent: Thursday, November 29, 2001 4:40 PM
To: [ISAserver.org Discussion List]
Subject: [isalist] Publishing Exchange Server - Weird Problem


http://www.ISAserver.org


I have this very strange problem with publishing an Exchange server
behind ISAServer.

I use the "Secure Mail Server" publishing wizard to publish my Exchange
server.  Everything works fine with respect to POP/SMTP but Outlook
clients connecting to my server can only resolve their mailbox name
(when they setup their profile).  When they launch Outlook it fails to
connect to the server. I know it can connect since it properly resolves
the name and sets up the profile.

David A. Morrow
Network Administrator
Autodata Solutions Company
David.Morrow@xxxxxxxxxxxx
http://www.autodata.net <http://www.autodata.net> 
Phone: (519) 951-6067   Fax: (519) 451-6615

This message has originated from Autodata Solutions Company. The
attached material is the Confidential and proprietary Information of
Autodata Solutions Company. This email and any files transmitted with it
are confidential and intended solely for the use of the individual or
entity to whom they are addressed. If you have received this email in
error please delete this message and notify the Autodata system
administrator at ADMINISTRATOR@xxxxxxxxxxxx





------------------------------------------------------
You are currently subscribed to this ISAserver.org Discussion List as:
syed.muqeem@xxxxxxxxxxxx To unsubscribe send a blank email to


------------------------------------------------------
You are currently subscribed to this ISAserver.org Discussion List as:
david.morrow@xxxxxxxxxxxx To unsubscribe send a blank email to


********************************************************************

This email may contain information which is privileged or confidential.
If you are not the intended recipient of this email, please notify the
sender immediately and delete it without reading, copying, storing,
forwarding or disclosing its contents to any other person Thank you

Check us out at http://www.syntegra.com

********************************************************************


------------------------------------------------------
You are currently subscribed to this ISAserver.org Discussion List as:
david.morrow@xxxxxxxxxxxx To unsubscribe send a blank email to
$subst('Email.Unsub')

------------------------------------------------------
You are currently subscribed to this ISAserver.org Discussion List as:
davidh@xxxxxxxxxxxx To unsubscribe send a blank email to
$subst('Email.Unsub')

------------------------------------------------------
You are currently subscribed to this ISAserver.org Discussion List as:
tshinder@xxxxxxxxxxxxxxxxxx To unsubscribe send a blank email to
$subst('Email.Unsub')

------------------------------------------------------
You are currently subscribed to this ISAserver.org Discussion List as:
davidh@xxxxxxxxxxxx To unsubscribe send a blank email to
$subst('Email.Unsub')

------------------------------------------------------
You are currently subscribed to this ISAserver.org Discussion List as:
tshinder@xxxxxxxxxxxxxxxxxx
To unsubscribe send a blank email to $subst('Email.Unsub')


Other related posts: