Welcome, Guest. Please login or register.
October 07, 2008, 08:55:28 AM

Login with username, password and session length

197817 Posts
22768 Topics
54720 Members

Latest Member: Cache22

Search:     Advanced search | Tag Cloud
+  Welcome to the Comodo Forum
|-+  Desktop Security Products
| |-+  Comodo Firewall
| | |-+  Frequently Asked Questions (FAQ) for Comodo firewall
| | | |-+  Problems with acquiring or renewing the IP address
« previous next »
Pages: 1 ... 10 11 [12] 13 Go Down Print
Author Topic: Problems with acquiring or renewing the IP address  (Read 48631 times)
jjb3
Newbie
*
Offline Offline

Posts: 10


« Reply #165 on: October 25, 2007, 04:45:02 AM »

Thanks for the reply. The steeings that you gave me where already applied (post a few pages back has the same advise). 99% it works  Grin, Thanks. Sometimes it will still block some parts of the connection, windows will say "Limited network connection", but I dont have a good log with that.

Btw Logs show that the Application monitor gives severity High on svchost.exe  (UPD OUT 239.255.255.250:1900 / UDP IN 130.115.78.140:123), does that give problems?

jjb3
Logged
alaindc
Newbie
*
Offline Offline

Posts: 3


« Reply #166 on: October 31, 2007, 03:50:23 PM »

hi  Tongue
i discover suddenly comodo firewal a few weeks ago, and i'm glad i have.

the same problem with version 2.4.18.184 fr begin to happen, on XP SP2.
every 6 hours or so, sometime much less, i was having this disconnecting problem, unable to renew my ip adress, on my ADSL modem.

at first, i follow the instruction, add these 2 rules, but it wasn't working.
so, i can confirm one thing, it really need a reboot to work.
thank's for helping.

the first week i use CFP, i also find the solution to connect my 360 through my pc, and allow the connection via CFP, on the same forum.
the forum are great, the firewall is great...



Given the potentially cranky nature of DHCP, you may find it helpful to add two more rules to the very top of Network Monitor (these will be done manually), in this fashion:

Right-click Rule ID 0, and select Add/Add Before.  Build the rule like this:

Action:  Allow
Protocol:  UDP
Direction:  In
Source IP:  Any
Destination IP:  Any
Source Port:  67
Destination Port:  68

Repeat the step in blue above, and build the next rule like this:
Action:  Allow
Protocol:  UDP
Direction:  Out
Source IP:  Any
Destination IP:  Any
Source Port:  68
Destination Port:  67

Now reboot, just to clear any temporary memory and make sure the new rules are properly set.

That should resolve the DHCP issue for you.

LM

Logged
allkatraz
Newbie
*
Offline Offline

Posts: 2


« Reply #167 on: November 08, 2007, 03:51:48 AM »

Welcome to the forums, alkatraz; sorry you're in the "club."
[...]
That should resolve the DHCP issue for you.

Sorry for the delay, i was very busy. In all this time i just deactivated Comodo Smiley. Today i found some extra time and i followed you advices. And... it works! Thanks for your patience. I saved your post for the future (windows reinstalls) Smiley

Thanks again.
Logged
Little Mac
Global Moderator
Comodo's Hero
*****
Offline Offline

Posts: 6017



« Reply #168 on: November 08, 2007, 03:23:06 PM »

No problem, allkatraz; glad that worked for you!

LM
Logged

date
dcfldd split=2G conv=noerror hashwindow=0 hash=md5 bs=32768 hashlog=/mnt/sda1/images/hash.log if=/dev/hda of=/mnt/sda1/images/LM.dd
date
cat LM.dd.* | md5sum > verify.log
date
enphreaked
Newbie
*
Offline Offline

Posts: 1


« Reply #169 on: November 22, 2007, 11:33:30 AM »

First of all I want to say how happy and grateful I am to have found such a smart, flexible and smooth Firewall like Comodo.

Unfortunately I'm a bearer of the DHCP-problem plague..

