Skip to main content
Participant
May 3, 2006
Answered

MX7 problem: Admin access from remote machine

Within the last month or so, I'm suddenly finding it impossible to login to the web admin application from any machine other than the webserver itself. It just hangs for minutes, trying to connect, and eventually errors out with a standard IIS error (not CF debugging trace) saying there is a dns error or it can't find the site.

I'm on the same subnet -- it's a development lab -- and it worked fine for years, through CF5, and CFMX6. Then last month, while still on MX6, I was suddenly unable to connect anymore, without any config changes at all.

I upgraded to MX7 today (hoping that the admin access problem would go away, though that wasn't the reason for the upgrade) and I'm still unable to access the /CFIDE/administrator/ app from anywhere but the localhost. CFDocs works fine, and all my sites and apps work fine. I just can't access the administrator app remotely.

Any ideas out there?

In the interest of full disclosure, I work for the federal govt., and the IT staff here pushes out a seemingly endless stream of updates via SMS to our OS, browsers, apps, etc. I wouldn't be surprised if they disabled something that is required for the CFadmin app, but I can't figure out how to check. But the admin app won't work on Firefox, IE or netscape (and they only patch for IE).

    This topic is closed to new replies. Start a new post to keep the conversation going.
    cfestelCorrect answer
    Participant
    May 4, 2006
    Got the answer.

    Our local IT wizards push out SMS packages all the time, thinking that a one-size-fits-all solution will work for everyone. Trouble is, the few coders in our facility don't benefit from tons of hidden programs being installed on our desktops in the name of "security".

    They installed the BlackIce Intrusion Detection Firewall. I found this out by looking through my active processes, and found 'blackd.exe'. I disabled that and suddenly I was able to access the CF admin immediately from any browser.

    Now I just have to figure out how to modify BlackIce or disable it without the IT police reinstalling it every night...

    4 replies

    Participating Frequently
    May 5, 2006
    BlackIce runs as a service (BlackICE in Control Panel -> Services). You could simply disable it when you need to use the CFIDE and re-enable it when you are done.

    OR

    Better answer - get your IT snoops to fix their BlackICE configuration. We use it too, and I've never had a problem the packet intrusion filter causing the issue you described.
    Translate
    cfestelAuthorCorrect answer
    Participant
    May 4, 2006
    Got the answer.

    Our local IT wizards push out SMS packages all the time, thinking that a one-size-fits-all solution will work for everyone. Trouble is, the few coders in our facility don't benefit from tons of hidden programs being installed on our desktops in the name of "security".

    They installed the BlackIce Intrusion Detection Firewall. I found this out by looking through my active processes, and found 'blackd.exe'. I disabled that and suddenly I was able to access the CF admin immediately from any browser.

    Now I just have to figure out how to modify BlackIce or disable it without the IT police reinstalling it every night...
    Translate
    Participant
    May 3, 2006
    The DEV edition of CF limits the number of IP allowed to access the CF site. I think (and I could be wrong), MX 6 bound the server to one ip address at a time. I think MX 7 binds to 5 ips. Try it again when you know no one is using the dev site. It's not just access to the admin; it limits access to any CF application running on the server.
    Translate
    cfestelAuthor
    Participant
    May 4, 2006
    Good thought, but this is a full version of CFMX 7 Standard. It's a dev lab but it also serves some local Intranet content and is used as an exact mirror of our production environment for debugging and testing.

    All other applications and sites can be accessed from multiple desktops on the network, but the admin application cannot be accessed from anywhere but the localhost.

    The problem doesn't discriminate between OS either - Win2000 and WinXP both timeout trying to access the admin app.
    Translate