Re: Sygate blocking DHCP from starting

From: Piotr Makley (pmakley_at_mail.com)
Date: 03/05/04 

Date: Fri, 05 Mar 2004 13:54:59 GMT

Duane Arnold <notme@notme.com> wrote:

> Piotr Makley <pmakley@mail.com> wrote in
>
>> I a running Sygate Personal Firewall Pro version 5.0 on WinXP
>> Pro.
>>
>> After booting, I cannot connect to the network. The DHCP
>> client won't start.
>>
>> Sygate's traffic log shows it is blocking incoming UDP packets
>> from 10.82.32.1: 67 going to 255.255.255.255: 68.
>>
>> How do I get Sygate to permit these incoming UDP packets?

> What does Sygate have to do with the DHCP service not starting
> on a NT base O/S? Unless you went to the DHCP service and
> disabled the service, then most likely DHCP service is running
> on the machine.

I am not very familiar with networks and firewalls. Guess my hunche
was wrong.

> It doesn't appear that the machine doesn't have an invalid
> TCP/IP connection to the Internet, based on your statement that
> inbound UDP packets are being blocked by Sygate from 10.82.32.1.

What I did was key in the "IP address" value and "default gateway"
values by hand into the TCP/IP properties window for my LAN adaptor.

For some reason, DHCP service will not run on my XP system even if I
try to start it manually. It says "Error 1068: The dependency
service or group failed to start".

In the dependencies tab I can see this tree structure:

--------START-----------
AFD Networking Support Environment

NetBT
   SYMTDI
      TCP/IP Protocol Driver
         IPSEC Driver
   TCP/IP Protocol Driver
      IPSEC Driver

SYMTDI
   TCP/IP Protocol Driver
      IPSEC Driver

TCP/IP Protocol Driver
   IPSEC Driver
----------END-------------

I assume that DHCP needs to be running to get my system working
properly again for when the IP address next gets changes by the
network.

In actual fact, even after keying the IP addresses by hand and
rebooting it didn't work. I then ran the Network Setup Wizard in
Network Connections and this seemed to get something to work.

 

> I don't know what your problem is, but it has nothing to do with
> the DHCP service and Sygate.
>
> If Sysgate is blocking the UDP packets, then it's doing its job
> in stopping unsolicted inbound traffic to the machine.
>
> You can use the link to determine who the IP belongs to.
> http://www.arin.net/
>
> You'll see that it belongs to this.
> http://en.wikipedia.org/wiki/IANA

Sounds like it is to do with DHCP? Or not? Hey, I'm getting lost.
Any further info would be appreciated.

Relevant Pages

  • Re: Sygate blocking DHCP from starting
    ... >> I a running Sygate Personal Firewall Pro version 5.0 on WinXP ... I cannot connect to the network. ... then most likely DHCP service is running ... TCP/IP Protocol Driver ...
    (comp.security.misc)
  • Re: Sygate blocking DHCP from starting
    ... >> I a running Sygate Personal Firewall Pro version 5.0 on WinXP ... I cannot connect to the network. ... then most likely DHCP service is running ... TCP/IP Protocol Driver ...
    (alt.computer.security)
  • Re: Sygate blocking DHCP from starting
    ... >> What does Sygate have to do with the DHCP service not starting ... >> inbound UDP packets are being blocked by Sygate from 10.82.32.1. ... > TCP/IP Protocol Driver ... I then ran the Network Setup Wizard in ...
    (comp.security.firewalls)
  • Re: Sygate blocking DHCP from starting
    ... >> What does Sygate have to do with the DHCP service not starting ... >> inbound UDP packets are being blocked by Sygate from 10.82.32.1. ... > TCP/IP Protocol Driver ... I then ran the Network Setup Wizard in ...
    (alt.computer.security)
  • Re: Sygate blocking DHCP from starting
    ... >> What does Sygate have to do with the DHCP service not starting ... >> inbound UDP packets are being blocked by Sygate from 10.82.32.1. ... > TCP/IP Protocol Driver ... I then ran the Network Setup Wizard in ...
    (comp.security.misc)
Quantcast