Topic: Strange i-bay creation behaviour

[Jason Judge]

I created an i-bay 'ibay1' and forgot to select the website access option. As would be expected, the i-bay was created as a simple Samba share.

Now I went back to change the i-bay to enable web access, but the Samba share does not seem to get updated: i.e. I do not see the html/files/cgi-bin directories in it.

So, I remove the i-bay completely, then recreate it properly. Except it appears just like before, just a simple Samba file share and no web directories!

Now I remove it again and it won't go away from the network shares when I browse the server using Windows 2000 network-neighbourhood. Trying to access the share (which no longer appears as an i-bay) just gives me an 'access denied' error.

This is entirely repeatable. When I first created the i-bay, the 'enable cgi' option was selected.

Is this just my SME5.1.2 setup, or a bug?

-- Jason

[Dub Dublin]

I've seen something like this, too.  At least sometimes, it has to do with some sort of cacheing of available resources on the client end, and rebooting the client will fix it.  Other times, though, it doesn't, so it does appear that the server is doing something to at least confuse the client, if not actually fail to make resourdes properly available.  I'll try to repeat this when I build up a new 5.1.2 server tomorrow.