On Wed, 1 Sep 2004, Brian Raven wrote:
> [EMAIL PROTECTED] wrote:
> > Hi All
> >
> > Thanks to everyone for the suggestions. Unfortunately I'm
> > still having no
> > luck. I have upgraded the Win2000 SP2 box to 5.8.4.
> >
> > When I run the example below I get this error and the machine makes no
> > attempt to connect to the requested URL ( I can tell 'cos I'm using
> > 'tcpview' to look for activity. It's almost as though the PERL library
> > doesn't think that there is a TCP connection available.
> >
> > ###########
> > 500 (Internal Server Error) Can't connect to perl.org:80 (Bad
> > protocol 'tcp') Content-Type: text/plain
> > Client-Date: Wed, 01 Sep 2004 15:59:37 GMT
> > Client-Warning: Internal response
> > 500 Can't connect to perl.org:80 (Bad protocol 'tcp') ##########
> >
> > Not sure what this is about. Anyone got any ideas. I have the machine
> > connected to to the internet via ADSL and everything work
> > fine for browsing,
> > ftp etc. and I have tried disabling the firewall etc.
>
> The message "Bad protocol 'tcp'" is usually caused by the call to
> getprotobyname failing. IIRC, all that this system call does is look up
> the protocol ('tcp' in this case) in the file
> c:winnt/system32/drivers/etc/protocol. Its possible that the other
> programs that you have used don't call getprotobyname. If that file is
> missing or corrupt, it might suggest that the OS or networking has not
> been properly installed, or has been mucked about with in some way.
>
> HTH
There was a problem with ppm reported on the ppm mailing
list that may be relevant - see
http://aspn.activestate.com/ASPN/Mail/Message/ppm/2132449
--
best regards,
randy kobes
_______________________________________________
ActivePerl mailing list
[EMAIL PROTECTED]
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
