Your question is not very clear. When the hoster says the server is "configured right", what are the particular features of the configuration that should be relevant to your task? (For example, does the config involve allowing scripts to be executed from directories other than "cgi-bin", and/or does it involve scripts to be executed if their file names end with a particular extension such as ".cgi" or ".pl"?)
If the web server config is "right" in terms of allowing your script file (in its current location, with its current file_name.extension) to be treated as an executable script -- and if this web server is a unix or linux OS -- you still need to check a couple things about the script file:
- Are the permissions on the file set so that it is executable? (See the "chmod" shell command, which is similar to the perl chmod function.)
- Does the first line of the script file (the "shebang" line) correctly identify the path to perl (and does the file use unix-style line termination -- line-feed only -- as opposed to dos/windows-style "CRLF")?