Results 1 to 6 of 6

Thread: XP Firewall Problems

  1. Aug 15th, 2004, 02:23 PM #1
    alacritous
    alacritous is offline

    Thread Starter
    Hyperactive Member alacritous's Avatar
    Join Date
    Aug 2003
    Posts
    464

    XP Firewall Problems

    Hello,
    I am having a slight problem with the Windows XP Pro Built-In Firewall. OK, I have some programs like FTP Servers, Web Servers, and the like. Those all work. I have a Remote Control program (TightVNC) and it doesn't work. I choose "Add" and put in my ports and everything. I put the LAN IP, etc. So, when I try and connect to the server side using the client it doesn't work.

    I am not sure if this is the TightVNC problem, although, I have never experienced such problems. The other part could be the XP Firewall. I use the right port type (protocol?) for the port, TCP.

    I am stuck!
    alacritous
    Reply With Quote Reply With Quote
  2. Aug 15th, 2004, 05:06 PM #2
    szlamany
    szlamany is offline
    MS SQL Powerposter szlamany's Avatar
    Join Date
    Mar 2004
    Location
    Connecticut
    Posts
    18,263
    IPSEC (?guessing at the spelling) policy - I think a customer of mine changed this to make a VPN work...
    Reply With Quote Reply With Quote
  3. Aug 16th, 2004, 01:35 AM #3
    Ideas Man
    Ideas Man is offline
    Frenzied Member Ideas Man's Avatar
    Join Date
    Aug 2002
    Location
    Australia
    Posts
    1,718
    I'd install Service Pack 2 and get the new Windows Firewall, it's much easier to setup and should prompt you about adding a rule for it when you run it.
    I use Microsoft Visual Basic 2005. (Therefore, most code samples I provide will be based around the .NET Framework v2.0, unless otherwise specified)
    Reply With Quote Reply With Quote
  4. Aug 16th, 2004, 09:14 PM #4
    alacritous
    alacritous is offline

    Thread Starter
    Hyperactive Member alacritous's Avatar
    Join Date
    Aug 2003
    Posts
    464
    Originally posted by szlamany
    IPSEC (?guessing at the spelling) policy - I think a customer of mine changed this to make a VPN work...
    Yes, I have heard about this. I might look into this. For now, ahem, I have disabled it (DOH!). Now yes, this is totally stupid, especially for a server, but I have to be able to control it remotely.

    Originally posted by Ideas Man
    I'd install Service Pack 2 and get the new Windows Firewall, it's much easier to setup and should prompt you about adding a rule for it when you run it.
    Ah, yes, I see. The problem is the fact that programs won't work after that. Most of the programs I run on that computer (SERVER) are, heh, fairly old and are freeware. Obviously, freeware authors don't have the time to always keep up with stuff like this.

    Thank you!
    alacritous
    Reply With Quote Reply With Quote
  6. Aug 18th, 2004, 01:23 AM #5
    Ideas Man
    Ideas Man is offline
    Frenzied Member Ideas Man's Avatar
    Join Date
    Aug 2002
    Location
    Australia
    Posts
    1,718
    That shouldn't matter, Windows does that automatically, I don't think they need to 'hook into' it at all.
    I use Microsoft Visual Basic 2005. (Therefore, most code samples I provide will be based around the .NET Framework v2.0, unless otherwise specified)
    Reply With Quote Reply With Quote
  7. Aug 18th, 2004, 01:26 AM #6
    dglienna
    dglienna is offline
    Banned dglienna's Avatar
    Join Date
    Jun 2004
    Location
    Center of it all
    Posts
    17,901
    Use netstat -ano to see what programs are using your computer ports. if they don't appear, turn off the firewall and try it again, and then re-configure the firewall to let them through
    Reply With Quote Reply With Quote
« Previous Thread | Next Thread »

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

Forum Rules


Click Here to Expand Forum to Full Width