This error message is a symptom for several different problems.
I solved this problem when I realized that the XP32 box was able to do this with IE8. So I went back to IE8 in 7x64 (you need to do this by uninstalling updates for IE until you return to 8), and that didn't work. The build options were different, but in the βaboutβ field of 7x64 he said that IE8 uses a 256-bit cipher, while in XP32 it had 128-bit. This was a hint to me that 64-bit problems are possible, even if you are running a 32-bit executable.
Then I found this fix , so I reinstalled the Windows update for IE10 and installed this fix. Now I can open the TeamCenter site in question in Windows Explorer. IE10 reports version 10.0.9200.16686. I cannot guarantee that this is only the fix (and not reinstalling IE10) that fixed it. But I bet it was just a fix.
In XP, I was not able to map this network location to a drive letter, because the mapping is not like a URL. However, in Windows 7, you can translate the URL so that it is interpreted as a Windows share. If the URL of this folder has the following form:
https:
you can also access it as
\\somesharepoint.com@SSL\DavWWWRoot\folder1\folder2\folder3
and in this form it can be mapped to the drive letter.
I have problems at this point that even when I open and log in IE10 to the site, I see random timeouts similar to the problems, and they start to run me (and were asked to log into IE10 again). My situation is complicated, because to access the site I need an Exostar token to log in, so I have to log in to the site through the website, no matter what.
pelesl
source share