M
Michael Parisi
My firewall is blocking port 80 from my file server since
it is strictly a file server. The traffic log on the
firewall shows my windows xp pro clients trying to
connect to the file server over tcp port 80 and are being
blocked. This is causing a long delay when a user tries
to open a mapped network drive to a file share on the
file server. Once the connection is made and the folders
and file are displayed users can close the file share and
reopen the mapped drive immediately without delay. The
delay then reappears if they reboot the computer or wait
an unknown amount of time before reopening the share. If
I add a rule allowing tcp port 80 to the file server the
delay is gone. Why is windows XP using port 80 to
connect to file shares on a windows 2000 server?
Thanks,
Mike
it is strictly a file server. The traffic log on the
firewall shows my windows xp pro clients trying to
connect to the file server over tcp port 80 and are being
blocked. This is causing a long delay when a user tries
to open a mapped network drive to a file share on the
file server. Once the connection is made and the folders
and file are displayed users can close the file share and
reopen the mapped drive immediately without delay. The
delay then reappears if they reboot the computer or wait
an unknown amount of time before reopening the share. If
I add a rule allowing tcp port 80 to the file server the
delay is gone. Why is windows XP using port 80 to
connect to file shares on a windows 2000 server?
Thanks,
Mike