Hi,
A google search on 'windweb' indicates that it is a web server for embedded
systems with limited memory.
http://www.roe.ac.uk/atc/projects/vista/background/phase_b/software/VxWorks/docs/windweb/guide/c-overview.html#84477
Note that the ftp server is VxWorks....same as the web server. Can you
describe your linux installation? Did you install these programs?
Can you find their directories using slocate?
I am running out of answers on this but the information might be useful for
others to help you solve your problem. Plus it is an interesting question.
Regards,
Bill W.
On Wednesday 06 August 2003 05:18 am, Anne Wilson wrote:
> On Wednesday 06 Aug 2003 12:48 pm, Derek Jennings wrote:
> > On Wednesday 06 Aug 2003 11:37 am, Anne Wilson wrote:
> > > On Wednesday 06 Aug 2003 11:13 am, Derek Jennings wrote:
> > > > Personally I find that http://scan.sygatetech.com/ is a better
> > > > firewall test site.
> > >
> > > Sorry for hijacking - but need clarification of sygatetech's
> > > report. It saw my outwardfacing ip - fine. It saw Linux i686 and
> > > Netscape Navigator 5.0 - to be expected, I think. Then, in
> > > services found, it said
> > >
> > > Web Server Found = Server: WindWeb/1.0.2
> > > FTP Server Open = 220 VxWorks (5.4.1) FTP server ready
> > >
> > > This is a complete surprise to me, as to the best of my knowledge
> > > I don't have either of these. What is it seeing?
> > >
> > > Anne
> >
> > Dunno. It reports my Web server and Mail server OK. Are you
> > connecting through a proxy?
>
> I connect through a router/firewall. The web interface for this
> doesn't allow me many options for configuring the firewall, though,
> so it's difficult to know exactly how it is configured.
>
> It didn't report any more than I have told you, so I presume that it
> couldn't find anything else - it certainly couldn't get the computer
> name. I did wonder if it was my isp's web server and ftp server that
> it was seeing.
>
> Anne
>
> > Going a bit Off Topic I was surprised to see in the Sygate Quick
> > Scan that my ports 113 and 135 were reported as 'Closed' instead of
> > 'Blocked' like the others. grc.com also agreed these ports were
> > 'closed'.
> >
> > A quick look at the FAQ on the shorewall site at
> > http://www.shorewall.net/FAQ.htm#faq4 tells me that shorewall will
> > by default leave these ports 'closed' because it cuts down on
> > 'chatter' in Windows/Samba networks. So thats another mystery
> > solved :-)
> >
> > derek
Want to buy your Pack or Services from MandrakeSoft?
Go to http://www.mandrakestore.com
