Welcome to ISAserver.org
Forums |
Register |
Login |
My Profile |
Inbox |
RSS
|
My Subscription |
My Forums |
Address Book |
Member List |
Search |
FAQ |
Ticket List |
Log Out
ERROR: Firewall Client Winsock providers are not installed properly
|
Users viewing this topic:
none
|
Logged in as: Guest
|
Login | |
|
ERROR: Firewall Client Winsock providers are not instal... - 14.Apr.2005 12:42:00 PM
|
|
|
fermo2
Posts: 32
Joined: 1.Jan.2005
Status: offline
|
I have installed the Firewall Client sw on a Windows Server 2003 machine. I have started the fw client management appl and clicked on the Test Server button. The ISA Server answers correctly.
However TCP traffic is not intercepted by the fw client. In other words it doesn't work.
I have tried a "FwcTool PingServer" and the following error is returned: "Firewall Client Winsock providers are not installed properly"
Any idea what the reason could be?
Luca
|
|
|
|
RE: ERROR: Firewall Client Winsock providers are not in... - 15.Apr.2005 1:20:00 PM
|
|
|
tshinder
Posts: 47490
Joined: 10.Jan.2001
From: Texas
Status: offline
|
Hi Fermo,
Could be a number of things, but the most important question to ask first is why are you installing the Firewall client on a server?
Thanks! Tom
|
|
|
|
RE: ERROR: Firewall Client Winsock providers are not in... - 15.Apr.2005 10:38:00 PM
|
|
|
fermo2
Posts: 32
Joined: 1.Jan.2005
Status: offline
|
Hi Tom
it is my PC. It's an old habit to have server operating systems installed.
I should add that I have installed Windows Server 2003 SP1 Release Candidate.
I have installed the Firewall client on another machine with a clean Windows Server 2003 installation and everything worked fine.
My machine instead is an upgrade from Windows 2000 Server. It has also A LOT of software installed.
Luca [ April 15, 2005, 10:48 PM: Message edited by: fermo2 ]
|
|
|
|
RE: ERROR: Firewall Client Winsock providers are not in... - 19.Apr.2005 8:04:00 PM
|
|
|
ClintD
Posts: 1833
Joined: 26.Jan.2001
From: Keller, TX
Status: offline
|
Run the Support Tool NETDIAG on the machine and use the /test:winsock /v option (netdiag /test:winsock /v).
Look for this section near the bottom...
code:
Winsock test . . . . . . . . . . . : Passed The number of protocols which have been reported : 16 Description: Microsoft Firewall Client Service Provider [TCP/IP] Provider Version :2 Max message size : Stream Oriented Description: MSAFD Tcpip [TCP/IP] Provider Version :2 Max message size : Stream Oriented Description: Microsoft Firewall Client Service Provider [UDP/IP] Provider Version :2 Description: MSAFD Tcpip [UDP/IP] Provider Version :2 Description: Microsoft Firewall Client Service Provider for RSVP [UDP/IP] Provider Version :2 Description: RSVP UDP Service Provider Provider Version :6 Description: Microsoft Firewall Client Service Provider for RSVP [TCP/IP] Provider Version :2 Max message size : Stream Oriented Description: RSVP TCP Service Provider Provider Version :6 Max message size : Stream Oriented Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{56EED800-075A-4D92-93E5-D9B2C788CF5A}] SEQPACKET 3 Provider Version :2 Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{56EED800-075A-4D92-93E5-D9B2C788CF5A}] DATAGRAM 3 Provider Version :2 Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{D49F0E3B-6E93-41A0-9E20-9C144E91E2B7}] SEQPACKET 0 Provider Version :2 Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{D49F0E3B-6E93-41A0-9E20-9C144E91E2B7}] DATAGRAM 0 Provider Version :2 Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{0EBADD46-23DF-4AA1-9507-A6C11A32563F}] SEQPACKET 1 Provider Version :2 Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{0EBADD46-23DF-4AA1-9507-A6C11A32563F}] DATAGRAM 1 Provider Version :2 Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{2E57EF9B-1863-4360-B6BE-4FBA590A971B}] SEQPACKET 2 Provider Version :2 Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{2E57EF9B-1863-4360-B6BE-4FBA590A971B}] DATAGRAM 2
Look for other entries beside Firewall Client Service Provider and Stream Oriented.
Also in the section with entries like this...
Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{56EED800-075A-4D92-93E5-D9B2C788CF5A}] SEQPACKET 3
Look at the section in BOLD and look for other entries. Post the output of the command if you can - just the last portion though. There might be another WinSock provider installed that is interfering with the ISA Firewall Client. [ April 19, 2005, 08:06 PM: Message edited by: ClintD ]
|
|
|
|
RE: ERROR: Firewall Client Winsock providers are not in... - 20.Apr.2005 5:07:00 PM
|
|
|
fermo2
Posts: 32
Joined: 1.Jan.2005
Status: offline
|
Hi Tom!
GREAT help!
I found the following suspicious entry: Description: Google Desktop over [MSAFD Tcpip [TCP/IP]] Provider Version :2 Max message size : Stream Oriented
Uninstalling Google Desktop fixed the problem
THANK YOU
Luca [ April 20, 2005, 09:57 PM: Message edited by: fermo2 ]
|
|
|
|
RE: ERROR: Firewall Client Winsock providers are not in... - 22.Apr.2005 3:06:00 PM
|
|
|
fermo2
Posts: 32
Joined: 1.Jan.2005
Status: offline
|
What a gaffe! Sorry... and thanks again
Luca [ April 22, 2005, 03:07 PM: Message edited by: fermo2 ]
|
|
|
|
RE: ERROR: Firewall Client Winsock providers are not in... - 16.Sep.2005 7:02:00 AM
|
|
|
cinderellagcs
Posts: 9
Joined: 13.May2004
Status: offline
|
My machine doesn't have Google Desktop Search but it still exist this problem. Please give me an advise.
Thanks, Cinderellagcs
|
|
|
|
New Messages |
No New Messages |
Hot Topic w/ New Messages |
Hot Topic w/o New Messages |
Locked w/ New Messages |
Locked w/o New Messages |
|
Post New Thread
Reply to Message
Post New Poll
Submit Vote
Delete My Own Post
Delete My Own Thread
Rate Posts |
|