FrontPage 2000 - Website access errors

I created a web using Front Page 2000 and I am hosting it on an Apache Server. I have an access and error log so I can see the detailed access information. Occassionaly I get IP's trying to access items that are not on the web and my concern is that they are trying to hack and I use my firewall to block their IP's. The most common access errors I get is when they try to access the following:
"robots.txt" "fphoverBeanInfo.class" "fphover$COMClassObject.class" and "default.ida "...the default item sometimes has the extensions .a .d . Can some one give me a clue as to what they are and if I should be concerned. I can always block the IP with my firewall but if it's not a problem I might not need to.

Thanks

 

Thanks. I was up in the air about how to title it. ASppreciate your help.

 

ASppreciate your help - ASP preciate Love it.

Code:

[error] [client 194.45.109.171] File does not exist: /usr/......./classes/DgclockBeanInfo.class
[error] [client 203.23.27.1] File does not exist: /usr/......../_fpclass/fphoverBeanInfo.class

This thread may give you a hint and a starting place.

 

Thanks I had an idea it might be a Front Page issue because of the fp but I am running on a windows 98 platform but the info was helpfull. Thanks again

 

robots.txt is accessed by web-crawler "robots" used by search-engines. The file tells the robot whether to just "go away ", or which parts of the site the webmaster wants to be excluded from a search. It's also possible to tell the robot not to return until a specific period has elapsed. These days the functions are more commonly carried out by a Robots meta-tag in HTML. If you want your page indexed by as many search engines as possible, you'd do well not to block those IPs. Download a useful utility called "Sam Spade" (no kidding!) It has excellent facilities for tracing IP addresses on internet databases like ARIN.

default.ida is searched for by the "Code Red II" worm looking for MS IIS servers to infect - yet another MS vulnerability. Won't affect you of course.

The other items are because there are inconsistencies/errors in the Frontpage webpage you've created. Not your fault, Frontpage is not exactly the best or most efficient creator of HTML code.