What do do with Web Server

I use port forwarding on my router for port 80 to forward to a Windows 2000
server running a small home business web page. I have had this setup for
years, with previous versions of Foldershare coexisting just fine with that
setup.

Now I cannot view contents of any PC other that localhost (not even that on
windows 2000 machine), and the folders all just show as 'Sorry, there was an
unexpected error. Please try again.'

I have ports TCP (80,443, 6571 and 8000) open for send/receive on each
software firewall. Further I have made sure that Norton firewall allows those
ports for the Foldershare applicatin.

Foldershare correctly recognized other client seats as either online or
offline, but errors when connecting to the client PC. Interestngly, I do not
get the error when clicking on an offline client seat. The message just
correctly states that the target is offline. This is true for PCs with
dedicated IP addresses, and those behind NAT using DHCP.

When I disabled the port forwarding to test foldershare issues, I still
could not connect from PC to PC, nor create new folders. Reverting to
previous clients has not seemed to help.

I am not the most technical of network users, so maybe I am missing
something very basic here. I am thinking that some fundamental behaviors in
the program were changed when Fldershare was rolled into Microsoft
LiveServices, and those changes have wreaked havoc with many users.

For what it is worth, my login identity is not tied to a
MSN/Hotmail/passport login. It was creaated before Microsoft acquired
Foldershare, and is tied to a different email.

This issue should be fixed by our service/website/client updates that we
released today.

--
Jeremy Epling
Lead Program Manager - Windows Live FolderShare


"Q" wrote: