Re: vpn - problems after connecting

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

i do not know anything about somebody or something using H.323 and the error
on the server is also there when all client computers are down.

i found the H.323 filter already disabled in the ISA Server Management.

the version of the isa server is 3.0.1200.365 SP2 - how can i update it ?



"Merv Porter [SBS-MVP]" wrote:

Am I correct that you're not using H.323 on your network? If so, try
disabling the H.323 filter in ISA 2004 (I assume you're using ISA 2004)...

To configure H.323 filter
+ In the console tree of ISA Server Management, click Add-ins:
+ For ISA Server 2004 Standard Edition, expand Microsoft Internet Security
and Acceleration Server 2004, expand Server_Name, expand Configuration, and
then click Add-ins.
+ In the details pane, on the Application Filters tab, select the H.323
Filter.
+ Right click on the h.323 filter and select Disable
+ Click the Apply button at the top of the menu
+ In the popup, click on "Save changes and Restart services"

--
Merv Porter [SBS MVP]
===================================
"Mike" <Mike@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:96788ED4-66D6-4B2C-B835-D6C4CE27EA19@xxxxxxxxxxxxxxxx
sorry - forgot to select it after configuring.

with ip adress assignment in routing and remote access:

Static address pool
192.168.0.111 to 192.168.0.120

there are the same errors and the ip adress changed in the following
error:

Failed to create a RAS context for the IP address 192.168.0.111. Please
insure that no other application or service is using the H.225 RAS ports
(1719 and 1718). Context status code: 00002741H Context status text: The
requested address is not valid in its context.

"cjobes" wrote:

It's still the same IP address as in your first error. I thought you have
changed RRAS to a different static pool that is outside the scope of the
DHCP.


"Mike" <Mike@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:254ACD2C-6BAB-4ACD-9456-8AE204A69B03@xxxxxxxxxxxxxxxx
Event Type: Error
Event Source: Microsoft H.323 Gatekeeper
Event Category: None
Event ID: 21075
Date: 08.05.2006
Time: 09:10:33
User: N/A
Computer: SBSERVER
Description:
Failed to create a RAS context for the IP address 192.168.0.169. Please
insure that no other application or service is using the H.225 RAS
ports
(1719 and 1718). Context status code: 00002741H Context status text:
The
requested address is not valid in its context.

Event Type: Error
Event Source: Microsoft H.323 Gatekeeper
Event Category: None
Event ID: 21056
Date: 08.05.2006
Time: 09:10:33
User: N/A
Computer: SBSERVER
Description:
An error has been returned by the <WSAJoinLeaf> API. API error code:
00002741H. API error text: The requested address is not valid in its
context.

Event Type: Error
Event Source: Microsoft H.323 Gatekeeper
Event Category: None
Event ID: 21056
Date: 08.05.2006
Time: 09:10:33
User: N/A
Computer: SBSERVER
Description:
An error has been returned by the <setsockopt> API. API error code:
00002741H. API error text: The requested address is not valid in its
context.


Event Type: Error
Event Source: SOCKS Filter
Event Category: None
Event ID: 20002
Date: 08.05.2006
Time: 08:29:51
User: N/A
Computer: SBSERVER
Description:
SOCKS filter: failed to bind IP address 192.168.0.2:1080 for listening.
Future SOCKS requests will be refused.


Event Type: Warning
Event Source: Microsoft Firewall
Event Category: None
Event ID: 14060
Date: 08.05.2006
Time: 08:29:51
User: N/A
Computer: SBSERVER
Description:
Cannot load an application filter SOCKS V4 Filter
({25765C04-C80B-494C-914E-286297DB8C8E}). FilterInit failed with code
0x80072740. To attempt to activate this application filter again, stop
and
restart the Firewall service.

Event Type: Error
Event Source: Symantec Mail Security for Microsoft Exchange
Event Category: Error
Event ID: 283
Date: 08.05.2006
Time: 14:15:34
User: N/A
Computer: SBSERVER
Description:
An error has occurred trying to send an email notification.
The error occurred while sending LiveUpdate notifications to
administrators.
Error code returned: 0x80004005

Event Type: Error
Event Source: Symantec Mail Security for Microsoft Exchange
Event Category: LiveUpdate/Rapid Release
Event ID: 35
Date: 08.05.2006
Time: 14:15:34
User: N/A
Computer: SBSERVER
Description:
LiveUpdate was unable to complete successfully. More information may
be
available in C:\Documents and Settings\All Users\Application
Data\Symantec\LiveUpdate\Log.LiveUpdate




"cjobes" wrote:

Has the IP address changed in the new errors? Post the new errors as
they
appear in the event logs and don't forget to give us the source as
well.

"Mike" <Mike@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:00410638-B59C-45DA-880A-A13C847440B3@xxxxxxxxxxxxxxxx
changed the routing and remote access from dhcp to static pool -
reruned
internet connection wizard and remote access wizard - socks proxy
error
still
there in app-evt-log

where can i find the winproxy properties ?


"cjobes" wrote:

You still didn't give us the source but I think I know what is
going
on.
It
looks like you have an IP address conflict. One way of testing this
is
to
change the Routing and Remote Access from DHCP to an unused static
address
pool.

It could be that another service is using the specified IP address.
In
most
cases this address has been bound to the WinProxy service. Open the
WinProxy
properties and remove the offending IP from its list.

I would first try solution one and see if it resolves the issue.
Just
make
sure that you are using a static pool that is not used anywhere
else.

Claus

"Mike" <Mike@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:4876B15A-78C7-4AAE-BBD9-D428C525DC4A@xxxxxxxxxxxxxxxx
20002

SOCKS Filter

SOCKS filter: failed to bind IP address 192.168.0.2:1080 for
listening.
Future SOCKS requests will be refused.

21075
Microsoft H.323 Gatekee

Failed to create a RAS context for the IP address 192.168.0.169.
Please
insure that no other application or service is using the H.225
RAS
ports
(1719 and 1718). Context status code: 00002741H Context status
text:
The
requested address is not valid in its context.

21056


21056
Microsoft H.323 Gatekee
An error has been returned by the <WSAJoinLeaf> API. API error
code:
00002741H. API error text: The requested address is not valid in
its
context.


21056
Microsoft H.323 Gatekee
An error has been returned by the <setsockopt> API. API error
code:
00002741H. API error text: The requested address is not valid in
its
context.


"cjobes" wrote:

Give us the detailed info on the errors from the eventlogs
(Event
ID,
Source, Description)

Claus

"Mike" <Mike@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D6738CE7-F6DE-4D08-B23D-44360E618998@xxxxxxxxxxxxxxxx
we do not use any services on this ports... no VoIP...

maybe spyware, adware ? or a client which uses VoIP ???

"cjobes" wrote:

What are you running there? Those ports are phone related
ports
for
VoIP?

Claus

"Mike" <Mike@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:850EBA0C-0093-47DF-A5A2-340277EB1FDF@xxxxxxxxxxxxxxxx
we have notebooks connecting to our sbs 2003 premium sp1 (2
nic´s)

suddenly after a windows update some days ago after
connecting
to
the
server
via vpn the connections gets established but then the
services
like
internet,
outlook, ecc. do not work.
after rerunning the internet connection wizard on the
server
everything
works for some hours than same problem.

we have this event errors:

failed to create a RAS context for the IP address
192.168.16.165.
Please
insure that no other application or service is using the
H.225
RAS
ports
(1719 and 1718). Context status code: 00002741H Context
status
text:
The
requested address is not valid in its context.

An error has been returned by the <WSAJoinLeaf> API. API
error
code:
00002741H. API error text: The requested address is not
valid
.

Quantcast