Re: Problems with MS Diagnostic Log Viewer
- From: "Mike in Nebraska" <Mike_in_Nebraska@xxxxxxxxxxxxxxxx>
- Date: Thu, 7 May 2009 11:14:06 -0500
Lots of things to think about and try. While I was doing so, I found that my Firewall Client was not working right; had a yellow exclamation mark on it. Wound up uninstalling and reinstalling it and, using your idea for settings within GoLive, I was able to connect to the ISP via FTP.
Thanks!
Mike
"Phillip Windell" <philwindell@xxxxxxxxxxx> wrote in message news:OBdoHQyzJHA.5528@xxxxxxxxxxxxxxxxxxxxxxx
I think I'd rather just look at the FTP issue and not worry about the Tool (I don't know anything about that tool anyway). I usually figure most things out without any special "tools",...I can't even remember the last time I ever opened just Network Monitor.
Adobe Go Live -- Make sure that it is rigged to *not* think there is a proxy,...assuming of course that Adobe gives you the ability to do that (I know they don't with the software activation module that you use on a freshly installed product). You do not want it to "borrow" the browser's proxy settings.
Adobe products have a tendency to "borrow" the browser's proxy settings. This a really stupid thing for them to do particularly with FTP. This implies they try to do FTP through the browser components (WinInet.dll),...the problem with that is that "browser based ftp" uses the CERN Compliant Web Proxy standard (which doesn't come from MS) and the CERN standard says that "web proxy" FTP (aka http encapsulated ftp) can only be *read-only*. That means no uploads. It doesn't matter what you do with the checkbox on the FTP App Filter to my knowledge. That checkbox is for when you use "real" ftp with a real FTP Client. But I could be wrong.
Anyway, make sure the Adobe Product is completely "oblivious" to the fact the the proxy exists. Then if the FTP Access Rule requires user authentication then you will *have* to install the Firewall Client on the source machine. If the Acces Rule is anonymous (All Users) then you can probably get aways with just being a SecureNAT Client.
If for some silly reason Adobe does not give you the ability to make the Application "proxy agnostic" then you will have to temporarily remove the proxy settings from the browser when you have Go Live "send",...then put them back after.
--
Phillip Windell
www.wandtv.com
The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------
Technet Library
ISA2004
http://technet.microsoft.com/en-us/library/cc302436(TechNet.10).aspx
ISA2006
http://technet.microsoft.com/en-us/library/bb898433(TechNet.10).aspx
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/ISA2004_AccessRules.html
Troubleshooting Client Authentication on Access Rules in ISA Server 2004
http://download.microsoft.com/download/9/1/8/918ed2d3-71d0-40ed-8e6d-fd6eeb6cfa07/ts_rules.doc
Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.mspx
Microsoft ISA Server Partners: Partner Hardware Solutions
http://www.microsoft.com/forefront/edgesecurity/partners/hardwarepartners.mspx
-----------------------------------------------------
"Mike in Nebraska" <Mike_in_Nebraska@xxxxxxxxxxxxxxxx> wrote in message news:4A1B36F5-40E5-4FF6-AEE2-78FFDD3DD5B8@xxxxxxxxxxxxxxxxSetup: ISA 2004 on SBS 2003 Premium. All current with updates and patches and service packs.
==============
Background problem: I'm trying to update our website from Adobe GoLive by FTP'ing a new page to the ISP. Can't connect to the FTP server. Ran live log in ISA 2004 and find that the Internet Access Rule is to blame. Re-checked that I have FTP Outbound properly set in ISA. Neither System Log nor the ISA live log tells me the additional info I need to know WHY it is blocking the FTP attempt.
I installed Log Parser 2.2 and MS's Diagnostic Log Viewer on my server. I opened a command prompt and ran the following:
dlviewer -t 24:00:00 -odir html (I created a folder named html to hold those files)
When I hit Enter, I see this:
Generating query results. Please wait....
'logparser' is not recognized as an internal or external command, operable program or batch file.
Generating contexts information results. Please wait ...
'logparser' is not recognized as an internal or external command, operable program or batch file.
Done. Open html\index.html to view results.
When I open the html folder, all I see is a file named "dlviewer.css". I'm guessing that DLV is not "seeing" Log Parser.
What do I do?
--
Mike Webb
Platte River Whooping Crane Maintenance Trust, Inc.
a conservation non-profit (501 (c)(3)) organization
Wood River, NE
.
- Follow-Ups:
- Re: Problems with MS Diagnostic Log Viewer
- From: Phillip Windell
- Re: Problems with MS Diagnostic Log Viewer
- References:
- Problems with MS Diagnostic Log Viewer
- From: Mike in Nebraska
- Re: Problems with MS Diagnostic Log Viewer
- From: Phillip Windell
- Problems with MS Diagnostic Log Viewer
- Prev by Date: Re: Problems with MS Diagnostic Log Viewer
- Next by Date: Re: Problems with MS Diagnostic Log Viewer
- Previous by thread: Re: Problems with MS Diagnostic Log Viewer
- Next by thread: Re: Problems with MS Diagnostic Log Viewer
- Index(es):
Relevant Pages
|
Loading