You're mixing protocols with name resolution. Apples and oranges kina. With the proper DNS configuration, your users should be able to connect just fine.
> -----Original Message----- > From: Irwan Hadi [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, September 11, 2002 10:10 AM > To: Exchange Discussions > Subject: Re: Clients can't connect to Microsoft Exchange 5.5 > > > On Tue, Sep 10, 2002 at 09:30:16AM -0600, Morrison, Mike L. wrote: > > > Reverse the search order of Tom's suggestion (DNS, LMHOSTS, > then WINS) > > and you have my vote for the solution. Outlook uses DNS name > > resolution first (which can be circumvented by using a HOSTS or > > LMHOSTS file), then goes to WINS after that times out. > > > > -----Original Message----- > > From: Tom Meunier [mailto:[EMAIL PROTECTED]] > > Sent: Tuesday, September 10, 2002 11:15 AM > > To: Exchange Discussions > > Subject: RE: Clients can't connect to Microsoft Exchange 5.5 > > > > > > Network connectivity and name resolution (WINS or LMHOSTS & DNS) is > > your starting point. > > After a little test I found out that computers which couldn't > access the Exchange server using Microsoft Outlook can't see > the server using Netbios resolution. (When I right click on > My computer, then tried to map network drive, I couldn't find > the server's Netbios name there). My question is, is there > any way so that the Microsoft Outlook won't utilize Netbios, > but just TCP/IP (of course not IMAP or POP) ? _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED]
