500 Internal Server Error. The Network Logon Failed
| Address Book | Member List | Search | FAQ | Ticket List | Log Out The network logon failed Users viewing this topic: none Logged in as: Guest Tree Style Printable Version All Forums >> [ISA 2006 Publishing] >> Web Publishing >> The network logon failed Page: [1] Login Message << Older Topic Newer Topic >> The network logon failed - 9.Sep.2008 11:12:53 AM ldoodle Posts: 158 Joined: 21.Mar.2005 From: England Status: offline Hiya, Getting "Error Code: 500 Internal Server Error. The network logon failed. (1790)" when publishing our intranet site. The server itself has 2 websites on it (Intranet HTTP and Intranet HTTPS). The http one is configured with 2 host headers on port 80 (intranet and intranet.internaldomainname). The https one is configured with 1 host header on port 443 (intranet.externaldomainname). The https one also has our certificate bound to it. When testing the rule, I get the same error message. I have published this exactly the same as OWA and OWA works fine (even though testing the OWA rule fails!!). Any ideas? Thanks Post #: 1 Featured Links* RE: The network logon failed - 9.Sep.2008 4:52:32 PM Jason Jones Posts: 4663 Joined: 30.Jul.2002 From: United Kingdom Status: offline What delegation method are you using? What authentication method does you intranet web server use? Some details of your publishing rule may be handy... Cheers JJ _____________________________Jason Jones | Forefront MVP | Silversands Ltd My Blogs: http://blog.msedge.org.uk/ and http://blog.msfirewall.org.uk/ (in reply to ldoodle) Post #: 2 RE: The network logon failed - 16.Sep.2008 6:08:57 AM ldoodle Posts: 158 Joined: 21.Mar.2005 From: England Status: offline SSL Cert was obtained from DigiCert (Wildcard SSL). Publishing rule details: Name: Intranet Action: Allow From: Anywhere To: intranet.domainname (10.0.0.31). Forward original host header and requests appear to come from the original client both selected Traffic: HTTPS (Require 128-bit encryption for HTTPS traffic is selected) Listener: Intranet HTTPS Public Name: Requests for the following Web sites: intranet.domainname Paths: (Microsoft) Technical Consultant/SI GROUP SPONSORED BY MICROSOFT IN THIS DISCUSSION Join the Community! Creating your account only takes a few minutes. Join Now We have a landing page on our domain that we use to allow easy access to our internal services for employees. Not quite an Intranet page, but not a public page either. In any case, it was working fine until roughly August of this year when a cert expired. I have the certs updated on each of the systems, but I am still running into an issue. When I connect to the website from my house (over RDP) I get the 500 code: http://forums.isaserver.org/The_network_logon_failed/m_2002073528/tm.htm "Error Code: 500 Internal Server Error. The network logon failed (1790)" I did some research and a page I found mentioned something about the firewall rule in the ISA server is forwarding the requests to an internal server on a port that it is not listening on. He then suggests that a site using https:// is directed to an http:// site, and this IS our case as well, but I'm not sure where to https://community.spiceworks.com/topic/174067-problems-with-local-hosted-website-error-500-isa-issues go to look up the settings he mentioned on ISA (the server is ISA 2006, by the way) I'm an IIS n00b, I don't have any idea where to go for this stuff... The Blog referenced is: http://reidablog.blogspot.com/2007/10/error-code-500-internal-server-error.html
23, 20120 0 0 0 In this post, I’ll be talking about a web publishing problem and how I dealt with it. The problem was that external clients were failing to access an internal Web server published on ISA 2004 server with HTTP 500 https://blogs.technet.microsoft.com/nettracer/2012/05/23/getting-http-500-internal-server-error-when-accessing-a-published-web-site-through-isa-2004/ internal error. As usual, I asked the following logs from our customer when reproducing http://searchexchange.techtarget.com/answer/Network-logon-fails-during-OWA-setup the problem: - Collecting an ISA data packager while reproducing the problem (as part of ISA Best practices Analyzer log). The tool could be downloaded from the below link: http://www.microsoft.com/en-us/download/details.aspx?id=811 - Collecting a network trace from the internal web server - Collecting a network trace and Fiddler trace from an external test client. It could be downloaded at 500 internal the following link: http://www.fiddler2.com/fiddler2/ Note: Fiddler or similar tools (like HTTPWatch – we also use it) provide useful information even if the connection is clear text HTTP. For HTTPS connections it’s nearly a requirement to collect it to see what’s going on from client’s perspective. Another possibility is collecting WinInet/WinHTTP ETL traces which I plan to discuss in another post. Troubleshooting: After collecting the logs, I started troubleshooting the problem a) I 500 internal server first checked the Web proxy logs (collected as part of Data packager logs) and saw the same problem there: (I included only a part of the log and also changed the names deliberately) Result code is -2146893022 which is FFFFFFFF80090322 which is SEC_E_WRONG_PRINCIPAL Actually the web listener used by the given web publishing rule doesn’t have authentication configured. But that error might also be seen when certificate related issues are seen. b) Then I decided to check the ETL trace that was also collected as part of ISA data packager. Please note that the ETL trace collected as part of data packager could only be converted to human readable format by Microsoft support but we also provide a lightweight version of the same facility as part of the product. You can do that as follows:
(Before reproducing the problem you have to enable logging from “Enable Diagnostic Logging” and once the problem is reproduced you have to disable logging by selecting “Disable Diagnostic Logging”) When checking ETL traces, one of the key parameters is the filter info which is also a part of Web proxy log. Example: So I focused on the relevant filter info and have seen the following problem there: (please note that the ETL output is much more detailed thaOWA Exchange Security View All Compliance Management Compliance tools Email Compliance Email Encryption Email Policy Management ISA Server and Firewalls Password Management Microsoft Exchange Server Permissions Phishing and Email Fraud Protection Spam and virus protection Virtual Private Networks (VPNs) Email, Messaging and Collaboration Clients View All IM and Unified Messaging Microsoft Outlook Mobile Devices MS Office 365 Outlook Web Access Email, Messaging and Collaboration Servers View All Legacy Exchange Servers Microsoft Exchange Server 2003 Microsoft Exchange Server 2007 Microsoft Exchange Server 2010 Microsoft Exchange Server 2013 Exchange 2016 SharePoint Small Business Server Exchange Security View All Compliance Management Compliance tools Email Compliance Email Encryption Email Policy Management ISA Server and Firewalls Password Management Microsoft Exchange Server Permissions Phishing and Email Fraud Protection Spam and virus protection User Authentication for Outlook and OWA Virtual Private Networks (VPNs) Exchange Administration View All Mail Protocols Internet Information Services (IIS) Administration Tools Active Directory Licensing Mailbox Management Monitoring and Logging Performance Scripts and Programming User Settings Calendar and Contact Management Exchange Deployment and Migration View All Deployment and Migration Advice Deployment and Migration Tools Exchange Storage and Data Management View All .OST Files .PST Files Backup Microsoft Exchange Server Clustering Database Management Defragmentation Email Archiving Hardware Management Information Store Public Folders Storage Management Replication and Synchronization Transaction Logs Topics Archive View All Please select a category Email, Messaging and Collaboration Clients Email, Messaging and Collaboration Servers Exchange Security Exchange Administration Exchange Deployment and Migration Exchange Storage and Data Management Section Problem Solve News Get Started Evaluate Manage Problem Solve Sponsored Communities Q Network logon fails during OWA setup bySearchExchange Staff Sections Share this item with your network: Related Expert Q&A OWA logon screen keeps reappearing – SearchExchange Having problems with user name and password logon in ... – SearchExchange Customizing Exchange 2000 OWA logon page – SearchExchange Sponsored News Predictable VDI Performance From PoC to Production –SimpliVity Achieving Organizational Competency in I