Re: bad protocol 'tcp' win32 error because getprotobyname is failing

Before you go to the pain of re-installing tcp/ip, take a look in C:\WINDOWS\SYSTEM32\DRIVERS\ETC\PROTOCOL

Mine looks like this:

# Copyright (c) 1993-1999 Microsoft Corp.
#
# This file contains the Internet protocols as defined by RFC 1700
# (Assigned Numbers). 
#
# Format:
#
# <protocol name>  <assigned number>  [aliases...]   [#<comment>]

ip       0     IP       # Internet protocol
icmp     1     ICMP     # Internet control message protocol
ggp      3     GGP      # Gateway-gateway protocol
tcp      6     TCP      # Transmission control protocol
egp      8     EGP      # Exterior gateway protocol
pup      12    PUP      # PARC universal packet protocol
udp      17    UDP      # User datagram protocol
hmp      20    HMP      # Host monitoring protocol
xns-idp  22    XNS-IDP  # Xerox NS IDP
rdp      27    RDP      # "reliable datagram" protocol
rvd      66    RVD      # MIT remote virtual disk
[download]

Examine what is said, not who speaks.

"Efficiency is intelligent laziness." -David Dunham
"Think for yourself!" - Abigail
"Memory, processor, disk in that order on the hardware side. Algorithm, algoritm, algorithm on the code side." - tachyon

Comment on Re: bad protocol 'tcp' win32 error because getprotobyname is failing Select or Download Code

Replies are listed 'Best First'.
Re^2: bad protocol 'tcp' win32 error because getprotobyname is failing by tachyon (Chancellor) on Jul 15, 2004 at 05:44 UTC
Thanks BrowserUk I ran filemon.exe and regmon.exe from Sysinternals which showed up this location (after I had posted) - the protocol file is still there on the broken box and looks just like the above. Regmon does not show the issue either when you diff the results of a working and broken system and filter for Winsock2. cheers tachyon	[reply]