We too have begun to see the problem Erik mentions- just over the last
week. Server version 3.5.6; client 3.5.8. Devices that previously worked
without issue (and without change) are now unable to connect. The fixes
that Tim and Michael mention do not seem to provide a remedy. I'm
reading up on the 3.5.8 upgrade now to see if anything can be gleaned
therein...

- Gerard Duguay, CIS
Seattle Pacific University

-----Original Message-----
From: Perfigo SecureSmart and CleanMachines Discussion List
[mailto:[log in to unmask]] On Behalf Of King, Michael
Sent: Tuesday, November 29, 2005 11:02 AM
To: [log in to unmask]
Subject: Re: The attempt to connect to the server failed [12029]

We ran into that alot on our orignal deployment.  We chose 192.168.1.1
for our Untrusted interface.  It was a major problem.

Windows clients would not give up there invalid IP's, because the DHCP
server was pingable.  

Changing it to 10.x.x.x fixed that.  (A little less common)

________________________________

From: Perfigo SecureSmart and CleanMachines Discussion List
[mailto:[log in to unmask]] On Behalf Of Grzeczka, Timothy J.

2.	The other cause can be an IP issue. This is especially true with
our few Windows 98 users. If they move between subnets, especially from
a public subnet to a CCA controlled subnet, they don't get an IP from
the new subnet. They need to do a release and renew via winipcfg to get
online. Windows XP doesn't have that problem usually, but I have seen it
a few times.