Can't login to CMC or Infoview from other stations

[ajharn]

Hi,

I have a new installation of CR Server XI and I suspect this is a permissions or IIS config issue.

When I try to login to CMC or Infoview on the local machine that is running CR Server, I can login via the launchpad links, w/ no problems.

If I access the launchpad from any other machine on the network, the page loads with no problem and links to the CMC and Infoview loging pages w/ no problem, but when I enter the user name and password, it simply returns me to the login page and blanks out the username and password fields. No error message is given.

Port 6400 (for the CMC server) is open and accepting connections from inside the network. So it does not seem to be a connectivity issue.

Any advice would be greatly appreciated!

Thanks,
AJ

Details:
CR Server XI running on Windows 2003 SP1

CR Knowledge Base has and item for this specific problem but that item says that it is due to an underscore in the server name and that replacing the server name with the IP address solves the problem. In my case, there is no underscore in the server name and substituting the IP address did not help.

<Moved this post from the CR 2 forum on recommendation of dgillz>

 

[ajharn]

Sorry for the duplicate post. Have asked TT to remove 1. Please reply to this thread. Thanks.

 

[Turkbear]

Hi,
Is there a firewall involved..If so, just opening 6400 is not sufficient to access the CMS server - read the docs about working with firewalls.





To Paraphrase:"The Help you get is proportional to the Help you give.."

 

[ajharn]

Thanks.

There should not be a firewall involved, but I will double-check. The station and the server are on the same LAN and no s/w firewalls are running on the server, including Windows. But I'll double check and I'll look that section of the docs over again.

 

[Turkbear]

Hi,
I asked because of:
Port 6400 (for the CMC server) is open and accepting connections from inside the network. So it does not seem to be a connectivity issue.


That implied that the CMS was somewhere outside..

What database is being used for the CMS?




To Paraphrase:"The Help you get is proportional to the Help you give.."

 

[ajharn]

Problem Resolved:

It WAS a firewall issue. But a slightly tricky one, and not on the server. Tech support asked me to check if the client browser was accepting cookies. I tested this and it was. Turned cookie security all the way off. No change in behavior. Tried all of the above w/ Firefox as well. No joy. Cookies were being accepted.

It was then, that my eyes FINALLY fell upon the Zone Alarm Pro firewall in the system tray of the CLIENT. Zone Alarm filters Private Headers out of cookies, unless you name a site and specificlly allow it.

I allowed Private Headers from that server and the problem was solved.

Hope that helps someone in the future.