On 9/7/04 6:05 PM, "bruce" <[EMAIL PROTECTED]> wrote: > It was caused when the network connection switched from a lost wireless > connection to another wireless connection. This may be interesting. > > It seems as though you are not maintaining the NETWORK connection reliably.
When connecting normally to the proxy directly from the Network control panel, I'm not perceiving any broken network connection, no delays or timeouts. > > We know that the NTLM works... eventually but it seems to work. > Therefore that is probably NOT the problem. > > I wonder if the transactions are getting to the proxy server/authenticating > in the way that you expect? I'd be interested in knowing exactly what Step 2 is. > > Is it a highly loaded network? I would not say highly loaded though there are times when the Internet access seems slower, I'm pretty sure because we're all sharing a single T1. Internal network traffic I don't think is excessive. There are a good number of users, usage levels vary. > Are packets getting dropped anywhere because of load? Not that I know of. Let's see, I could ping the proxy server....... PING 10.2.0.2 (10.2.0.2): 56 data bytes 64 bytes from 10.2.0.2: icmp_seq=0 ttl=128 time=24.137 ms 64 bytes from 10.2.0.2: icmp_seq=1 ttl=128 time=0.416 ms 64 bytes from 10.2.0.2: icmp_seq=2 ttl=128 time=7.927 ms 64 bytes from 10.2.0.2: icmp_seq=3 ttl=128 time=0.441 ms 64 bytes from 10.2.0.2: icmp_seq=4 ttl=128 time=0.597 ms 64 bytes from 10.2.0.2: icmp_seq=5 ttl=128 time=0.404 ms 64 bytes from 10.2.0.2: icmp_seq=6 ttl=128 time=0.435 ms 64 bytes from 10.2.0.2: icmp_seq=7 ttl=128 time=0.51 ms 64 bytes from 10.2.0.2: icmp_seq=8 ttl=128 time=0.696 ms 64 bytes from 10.2.0.2: icmp_seq=9 ttl=128 time=0.598 ms --- 10.2.0.2 ping statistics --- 10 packets transmitted, 10 packets received, 0% packet loss round-trip min/avg/max = 0.404/3.616/24.137 ms That looks pretty good. The name server ping looks equally good: --- 10.2.0.1 ping statistics --- 10 packets transmitted, 10 packets received, 0% packet loss round-trip min/avg/max = 0.36/0.49/1.372 ms > Are you going through restrictive routers? Not that I know of. > Can you direct the transaction to your authenticating server more directly... > i.e. does it have a different IP address? I'll check with our sysadmin (although they're not too Mac-friendly down there). I believe our computers have both internal (10.2.0.x) and external IP addresses, but not sure. > > Note that in your log below, eveything worked perfectly within a second > AFTER the network connection was established with the Authenicating Server > see the blue log below. Yeah I saw that. So Step 2 is where the network connection is established with the Authenticating Server? It's definitely Step 2 that's binding things up. --Steve > > I am inclined to think that the network connection is not pointing to > where you think it should be pointing. Check domain name IP addresses... > If you are using a proxy server then delete DNS entries. > > Cheers, > Bruce. > PS On a wet cold and miserable Melbourne day downUnder.
