Can't access CRM website on CRM server
Question
Answers
All replies
-
Can you access CRM from server 3 if you use https://localhost:5555. I'm assuming you are not using the default web site. If you installed CRM to the default web site then try just https://localhost Also, ensure that none of your Services logins are using a CRM user login to start the services. You might also try right-clicking IE and select Run As Administrator to rule out any security issues. This could be related to a security issue on the server that is blocking the login. We can at least try ruling out any security issues first.
-
it means that you've most likely installed CRM on the default web site which is not generally recommended. Do you need to access CRM from server 3 using a FQDN.
If you want to find out more about what is going on you can check the event viewer to for more details about the error. You could also install Fiddler and take a look at the http traffic. It could be a dns, IFD or some other network related issue.
- Proposed as answer by Jamie MileyModerator Sunday, July 10, 2011 7:12 PM
-
I'll go back to my comment / suggestion:
Do you have a need to access CRM from server 3 using a FQDN? Why not just use localhost?
If you want to find out more about what is going on you can install Fiddler and take a look at the http traffic. It could be a dns, IFD or some other network related issue.
If we could answer the question, "why can all the other Win7 and Server 2008 R2 computers open that website with no problem and not even asking for credentials?" then we would know what you need to change on your network to get the FQDN working on the CRM server :)
Question:
"Why would using the default port be a problem other then for security?"
Response:
Some applications require use of the Default Web site so it could present a challenge if CRM is already using it.
- Proposed as answer by Jim Glass Jr Friday, July 15, 2011 4:55 PM
-
You're rightt, some things can be challenging to try and sort in an environment that is not available for view.
Based on what you've shared, it sounds like what we really need to solve is an e-mail router issue so why don't we try tackling that. Can you share your e-mail router configuration to include all the Profile Information to include each setting (Incoming, Outgoing, Deployment). You can take screenshots if that works better for you. Also, what error are you receiving with regard to the e-mail router.
-
Yes, we can focus on the URL issue understanding that resolving it will most likely not resolve the e-mail router issue. I think they are two seperate issues. I'll go back to my original suggestion, please download and install Fiddler, try accessing the FQDN from the CRM Server and have a look at the http traffic to see what is going on. That should point you to a resolution.cspanburg deleting the IPv6 didn't help, I made a spelling mistake in my prevoius post, sorry.
Donna can we please keep to the URL access problem, before we confuse ourself with what we really want, and that is to access the CRM organization on the CRm server using the FQDN.How do I go about adding screenshots here so that you can see the errors that I am receiving?
- Proposed as answer by Jim Glass Jr Friday, July 15, 2011 4:55 PM
-
Interesting, a Windows 2003, SP 1, SQL 2000, IIS 6 was the fix for a Windows 2008, SQL 2008, IIS 7.
I could have guessed for a year and never came up with that as a fix especially since it was happening for only one user and only when trying to access the FQDN from the CRM server.
