I meant IS. ------------------------------------------------------ Roger D. Seielstad - MCSE Sr. Systems Administrator Inovis - Formerly Harbinger and Extricity Atlanta, GA
> -----Original Message----- > From: Roger Seielstad > Sent: Friday, October 11, 2002 8:57 AM > To: Exchange Discussions > Subject: RE: Unusual OWA problem > > > Sounds like that server's IIS has the HTTP protocol disabled > for its users. > > In ExAdmin, Site | Configuration Container | Protocols and > make sure HTTP is > enabled, then make sure that the server is set to use the > site defaults for > protocols > > ------------------------------------------------------ > Roger D. Seielstad - MCSE > Sr. Systems Administrator > Inovis - Formerly Harbinger and Extricity > Atlanta, GA > > > > -----Original Message----- > > From: Nick Field [mailto:Nick.Field@;Comino.com] > > Sent: Friday, October 11, 2002 5:59 AM > > To: Exchange Discussions > > Subject: RE: Unusual OWA problem > > > > > > The plot thickens... > > > > I found the registry key which controls which server OWA > > contacts for DS > > info - > > HKEY_LM\SYSTEM\CurrentControlSet\Services\MSExchangeWEB\Parame > > ters\Server > > > > I tried changing it to the 4th server. > > > > Users still cannot access their mailboxes on the 4th server, > > all other users > > can still access their mailboxes. > > This suggests that OWA is not only accessing the 4th server > > ok, but is able > > to read the directory on that server. > > Therefore the problem probably lies elsewhere - Something > > unique to the > > mailbox setup on that server maybe? I have just gone through > > the mailbox > > properties and compared them to a mailbox that is working (I > > also compared > > the raw properties), and cannot find any differences (other > > than ones I > > would expect). > > > > So once again I am puzzled - Not an unusual state of affairs :) > > > > Nick > > > > > > -----Original Message----- > > From: Chris H [mailto:ntpro@;woh.rr.com] > > Sent: 11 October 2002 01:42 > > To: Exchange Discussions > > Subject: Re: Unusual OWA problem > > > > The value for the exchange server OWA hits is in the registry > > (I forget the > > key but it is in the MS KB). Perhaps change this server to > the failing > > server and see if that helps? > > > > Chris > > > > ----- Original Message ----- > > From: "Nick Field" <[EMAIL PROTECTED]> > > To: "Exchange Discussions" <[EMAIL PROTECTED]> > > Sent: Thursday, October 10, 2002 9:07 AM > > Subject: RE: Unusual OWA problem > > > > > > > Hi Tony, thanks for the response - > > > > > > I'm guessing that when users hit the OWA box, (if > authentication is > > > stipulated) they are authenticated against the domain, then once > > > authenticated the OWA code attempts to contact the mailbox > > specified in > > the > > > 'Log On' textbox, I am unsure how it determines which > > server to contact (I > > > assume it connects to the DS on one server, but which > > server or how it > > > determines which server is unknown to me) and I suspect > > this is where the > > > problem lies. > > > > > > Name resolution 'seems' ok... ie the OWA box can resolve > > the 4th server > > name > > > to IP address without problems. > > > OWA originally worked talking to the 4th server. > > > The IP address of the 4th server did change some time ago. > > Several weeks > > > before a report of problems with OWA. (I am not discounting > > this, since > > > users are notorious for not reporting problems immediately). > > > Test users fail in the same manner as normal users. > > > I get the same results connecting either from inside or outside. > > > > > > If this could be a problem caused by the change in IP > > address, I would > > > appreciate any ideas on where to start looking - WINS is > > fully updated, we > > > do not use DNS, all name resolution seems to be working. Is > > there anything > > > within the Exchange install that 'hard codes' the IP address? > > > > > > Nick > > > > > > -----Original Message----- > > > From: Tony Hlabse [mailto:thlabse@;hotmail.com] > > > Sent: 10 October 2002 15:32 > > > To: Exchange Discussions > > > Subject: Re: Unusual OWA problem > > > > > > You have to ask what happens when a users hits the OWA box. > > Sounds like a > > > name resolution problem. Did some change an IP or something > > on that 4th > > box. > > > Did this just start? Check event logs on 4th box. What > > happens if you > > create > > > a test users and try to get in. Does this happen only from > > the outside > > > world. Does in work OK internally? > > > > > > > > > ----- Original Message ----- > > > From: "Nick Field" <[EMAIL PROTECTED]> > > > To: "Exchange Discussions" <[EMAIL PROTECTED]> > > > Sent: Thursday, October 10, 2002 8:13 AM > > > Subject: Unusual OWA problem > > > > > > > > > > I am using Exchange 5.5, SP4 on 4 servers in a single > > exchange site, > > > single > > > > NT4 Domain, multiple geographical offices. > > > > I have a 5th server running OWA also SP4. > > > > > > > > All mailboxes on servers 1 through 3 can be accessed by > > their relative > > > users > > > > via OWA, all mailboxes on server 4 are inaccessible by > > their relative > > > users. > > > > All users on all 4 servers can access their mailbox via > an Outlook > > client. > > > > > > > > I get the standard - 'OWA was unable to get your Inbox' > > error. I have > > > > followed as many of the MS help/KB articles I can find, > > to no avail. > > > > > > > > There is no firewall between the OWA box and the 4 servers. > > > > > > > > All users have the same permissions on all 4 servers, and > > all have 'log > > on > > > > locally' on the OWA box. > > > > > > > > I have cranked all the diagnostic logging within Exchange > > up to maximum > > > and > > > > not seen any information regarding a logon attempt from the user > > > attempting > > > > to connect via OWA, suggesting problems with > > communication from the OWA > > > > system however all other communication between the two > > servers I have > > > tried > > > > seems to be fine. > > > > > > > > Has anyone got any suggestions? > > > > > > > > Cheers > > > > Nick > > > > > > > > > _________________________________________________________________ > > > > List posting FAQ: > http://www.swinc.com/resource/exch_faq.htm > > > > Archives: > http://www.swynk.com/sitesearch/search.asp > > > > To unsubscribe: mailto:leave-exchange@;ls.swynk.com > > > > Exchange List admin: [EMAIL PROTECTED] > > > > > > > > > > _________________________________________________________________ > > > List posting FAQ: http://www.swinc.com/resource/exch_faq.htm > > > Archives: http://www.swynk.com/sitesearch/search.asp > > > To unsubscribe: mailto:leave-exchange@;ls.swynk.com > > > Exchange List admin: [EMAIL PROTECTED] > > > > > > _________________________________________________________________ > > > List posting FAQ: http://www.swinc.com/resource/exch_faq.htm > > > Archives: http://www.swynk.com/sitesearch/search.asp > > > To unsubscribe: mailto:leave-exchange@;ls.swynk.com > > > Exchange List admin: [EMAIL PROTECTED] > > > > > > > > > _________________________________________________________________ > > List posting FAQ: http://www.swinc.com/resource/exch_faq.htm > > Archives: http://www.swynk.com/sitesearch/search.asp > > To unsubscribe: mailto:leave-exchange@;ls.swynk.com > > Exchange List admin: [EMAIL PROTECTED] > > > > _________________________________________________________________ > > List posting FAQ: http://www.swinc.com/resource/exch_faq.htm > > Archives: http://www.swynk.com/sitesearch/search.asp > > To unsubscribe: mailto:leave-exchange@;ls.swynk.com > > Exchange List admin: [EMAIL PROTECTED] > > > > _________________________________________________________________ > List posting FAQ: http://www.swinc.com/resource/exch_faq.htm > Archives: http://www.swynk.com/sitesearch/search.asp > To unsubscribe: mailto:leave-exchange@;ls.swynk.com > Exchange List admin: [EMAIL PROTECTED] > _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:leave-exchange@;ls.swynk.com Exchange List admin: [EMAIL PROTECTED]
