Welcome to ISAserver.org

Firewall Client Winsock providers are not installed properly?

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [ISA Server 2004 Firewall] >> Firewall Client >> Firewall Client Winsock providers are not installed properly?

Page: [1]

Message

<< Older Topic Newer Topic >>

Firewall Client Winsock providers are not installed pro... - 28.Jul.2004 1:31:00 PM

Ten

Posts: 20
Joined: 28.Jul.2004
From: Russian, Kirov
Status: offline

Dear all!

I have the following problem.
ISA server 2004 will not authorize me through Firewall Client. And the user for next computer - will authorize...
Has checked up everything, that only it is possible "[Frown]"

Eventually, has started utility FwcTool PingServer in my computer and has received the following:

quote:

FwcTool version 4.0.2161
Firewall Client for ISA Server 2004 support tool
Copyright (c) Microsoft Corporation. All rights reserved.

Action: Verify ISA Server connectivity

Error: Firewall Client Winsock providers are not installed properly

Result: The command failed and was not completed.

In the documentation the description of this mistake has not found. What further to do - I do not know. Help me please.

Post #: 1

Featured Links*

RE: Firewall Client Winsock providers are not installed... - 29.Jul.2004 2:09:00 AM

tshinder

Posts: 47490
Joined: 10.Jan.2001
From: Texas
Status: offline

Hi Tengiz,

Try uninstalling the firewall client and reinstalling it. Sounds like the install didn't work correctly.

HTH,
Tom

(in reply to Ten)

Post #: 2

RE: Firewall Client Winsock providers are not installed... - 29.Jul.2004 5:55:00 AM

Ten

Posts: 20
Joined: 28.Jul.2004
From: Russian, Kirov
Status: offline

I made it so many times - without results [Frown]

And made it on two computers. And both such mistake. And on the third - all is good.

(in reply to Ten)

Post #: 3

RE: Firewall Client Winsock providers are not installed... - 29.Jul.2004 11:13:00 AM

Ten

Posts: 20
Joined: 28.Jul.2004
From: Russian, Kirov
Status: offline

The trouble was fixed! [Big Grin]

Component IMON from NOD32 Antivirus system made badly.

Thanks for support!

(in reply to Ten)

Post #: 4

RE: Firewall Client Winsock providers are not installed... - 29.Jul.2004 2:11:00 PM

tshinder

Posts: 47490
Joined: 10.Jan.2001
From: Texas
Status: offline

Hi Tengiz,

Great! Good to hear you got it working and thanks for the follow up!

Tom

(in reply to Ten)

Post #: 5

RE: Firewall Client Winsock providers are not installed... - 16.Feb.2006 11:00:43 AM

Bugriy

Posts: 3
Joined: 16.Feb.2006
Status: offline

Is it possible to make NOD32 service IMON work with firewall client correctly? All of my workstations has this antivirus and IMON is a very important service for network security.

(in reply to tshinder)

Post #: 6

RE: Firewall Client Winsock providers are not installed... - 3.Mar.2006 2:27:49 AM

vrag_gosudarstva

Posts: 6
Joined: 3.Mar.2006
Status: offline

Hi!
It would help you, Ten
h**p://195.46.107.2/microsoft/mpc/

(in reply to Bugriy)

Post #: 7

RE: Firewall Client Winsock providers are not installed... - 22.Mar.2006 12:54:30 PM

Bugriy

Posts: 3
Joined: 16.Feb.2006
Status: offline

I have uninstalled NOD32 but it does not help. FWC is not working correctly. FWCtool writes
Error: Firewall Client Winsock providers are not installed properly
Result: The command failed and was not completed.
I have reinstalled firewall client without any result.

(in reply to vrag_gosudarstva)

Post #: 8

RE: Firewall Client Winsock providers are not installed... - 27.Mar.2006 11:34:09 PM

minerat

Posts: 131
Joined: 19.Mar.2003
From: Philadelphila
Status: offline

I had a similiar issue on one of my workstations - wasn't passing credentials for mstsc (probably for all apps - also had NOD32, but IMON was disabled). I initially uninstalled the FWC & reinstalled - no change. Then I ran fwctool and saw the winsock errors. I uninstalled FWC, uninstalled NOD32 & rebooted. I reinstalled FWC & rebooted. It connected no problem and passed fwctool tests. I reinstalled NOD32 (imon still disabled), rebooted and it was working. IMON is now enabled with exclusions and no further issues.

(in reply to Bugriy)

Post #: 9