Re: PCANYWHERE can not access server
From: Steven L Umbach (n9rou_at_n0-spam-for-me-comcast.net)
Date: 01/11/05
- Next message: PA Bear: "Re: Virus? Or malware?"
- Previous message: O.B.: "Virus? Or malware?"
- In reply to: Jimmy: "PCANYWHERE can not access server"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Mon, 10 Jan 2005 23:09:11 -0600
If you have the built in ICF firewall enabled you can configure exemptions
for the needed ports and protocols - probably tcp in your case. The problem
with the Windows 2003 firewall, in the current release, is that if you open
up an exception those ports will be available to anyone with user
credentials being the only barrier to access. Open networking properties and
then the properties for your network adapters/advanced and if the firewall
is enabled click settings and create a new service for your needs by
entering the ports and protocols user. Tcp/ip filtering when enabled on the
adapters can also block access as can an ipsec flittering policy if
assigned. Other than that check your hardware firewall if used. Check the
logs in firewalls for dropped/blocked traffic can also be helpful. The
Windows 2003 built in firewall can log dropped packets if you have it
configured to do such. Note that Windows 2003 Server has Remote Desktop
built in that can be used for up to two connections. It uses port 3389
TCP. --- Steve
"Jimmy" <Jimmy@discussions.microsoft.com> wrote in message
news:BF800D52-B347-4991-A15F-5D84A6C37CFF@microsoft.com...
>I have Windows 2k3 standard server with two LAN cards.
> For some reasons, I can not remote access to Server by using PCANYWHERE.
> Can someone tell me where is the microsoft basic firewall block the
> access,
> or where I shoud open 5631 and 5632 for PCANYWHERE
- Next message: PA Bear: "Re: Virus? Or malware?"
- Previous message: O.B.: "Virus? Or malware?"
- In reply to: Jimmy: "PCANYWHERE can not access server"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
