J
Joan Edington
Hi,
I've scoured the groups and have found several posts regarding the I/P
address "169.254.0.0", being that which APIPA allocates when the DHCP
server is unavailable for any length of time. That I can understand,
but not my own particular problem which I am sure several ZoneAlarm
Pro users also have.
My Win XP PC accesses the Internet (broadband) via an eTec ADSL
router. This router allocates my I/P address, presumably acting as a
DHCP server would.
When not using the PC I always lock ZoneAlarm. Now, every time I
unlock it, my network has disappeared, to be replaced by the New
Network "169.254.0.0".
The only way I can get round this is to re-boot the machine. Surely
this shouldn't be necessary. My partner uses Win2K through the same
router and doesn't have this problem.
Please can someone give me a clue of any way to avoid having to
re-boot or leave my system open at all times.
Thanks.
Joan
I've scoured the groups and have found several posts regarding the I/P
address "169.254.0.0", being that which APIPA allocates when the DHCP
server is unavailable for any length of time. That I can understand,
but not my own particular problem which I am sure several ZoneAlarm
Pro users also have.
My Win XP PC accesses the Internet (broadband) via an eTec ADSL
router. This router allocates my I/P address, presumably acting as a
DHCP server would.
When not using the PC I always lock ZoneAlarm. Now, every time I
unlock it, my network has disappeared, to be replaced by the New
Network "169.254.0.0".
The only way I can get round this is to re-boot the machine. Surely
this shouldn't be necessary. My partner uses Win2K through the same
router and doesn't have this problem.
Please can someone give me a clue of any way to avoid having to
re-boot or leave my system open at all times.
Thanks.
Joan