After a rebuild to replace what appears to be a faulty nic, the up2date system tries to talk to the internal up2date service (10.0.2.12?). I have rebuilt the system twice, but still have the same problem. I can't find where to change what it points at. You can't edit/delete the internal up2date host.
Tomorrow I will re-instal the system with the old card in and see what happens.
After a rebuild to replace what appears to be a faulty nic, the up2date system tries to talk to the internal up2date service (10.0.2.12?). I have rebuilt the system twice, but still have the same problem. I can't find where to change what it points at. You can't edit/delete the internal up2date host.
Tomorrow I will re-instal the system with the old card in and see what happens.
Gert,
thank you, I remember reading that thread at the time when my up2date was working without that fix. I haven't been able to determine what I did differently with this current configuration to the original.
I tried doing a restore of a saved configuration, but that function doesn't work. I have tried 3 different backup config files and each failed because the ht...... code failed after 5 attempts.
Gert,
I found the solution and it wasn't using your fix. The interface choice of "cable dhcp" doesn't load the gateway address. When put back to standard interface and a gateway address is entered manually the problem is resolved. Part of my problem was caused because I initially put the gateway on the wrong side of the firewall. I checked by forcing a renew and a reboot of the firewall v7b.
Now I know V6.303 which I am using to monitor the network behavior of the v7b passes the gateway info because it appears in the config checks of my PCs.
Now I have that working again it is back to learning how to make v7b tick better.
