Debugging output not appearing

[Guest]

I recently absorbed the task of supporting our CF MX 6.1 server. We have an app that we need to debug - the developer asked us to add her IP address to the "Debugging IP Addresses" list. I turned on debugging and added her IP address to the list, but debugging output is not displaying; this is true even when you run the CF app on the server running CF. The steps I took are as follows:

- In CF Administrator, checked Enable Robust Exception Information and Enable Debugging. Submitted changes and got msg Server has been updated successfully.
- Added developer's IP address to the list of debugging IP addresses. She couldn't see the debug output. Neither could I.
- Restarted CF server. No change.
- Rebooted server box. No change.
- Tried removing all IP addresses from list. Debugging input then shows for everyone.

One thing of note regarding the setup of the server is that IE has "Internet Explorer Enhanced Security Configuration" enabled - don't know if this would have any impact. I'd also tried adding the local IP address of my machine (I'm on the same LAN as the server), and I got no debug info on my machine. Our whole LAN, including the CF Server's box, is behind an ISA server, but of course that wouldn't have any impact on the local server, and I don't *think* it would affect machines on the LAN, but I'm not certain of this.

Showing the debug info to everyone is not an option, so we need to get the IP address filtering working. I've looked at the Windows event logs, the CF logs, and these forums, and can't find any helpful info.

Server config:

Windows Server 2003 (Standard Ed.) SP1
ColdFusion MX 6.1 (6,1,0,63958) Standard

Any suggestions would be very much appreciated.

[Guest]

I figured out the problem - it turns out that even our LAN traffic goes through our ISA server, and the ISA server passes its IP address to IIS, so CFMX is seeing all traffic as coming from the same IP address - the LAN address of the ISA server. Adding that turned it on for everyone, so it seems that the solution lies in changing the config of the ISA server to pass through IP addresses. See post by "Smiley Dave" titled "Debug IP Addresses" for a little more info, though there's no info in that thread that he ever actually got it working.

[Guest · Accepted solution]

(Question answered - can't add this attribute via an edit, only a new post. See post #2.)