OneandOne network issues

[pnhe]

Hi

I am trying to upload my web catalogue to my space at oneandone. I have followed the info in the previous oneandone thread which has helped.

However, while running the web wizzard I get an error with the 'ftp directory paths' page - it reports an error with the web root directory - (which is currently set at / ) - saying that the web root directory path is incorrect. I cant progress past this stage.

Any ideas greatly appreciated.

Thanks

[HowardW]

Hi try
"./"
without the quotes
Howard

[pnhe]

Hi Howard

I enter the missing '.' but to no avail.

The Connection wizard still reports back 'either your web root dir path or web site address appears to be incorrect. The web connection wizard attempted to upload a file to the web root directory and download it via the web server but the web server reported that the file was not found The specific web server message was:' - - no message is in the field.

Anything else I can try?

Thanks

[garyhay]

use the toolbar menu item > Advanced>Network settings

Place your details in there then run the test

[pnhe]

I have now managed to sort this one out - it transpired that having previously used Oneandone's web site creator, I had to go in and manually redirect the web root directory back to "/".

Many thanks for everyones assistance.

[Admin]

oneandone network settings

Hi Peter,

How exactly have you configured actinic on oneandone's webserver? Where have you put the actinic and cgi-bin folders? I am having a great difficulty connecting to the web server.

Also is it possible for you to give me the network settings that you are using to connect to the webserver at Oneandone?

Do you use proxy server to upload the catalog or a dial-up connection?

Thank you very much in advanced.


__________________
NCT

[pnhe]

Hi

I used the settings detailed in a previous thread 'oneandone network settings'.

I think our problems started when we started playing with one&ones web site creator. We had to redirect the root back from pointing to WSC - then everything worked. Except every now and again we get a 403 error. This happens on different client machines and we think its cookie related as we have eliminted most other avenues.

We dont run through a proxy at the moment.

Good luck.