I use no router, only a modem (that let's the traffic go right through). So it's my computer that aquires the IP-adress.

I've tried adding my gateway to trusted zones/places.

I've also tried the allow UDP in/out to my gateway, but that didn't help either..

When I try to aquire an IP-adress I get spammed with "Inbound Policy Violation (Access denied IP: xx.xxx.xx.xxx, Port=31486

Also this is added: Application access denied: svchost.exe:xx.xxx.xxx.xx :dhcp(68)
                              Application access denied: svchost.exe:xx.xxx.xxx.xx :bootp(67)



Any suggestions?

EDIT: Also I'd like to add that I lose my ip-adress at random intervals. Sometimes I can surf for hours, sometimes just 30 min. I cannot aquire an IP-adress when comodo is activated. When I disable it though I can aquire an IP-adress.
« Last Edit: November 22, 2007, 11:38:09 AM by enphreaked » Logged
xerovlade
Newbie
*
Offline Offline

Posts: 1


« Reply #170 on: November 22, 2007, 01:12:43 PM »

Same Thing Happens to me.. And i was thinking that i was supposed to write all of these stuff but i guess someone beat me to it.. Anyway whatever enphreaked said is what is happening to me too..

And i was contemplating on upgrading firewall a while ago.. Anyway Thanks in Advance..


******************************************************************

Anyway, I already figured out how to fix my DHCP with the current Comodo Version so Thanks anyways.. Viva Comodo
« Last Edit: November 26, 2007, 03:21:24 PM by xerovlade » Logged
notsavant
Newbie
*
Offline Offline

Posts: 5


« Reply #171 on: November 24, 2007, 08:38:54 PM »

I'm still having the same problem; I upgraded to v3, but went back, after a small while, to v2.
Now, my connection just drops from time to time, forcing me to renew my IP (cmd or control panel). After that, it works fine.. for a while. I tried adding the rules and disabling "Do protocol analysis" - to no avail.
I had a fine connection before.. "downgrading" (I used v2 for about 4 months), still, I remember having this problem when I switched from Outpost and, somehow, solving it.
Any ideas? Got the rules wrong perhaps? ;X
Logged
Little Mac
Global Moderator
Comodo's Hero
*****
Offline Offline

Posts: 6017



« Reply #172 on: November 24, 2007, 09:19:20 PM »

notsavant,

There are two things I'd target first:

1.  Make sure you are not blocking svchost.exe (application monitor) in any way; this system process is needed to establish the DHCP lease (which is what gets you the IP address).

2.  In network monitor, make sure you maintain the default rule to Allow TCP/UDP Out from Any to Any, as the rule in top position (Rule ID 0).  Then create a new NetMon rule as Rule ID 1 (2nd position from the top) to:

Action:  Allow
Protocol:  UDP
Direction:  In
Source IP:  Any
Destination IP:  Any
Source Port:  67
Destination Port:  68

There are a couple things you can do to "tighten" that up. 

1.  If you're behind a router, configure you computer to have a static IP address (this is an internal/network/LAN address and won't impact your contact to the outside world); you do this in Windows, Network Connection settings.  This eliminates the need for DHCP and the extra rule I listed above.

2.  If you still want to do (or need to) dynamic DHCP, but you know that your DHCP server's IP address won't be changing, you can define it as the Source IP in the rule I gave above.  Then add a new rule into the top position (a new Rule ID 0) ***Note:  Do not delete the default Allow TCP/UDP Out rule, as it allows you to surf and get email, etc.  Just add an additional rule on top of it.***  The new rule will be:

Action:  Allow
Protocol:  UDP
Direction:  Out
Source IP:  Any
Destination IP:  (IP of your DHCP server)
Source Port:  68
Destination Port:  67

That should clear up any issues.  If after creating the rules you're still having trouble, reboot.  If still no joy, we'll have to look at your firewall logs to see what's being blocked.

Hope that helps,

LM
Logged

date
dcfldd split=2G conv=noerror hashwindow=0 hash=md5 bs=32768 hashlog=/mnt/sda1/images/hash.log if=/dev/hda of=/mnt/sda1/images/LM.dd
date
cat LM.dd.* | md5sum > verify.log
date
notsavant
Newbie
*
Offline Offline

