Ok this is an odd issue but I have had it happen three times now. And it did it on 2 seperate networks that are completely different to rule out it being a windows issue.
I got a Windows 2000 Server (PDC) running the network with ASL as the firewall/NAT (no proxy). Usually after about 3+ weeks of the ASL box running my Windows 2000 servers start getting IP conflicts. So what I do is change the Windows 2000 IP to something completely different and it conflicts at EVERY IP address no matter what I put in.
I can remote access both my ASL box and Terminal server into the 2000 Server but the workstations on the local network cant access the 2000 Server. They do MASQ out correctly though.
So what I do is reboot the ASL box or just shut it down and everythign works perfectly. Restart ASL and everything is back to normal. And it takes usually 3+ weeks of ASL continually running to do it.
I have uses stable versions of v2 and also beta versions both did it. SInce Beta 3 is new I will let you know if I see it happen. I went ahead and put a beta 3 box out there to see if the problem happens.
Anyone have the same problem? I got it to happen on completely different networks so it kinda worries me. I dont find anythign in the ASL logs about issues so I have no ideas..
Thanks
Resistance
"For any Microsoft network there is always a linux box protecting it =)"
This thread was automatically locked due to age.