P
(PeteCresswell)
I just spent the better part of a day trying to figure out why
the IP camera server on a remote PC had started FTP-ing
zero-length files to my home PC.
All I had done was:
- Shut down the server PC
- Move it from a Verizon DSL-connected site
to a Comcast Cable-connected site
That's all, nothing else... nada.
Along with the move, the Ethernet connection to the new local LAN
started having problems too. Somebody with more presence of
mind than I thought to disable the connection and then re-enable
it and the problem went away.
What I eventually doped out my own was that Windows had removed
parts (not all... just parts) of the firewall exceptions for the
camera server - causing the FTPs to fail once the app tried
actually transferring data.
Could the firewall change have somehow been connected to Windows'
changing my firewall settings all on it's own?
the IP camera server on a remote PC had started FTP-ing
zero-length files to my home PC.
All I had done was:
- Shut down the server PC
- Move it from a Verizon DSL-connected site
to a Comcast Cable-connected site
That's all, nothing else... nada.
Along with the move, the Ethernet connection to the new local LAN
started having problems too. Somebody with more presence of
mind than I thought to disable the connection and then re-enable
it and the problem went away.
What I eventually doped out my own was that Windows had removed
parts (not all... just parts) of the firewall exceptions for the
camera server - causing the FTPs to fail once the app tried
actually transferring data.
Could the firewall change have somehow been connected to Windows'
changing my firewall settings all on it's own?