OK I tested the new startAuthoxy without success. I left logging on and logged in with startAuthoxy as a startup item. Here's what I got in the log:
Nov 4 12:01:07 : Authoxy has started successfully Nov 4 12:01:52 : Ready to NTLM! Nov 4 12:01:52 : Entering Step 1 Nov 4 12:01:52 : Entering Step 2 Nov 4 12:01:52 : Found Connection: close. Hiding for NTLM Authentication Nov 4 12:01:52 : Waiting for Step 2 Nov 4 12:01:52 : Content Length of response: 2640 Nov 4 12:01:52 : Step 2 is complete Nov 4 12:01:52 : Entering Step 3 Nov 4 12:01:52 : Created Type 1 string of 64 characters Nov 4 12:01:52 : Pausing in Step 3 Nov 4 12:01:52 : Entering Step 4 Nov 4 12:01:52 : Content-Length: 0 Nov 4 12:01:52 : NTLM: Target length is 4 Nov 4 12:01:52 : NTLM: Target length 2 is 4 Nov 4 12:01:52 : NTLM: Target offset is 56 Nov 4 12:01:52 : NTLM Flag: Negotiate OEM Nov 4 12:01:52 : NTLM Flag: Request Target Nov 4 12:01:52 : NTLM Flag: Negotiate NTLM Nov 4 12:01:52 : NTLM Flag: Target Type Domain Nov 4 12:01:52 : NTLM Flag: Negotiate Target Info Nov 4 12:01:52 : NTLM Flag: UNKNOWN5 Nov 4 12:01:52 : NTLM: Target is: MBBC Nov 4 12:01:52 : NTLM: Target length is 98 Nov 4 12:01:52 : NTLM: Target length 2 is 98 Nov 4 12:01:52 : NTLM: Target offset is 60 Nov 4 12:01:52 : NTLM: TargetInfo is: ^B^^H^M^B^B^C^^A^^H^I^N^E^T^^D^^P^m^b^b^c^.^e^d^u^^C^^Z^i^n^e^t^.^m^b^b^c^.^ e^d^u^^E^^P^m^b^b^c^.^e^d^u^^^^^ Nov 4 12:01:52 : The nonce is: sïJBÃlUÃ. Nov 4 12:01:52 : Finished Step 4 Nov 4 12:01:52 : Entering Step 5 Nov 4 12:01:52 : Got Type 3 msg of 176 characters. Nov 4 12:01:52 : Finished NTLM! Nov 4 12:01:52 : Client closed connection, killing session processes. Nov 4 12:01:58 : Authoxy has started successfully So Authoxy appears to have started successfully. But then when I attempt a network access (such as "Software Update") I get this in the log: Nov 4 12:03:35 : GET http://swscan.apple.com/scanningpoints/scanningpointX.xml HTTP/1.1 Nov 4 12:03:35 : Client closed connection, killing session processes. I'm using 10.3.5 and 3.1.2. I will do another networktraffic dump if it helps track it down. --Steve On 10/20/04 12:31 PM, "Steven Stratford" <[EMAIL PROTECTED]> wrote: > [Heath-- > > I stated below that the startup problem doesn't occur with my PowerBook, but > in fact it does. When I restart with startAuthoxy in my startup items, it > does not successfully start Authoxy even though Authoxy reports success. > > I just tested with startAuthoxy NOT in startup items so that startAuthoxy > has to be invoked manually. It is still not starting Authoxy successfully. > In either case (whether startAuthoxy is in the startup items or not), I have > to open the Authoxy control panel, stop, and start. I'm on OS X 10.3.5. > > --Steve] > > I am seeing the same thing now that I'm setting up a computer that has some > different login accounts specified. I want startAuthoxy to ask for the > login, which it does and reports success. However, it has not actually > started up (Authoxy reports 1 daemon). The startup problem doesn't show up > when I use startAuthoxy with my Powerbook because I leave my authentication > info in Authoxy. > > I will attach a dump taken right after restart (showing a failed attempt to > connect to software update) that might be helpful. > > --Steve > > > On 9/28/04 6:02 AM, "Heath Raftery" <[EMAIL PROTECTED]> wrote: > >> 2. A while back the issue of startAuthoxy reporting success after a >> reboot, but Authoxy not actually starting, was brought up. I had seen >> the issue before, but it seemed to fix itself, oddly enough. Recently I >> was working on a client's computer (actually a friend who lives near >> by!) and switched her Ethernet network connection from Manual to DHCP. >> Authoxy, which had never successfully started immediately after a >> reboot, started successfully the very next reboot. Strange stuff >> indeed. So the wrap-up is, I haven't discovered any changes I can >> actually make to Authoxy to make this more reliable. Instead it seems >> to be a networking startup glitch. >
