Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

error: Bad protocol 'tcp'

2 views
Skip to first unread message

Pratik

unread,
Oct 3, 2003, 3:02:03 PM10/3/03
to
Hi,

I get the following error when running a perl script on
my winxp PC:

500 (Internal Server Error) Can't connect to
www.anywhere.com:80 (Bad protocol 'tcp')

I dont have access to any site thru a script, and some
sites thru a browser (ex. yahoo opens but google doesnt).

Seems like tcp isnt recognized as a protocol, can
somebody tell me where should i be looking for a protocol
file on a winxp pro?

Thanks.

Michael Solomon (MS-MVP Windows Shell/User)

unread,
Oct 3, 2003, 4:37:13 PM10/3/03
to
I believe this is a script problem and not a problem with TCP/IP. A Google
search seems to indicate this is a common problem when running certain
scripts. These are not the boards for this type of issue.

Have you checked www.perl.com?

--
Michael Solomon MS-MVP
Windows Shell/User
Backup is a PC User's Best Friend
DTS-L.Org: http://www.dts-l.org/

"Pratik" <psa...@hotmail.com> wrote in message
news:037c01c389e0$d508cff0$a301...@phx.gbl...

Pratik

unread,
Oct 3, 2003, 4:54:12 PM10/3/03
to
this is definitely not a script problem... it runs fine
on an adjacent PC. it ran fine till yest on this one too
and now suddenly it doesnt run... nor can i open a few
sites like google, yahoo search...

500 Internal server error is a common cgi problem... u
think i havent looked on google... but bad protocol 'tcp'
is something else and my script isnt even a CGI script.

btw, this one has been posted on perl as well... i just
wanted to know where on winxp pro shud i look for
protocol info...

thanks.

>.
>

Michael Solomon (MS-MVP Windows Shell/User)

unread,
Oct 3, 2003, 5:18:06 PM10/3/03
to
I'm not sure the fact it runs on an adjacent PC is significant unless it was
identical in every way to the PC on which you receive the error. By that, I
don't mean the script itself is a problem but running that script may be the
triggering event.

That said, if you think the TCP\IP protocol is corrupt, go to Connect To,
select your connection, right click, select properties, select Internet
Protocol (TCP/IP) click uninstall, reboot the system, return to that area,
click install and add it back. You will probably be asked for your XP CD
during the reinstall of the protocol.

--
Michael Solomon MS-MVP
Windows Shell/User
Backup is a PC User's Best Friend
DTS-L.Org: http://www.dts-l.org/

"Pratik" <psa...@hotmail.com> wrote in message

news:06bb01c389f0$800abe90$a101...@phx.gbl...

Pratik

unread,
Oct 3, 2003, 5:40:42 PM10/3/03
to
Thats exactly what i did... but using the following
command:
netsh int ip reset "c:\log.txt"
and it works fine now :))) i told u it was the protocol...
thanks...

>.
>

Michael Solomon (MS-MVP Windows Shell/User)

unread,
Oct 3, 2003, 6:43:29 PM10/3/03
to
LOL, yeah, you sure did tell me!

I'm glad you got it sorted out.

You're Welcome.

--
Michael Solomon MS-MVP
Windows Shell/User
Backup is a PC User's Best Friend
DTS-L.Org: http://www.dts-l.org/

"Pratik" <psa...@hotmail.com> wrote in message

news:05ae01c389f6$fe718b00$a301...@phx.gbl...

0 new messages