Posts: 5


« Reply #173 on: November 25, 2007, 08:00:56 PM »

I took a while before replying in order to test the changes. So far it's fine; 19 hours without breaks. It seems that the problem was a wrong rule ;X
Thanks for the help "Little Mac". I appreciate it.
Logged
Little Mac
Global Moderator
Comodo's Hero
*****
Offline Offline

Posts: 6017



« Reply #174 on: November 26, 2007, 10:33:30 PM »

No problem, notsavant ~  glad to help!

LM
Logged

date
dcfldd split=2G conv=noerror hashwindow=0 hash=md5 bs=32768 hashlog=/mnt/sda1/images/hash.log if=/dev/hda of=/mnt/sda1/images/LM.dd
date
cat LM.dd.* | md5sum > verify.log
date
paper_ball
Newbie
*
Offline Offline

Posts: 1


« Reply #175 on: February 17, 2008, 10:47:31 AM »

I need help. How do I start a ticket...this is ALL WAY over my head. Just fix it. so I can get online and not have to turn off the firewall...that is the only way it works...I can get to this site...
Logged
panic
Global Moderator
Comodo's Hero
*****
Offline Offline

Posts: 5451


... and I say to myself, "What a wonderful world"


« Reply #176 on: February 17, 2008, 03:52:19 PM »

To lodge a ticket with the official Support Centre (which is what I'm hoping you mean), you need tog oto http://support.comodo.com, log in andfrom there, it's pretty obvious what to do.

Please note, that your username and password for these forums will not work on the support centre. You will need to register separately before you can lodge a support ticket.

Cheers,
Ewen :-)
Logged

As your mums would say, "If you can't play nice with all the other kiddies, go home".
All users are asked to please read and abide by the  Comodo Forum Policy.
If you don't like it, don't use the forum.
fake__n
Newbie
*
Offline Offline

Posts: 1


« Reply #177 on: March 08, 2008, 08:59:21 AM »

I may of fixed my problem, as I had the problem obtaining IP addy to my network upon reboot or from standby.
Kept asking for new network name with my adapter name already in use and wanted me to rename...now this is a problem every time I boot or log in.  Had to disable CF to obtain IP to network and Internet and then turn it back on each time.

This is what I did and see if it works for others with this problem.  Go to Firewall | MY Network Zones | and in your NIC adaptor addy line (IP IN 192.168.x.x), edit this/check "A range of IP Addresses" and enter your Router's full range...ie, (192.168.0.1 - 192.168.255.255) APPLY and exit as prompted.
This seems to be working for me, maybe opened up a bit much, but that is the way ZA did it.
Logged
brucine
Comodo Family Member
***
Offline Offline

Posts: 92


« Reply #178 on: March 08, 2008, 05:24:42 PM »

That is also the way i do it (including localhost at 127.0.0.1, Firefox keeps asking for it)
Logged
Little Mac
Global Moderator
Comodo's Hero
*****
Offline Offline

Posts: 6017



« Reply #179 on: March 08, 2008, 08:46:52 PM »

That is also the way i do it (including localhost at 127.0.0.1, Firefox keeps asking for it)
You shouldn't have to create a zone for localhost, just Allow w/Remember for Firefox.  Or, go into FF's rule in Defense+, Access Rights, and check the box to Allow on loopback connection. 

Firefox does utilize loopback connection, and it's nothing to worry about.  Some applications do, but there's no need to create a zone to allow it; just do it on a per-application basis.  Just IMO.

LM
Logged

date
dcfldd split=2G conv=noerror hashwindow=0 hash=md5 bs=32768 hashlog=/mnt/sda1/images/hash.log if=/dev/hda of=/mnt/sda1/images/LM.dd
date
cat LM.dd.* | md5sum > verify.log
date
Tags:
Pages: 1 ... 10 11 [12] 13 Go Up Print 
« previous next »
Jump to:  

SSL Firewall
Page created in -0 seconds with 20 queries.
Powered by SMF 1.1.5 | SMF © 2006, Simple Machines LLC
Seo4Smf v0.2 © Webmaster's Talks
Design by 7dana.com