Network manager is messing up my dns settings

I have 11.1 (64bits) with KD4.1 installed.
Everything was working just fine but recently i started having the following problem:

The eth0 interface seems to get the DNS configuration all messed up after a few seconds on network startup. As soon as i restart the network it works ok for a few seconds, then i just stop to have access to any IPs. It seems to me that the DNS is getting messed up. Also, it seems that without me doing anything it has an intermittent behavior because all of the sudden it starts working, and then again it stops.

Also, the wireless interface isn’t suffering from this problem.
I started getting this after i installed virtualbox_ose from the repos but it might be a coincidence.

Bellow is the log from NetworkManager when i restart the network.
Thanks in advance.

Jan 6 11:42:34 xplaptop028 NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) scheduled…
Jan 6 11:42:34 xplaptop028 NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) complete.
Jan 6 11:42:34 xplaptop028 NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) starting…
Jan 6 11:42:34 xplaptop028 NetworkManager: <info> (eth0): device state change: 4 → 5
Jan 6 11:42:34 xplaptop028 NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) successful.
Jan 6 11:42:34 xplaptop028 NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled.
Jan 6 11:42:34 xplaptop028 NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) complete.
Jan 6 11:42:34 xplaptop028 NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) started…
Jan 6 11:42:34 xplaptop028 NetworkManager: <info> (eth0): device state change: 5 → 7
Jan 6 11:42:34 xplaptop028 NetworkManager: <info> Activation (eth0) Beginning DHCP transaction.
Jan 6 11:42:34 xplaptop028 NetworkManager: <info> dhclient started with pid 1982
Jan 6 11:42:34 xplaptop028 NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) complete.
Jan 6 11:42:34 xplaptop028 NetworkManager: <info> DHCP: device eth0 state changed (null) → preinit
Jan 6 11:42:43 xplaptop028 NetworkManager: <info> DHCP: device eth0 state changed preinit → bound
Jan 6 11:42:43 xplaptop028 NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP Configure Get) scheduled…
Jan 6 11:42:43 xplaptop028 NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP Configure Get) started…
Jan 6 11:42:43 xplaptop028 NetworkManager: <info> address 192.168.20.58
Jan 6 11:42:43 xplaptop028 NetworkManager: <info> prefix 24 (255.255.255.0)
Jan 6 11:42:43 xplaptop028 NetworkManager: <info> gateway 192.168.20.1
Jan 6 11:42:43 xplaptop028 NetworkManager: <info> nameserver ‘10.10.10.70’
Jan 6 11:42:43 xplaptop028 NetworkManager: <info> nameserver ‘10.10.100.29’
Jan 6 11:42:43 xplaptop028 NetworkManager: <info> nameserver ‘10.10.100.30’
Jan 6 11:42:43 xplaptop028 NetworkManager: <info> domain name ‘inet’
Jan 6 11:42:43 xplaptop028 NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) scheduled…
Jan 6 11:42:43 xplaptop028 NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP Configure Get) complete.
Jan 6 11:42:43 xplaptop028 NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) started…
Jan 6 11:42:44 xplaptop028 NetworkManager: <debug> [1231242164.021174] run_netconfig(): Spawning ‘/sbin/netconfig modify --service NetworkManager’
Jan 6 11:42:44 xplaptop028 NetworkManager: <debug> [1231242164.037283] write_to_netconfig(): Writing to netconfig: INTERFACE=‘eth0’
Jan 6 11:42:44 xplaptop028 NetworkManager: <debug> [1231242164.037413] write_to_netconfig(): Writing to netconfig: DNSSEARCH=‘inet inet’
Jan 6 11:42:44 xplaptop028 NetworkManager: <debug> [1231242164.037455] write_to_netconfig(): Writing to netconfig: DNSSERVERS=‘10.10.10.70 10.10.100.29 10.10.100.30’
Jan 6 11:42:44 xplaptop028 NetworkManager: <info> Clearing nscd hosts cache.
Jan 6 11:42:44 xplaptop028 NetworkManager: <info> (eth0): device state change: 7 → 8
Jan 6 11:42:44 xplaptop028 NetworkManager: <debug> [1231242164.050485] run_netconfig(): Spawning ‘/sbin/netconfig modify --service NetworkManager’
Jan 6 11:42:44 xplaptop028 NetworkManager: <debug> [1231242164.074406] write_to_netconfig(): Writing to netconfig: INTERFACE=‘eth0’
Jan 6 11:42:44 xplaptop028 NetworkManager: <debug> [1231242164.074521] write_to_netconfig(): Writing to netconfig: DNSSEARCH=‘inet inet’
Jan 6 11:42:44 xplaptop028 NetworkManager: <debug> [1231242164.074560] write_to_netconfig(): Writing to netconfig: DNSSERVERS=‘10.10.10.70 10.10.100.29 10.10.100.30’
Jan 6 11:42:44 xplaptop028 NetworkManager: <info> Clearing nscd hosts cache.
Jan 6 11:42:44 xplaptop028 NetworkManager: <info> Policy set ‘System eth0’ (eth0) as default for routing and DNS.
Jan 6 11:42:44 xplaptop028 NetworkManager: <info> Activation (eth0) successful, device activated.
Jan 6 11:42:44 xplaptop028 NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) complete.
Jan 6 11:42:48 xplaptop028 NetworkManager: <info> DHCP: device wlan0 state changed preinit → bound
Jan 6 11:42:48 xplaptop028 NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Get) scheduled…
Jan 6 11:42:48 xplaptop028 NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Get) started…
Jan 6 11:42:48 xplaptop028 NetworkManager: <info> address 10.0.10.103
Jan 6 11:42:48 xplaptop028 NetworkManager: <info> prefix 24 (255.255.255.0)
Jan 6 11:42:48 xplaptop028 NetworkManager: <info> gateway 10.0.10.1
Jan 6 11:42:48 xplaptop028 NetworkManager: <info> nameserver ‘212.18.160.133’
Jan 6 11:42:48 xplaptop028 NetworkManager: <info> nameserver ‘212.18.160.134’
Jan 6 11:42:48 xplaptop028 NetworkManager: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) scheduled…
Jan 6 11:42:48 xplaptop028 NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Get) complete.
Jan 6 11:42:48 xplaptop028 NetworkManager: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) started…
Jan 6 11:42:49 xplaptop028 NetworkManager: <debug> [1231242169.077727] run_netconfig(): Spawning ‘/sbin/netconfig modify --service NetworkManager’
Jan 6 11:42:49 xplaptop028 NetworkManager: <debug> [1231242169.080228] write_to_netconfig(): Writing to netconfig: INTERFACE=‘wlan0’
Jan 6 11:42:49 xplaptop028 NetworkManager: <debug> [1231242169.080316] write_to_netconfig(): Writing to netconfig: DNSSEARCH=‘inet inet’
Jan 6 11:42:49 xplaptop028 NetworkManager: <debug> [1231242169.080360] write_to_netconfig(): Writing to netconfig: DNSSERVERS=‘10.10.10.70 10.10.100.29 10.10.100.30 212.18.160.133 212.18.160.134’
Jan 6 11:42:49 xplaptop028 NetworkManager: <info> Clearing nscd hosts cache.
Jan 6 11:42:49 xplaptop028 NetworkManager: <debug> [1231242169.085619] run_netconfig(): Spawning ‘/sbin/netconfig modify --service NetworkManager’
Jan 6 11:42:49 xplaptop028 NetworkManager: <debug> [1231242169.111981] write_to_netconfig(): Writing to netconfig: INTERFACE=‘eth0’
Jan 6 11:42:49 xplaptop028 NetworkManager: <debug> [1231242169.112409] write_to_netconfig(): Writing to netconfig: DNSSEARCH=‘inet inet’
Jan 6 11:42:49 xplaptop028 NetworkManager: <debug> [1231242169.112465] write_to_netconfig(): Writing to netconfig: DNSSERVERS=‘10.10.10.70 10.10.100.29 10.10.100.30 212.18.160.133 212.18.160.134’
Jan 6 11:42:49 xplaptop028 NetworkManager: <info> Clearing nscd hosts cache.
Jan 6 11:42:49 xplaptop028 NetworkManager: <info> Policy set ‘System eth0’ (eth0) as default for routing and DNS.
Jan 6 11:42:49 xplaptop028 NetworkManager: <info> (wlan0): device state change: 7 → 8
Jan 6 11:42:49 xplaptop028 NetworkManager: <info> Activation (wlan0) successful, device activated.
Jan 6 11:42:49 xplaptop028 NetworkManager: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) complete.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Well, DNS isn’t interface-specific, but I assume you mean that DNS
doesn’t work properly when you are using your wired connection vs. your
wireless connection. You mentioned, however, that you “just stop to
have access to your IPs” which isn’t a problem with DNS. If you cannot
ping something that you know is on your network by IP address you have
another problem altogether. This must be tested separately as you may
have a problem that is not DNS-caused but looks like it. If you can
ping your gateway or router or anything else on your network by IP
address directly but not via DNA name then you have a DNS problem. The
same applies if you can ping Google by IP address (74.125.45.100 for
example) but not by name; however, if you cannot ping anything at all
except your own box then you have another problem altogether, probably
with subnet mask or default route. Post the output from the following
commands, please:

ip addr sh
ip route sh
cat /etc/resolv.conf
rcnetwork status
rcSuSEfirewall status

Good luck.

hpalma wrote:
> I have 11.1 (64bits) with KD4.1 installed.
> Everything was working just fine but recently i started having the
> following problem:
>
> The eth0 interface seems to get the DNS configuration all messed up
> after a few seconds on network startup. As soon as i restart the network
> it works ok for a few seconds, then i just stop to have access to any
> IPs. It seems to me that the DNS is getting messed up.
>
> Also, the wireless interface isn’t suffering from this problem.
> I started getting this after i installed virtualbox_ose from the repos
> but it might be a coincidence.
>
> Bellow is the log from NetworkManager when i restart the network.
> Thanks in advance.
>
> Jan 6 11:42:34 xplaptop028 NetworkManager: <info> Activation (eth0)
> Stage 2 of 5 (Device Configure) scheduled…
>
> Jan 6 11:42:34 xplaptop028 NetworkManager: <info> Activation (eth0)
> Stage 1 of 5 (Device Prepare) complete.
>
> Jan 6 11:42:34 xplaptop028 NetworkManager: <info> Activation (eth0)
> Stage 2 of 5 (Device Configure) starting…
>
> Jan 6 11:42:34 xplaptop028 NetworkManager: <info> (eth0): device
> state change: 4 → 5
>
> Jan 6 11:42:34 xplaptop028 NetworkManager: <info> Activation (eth0)
> Stage 2 of 5 (Device Configure) successful.
>
> Jan 6 11:42:34 xplaptop028 NetworkManager: <info> Activation (eth0)
> Stage 3 of 5 (IP Configure Start) scheduled.
>
> Jan 6 11:42:34 xplaptop028 NetworkManager: <info> Activation (eth0)
> Stage 2 of 5 (Device Configure) complete.
>
> Jan 6 11:42:34 xplaptop028 NetworkManager: <info> Activation (eth0)
> Stage 3 of 5 (IP Configure Start) started…
>
> Jan 6 11:42:34 xplaptop028 NetworkManager: <info> (eth0): device
> state change: 5 → 7
>
> Jan 6 11:42:34 xplaptop028 NetworkManager: <info> Activation (eth0)
> Beginning DHCP transaction.
>
> Jan 6 11:42:34 xplaptop028 NetworkManager: <info> dhclient started
> with pid 1982
>
> Jan 6 11:42:34 xplaptop028 NetworkManager: <info> Activation (eth0)
> Stage 3 of 5 (IP Configure Start) complete.
>
> Jan 6 11:42:34 xplaptop028 NetworkManager: <info> DHCP: device eth0
> state changed (null) → preinit
>
> Jan 6 11:42:43 xplaptop028 NetworkManager: <info> DHCP: device eth0
> state changed preinit → bound
>
> Jan 6 11:42:43 xplaptop028 NetworkManager: <info> Activation (eth0)
> Stage 4 of 5 (IP Configure Get) scheduled…
>
> Jan 6 11:42:43 xplaptop028 NetworkManager: <info> Activation (eth0)
> Stage 4 of 5 (IP Configure Get) started…
>
> Jan 6 11:42:43 xplaptop028 NetworkManager: <info> address
> 192.168.20.58
>
> Jan 6 11:42:43 xplaptop028 NetworkManager: <info> prefix 24
> (255.255.255.0)
>
> Jan 6 11:42:43 xplaptop028 NetworkManager: <info> gateway
> 192.168.20.1
>
> Jan 6 11:42:43 xplaptop028 NetworkManager: <info> nameserver
> ‘10.10.10.70’
>
> Jan 6 11:42:43 xplaptop028 NetworkManager: <info> nameserver
> ‘10.10.100.29’
>
> Jan 6 11:42:43 xplaptop028 NetworkManager: <info> nameserver
> ‘10.10.100.30’
>
> Jan 6 11:42:43 xplaptop028 NetworkManager: <info> domain name
> ‘inet’
>
> Jan 6 11:42:43 xplaptop028 NetworkManager: <info> Activation (eth0)
> Stage 5 of 5 (IP Configure Commit) scheduled…
>
> Jan 6 11:42:43 xplaptop028 NetworkManager: <info> Activation (eth0)
> Stage 4 of 5 (IP Configure Get) complete.
>
> Jan 6 11:42:43 xplaptop028 NetworkManager: <info> Activation (eth0)
> Stage 5 of 5 (IP Configure Commit) started…
>
> Jan 6 11:42:44 xplaptop028 NetworkManager: <debug> [1231242164.021174]
> run_netconfig(): Spawning ‘/sbin/netconfig modify --service
> NetworkManager’
> Jan 6 11:42:44 xplaptop028 NetworkManager: <debug> [1231242164.037283]
> write_to_netconfig(): Writing to netconfig: INTERFACE=‘eth0’
>
> Jan 6 11:42:44 xplaptop028 NetworkManager: <debug> [1231242164.037413]
> write_to_netconfig(): Writing to netconfig: DNSSEARCH=‘inet inet’
>
> Jan 6 11:42:44 xplaptop028 NetworkManager: <debug> [1231242164.037455]
> write_to_netconfig(): Writing to netconfig: DNSSERVERS=‘10.10.10.70
> 10.10.100.29 10.10.100.30’
> Jan 6 11:42:44 xplaptop028 NetworkManager: <info> Clearing nscd hosts
> cache.
> Jan 6 11:42:44 xplaptop028 NetworkManager: <info> (eth0): device
> state change: 7 → 8
> Jan 6 11:42:44 xplaptop028 NetworkManager: <debug> [1231242164.050485]
> run_netconfig(): Spawning ‘/sbin/netconfig modify --service
> NetworkManager’
> Jan 6 11:42:44 xplaptop028 NetworkManager: <debug> [1231242164.074406]
> write_to_netconfig(): Writing to netconfig: INTERFACE=‘eth0’
> Jan 6 11:42:44 xplaptop028 NetworkManager: <debug> [1231242164.074521]
> write_to_netconfig(): Writing to netconfig: DNSSEARCH=‘inet inet’
> Jan 6 11:42:44 xplaptop028 NetworkManager: <debug> [1231242164.074560]
> write_to_netconfig(): Writing to netconfig: DNSSERVERS=‘10.10.10.70
> 10.10.100.29 10.10.100.30’
> Jan 6 11:42:44 xplaptop028 NetworkManager: <info> Clearing nscd hosts
> cache.
> Jan 6 11:42:44 xplaptop028 NetworkManager: <info> Policy set ‘System
> eth0’ (eth0) as default for routing and DNS.
> Jan 6 11:42:44 xplaptop028 NetworkManager: <info> Activation (eth0)
> successful, device activated.
> Jan 6 11:42:44 xplaptop028 NetworkManager: <info> Activation (eth0)
> Stage 5 of 5 (IP Configure Commit) complete.
> Jan 6 11:42:48 xplaptop028 NetworkManager: <info> DHCP: device wlan0
> state changed preinit → bound
> Jan 6 11:42:48 xplaptop028 NetworkManager: <info> Activation (wlan0)
> Stage 4 of 5 (IP Configure Get) scheduled…
> Jan 6 11:42:48 xplaptop028 NetworkManager: <info> Activation (wlan0)
> Stage 4 of 5 (IP Configure Get) started…
> Jan 6 11:42:48 xplaptop028 NetworkManager: <info> address
> 10.0.10.103
> Jan 6 11:42:48 xplaptop028 NetworkManager: <info> prefix 24
> (255.255.255.0)
> Jan 6 11:42:48 xplaptop028 NetworkManager: <info> gateway
> 10.0.10.1
> Jan 6 11:42:48 xplaptop028 NetworkManager: <info> nameserver
> ‘212.18.160.133’
> Jan 6 11:42:48 xplaptop028 NetworkManager: <info> nameserver
> ‘212.18.160.134’
> Jan 6 11:42:48 xplaptop028 NetworkManager: <info> Activation (wlan0)
> Stage 5 of 5 (IP Configure Commit) scheduled…
> Jan 6 11:42:48 xplaptop028 NetworkManager: <info> Activation (wlan0)
> Stage 4 of 5 (IP Configure Get) complete.
> Jan 6 11:42:48 xplaptop028 NetworkManager: <info> Activation (wlan0)
> Stage 5 of 5 (IP Configure Commit) started…
> Jan 6 11:42:49 xplaptop028 NetworkManager: <debug> [1231242169.077727]
> run_netconfig(): Spawning ‘/sbin/netconfig modify --service
> NetworkManager’
> Jan 6 11:42:49 xplaptop028 NetworkManager: <debug> [1231242169.080228]
> write_to_netconfig(): Writing to netconfig: INTERFACE=‘wlan0’
> Jan 6 11:42:49 xplaptop028 NetworkManager: <debug> [1231242169.080316]
> write_to_netconfig(): Writing to netconfig: DNSSEARCH=‘inet inet’
> Jan 6 11:42:49 xplaptop028 NetworkManager: <debug> [1231242169.080360]
> write_to_netconfig(): Writing to netconfig: DNSSERVERS=‘10.10.10.70
> 10.10.100.29 10.10.100.30 212.18.160.133 212.18.160.134’
> Jan 6 11:42:49 xplaptop028 NetworkManager: <info> Clearing nscd hosts
> cache.
> Jan 6 11:42:49 xplaptop028 NetworkManager: <debug> [1231242169.085619]
> run_netconfig(): Spawning ‘/sbin/netconfig modify --service
> NetworkManager’
> Jan 6 11:42:49 xplaptop028 NetworkManager: <debug> [1231242169.111981]
> write_to_netconfig(): Writing to netconfig: INTERFACE=‘eth0’
> Jan 6 11:42:49 xplaptop028 NetworkManager: <debug> [1231242169.112409]
> write_to_netconfig(): Writing to netconfig: DNSSEARCH=‘inet inet’
> Jan 6 11:42:49 xplaptop028 NetworkManager: <debug> [1231242169.112465]
> write_to_netconfig(): Writing to netconfig: DNSSERVERS=‘10.10.10.70
> 10.10.100.29 10.10.100.30 212.18.160.133 212.18.160.134’
> Jan 6 11:42:49 xplaptop028 NetworkManager: <info> Clearing nscd hosts
> cache.
> Jan 6 11:42:49 xplaptop028 NetworkManager: <info> Policy set ‘System
> eth0’ (eth0) as default for routing and DNS.
> Jan 6 11:42:49 xplaptop028 NetworkManager: <info> (wlan0): device
> state change: 7 → 8
> Jan 6 11:42:49 xplaptop028 NetworkManager: <info> Activation (wlan0)
> successful, device activated.
> Jan 6 11:42:49 xplaptop028 NetworkManager: <info> Activation (wlan0)
> Stage 5 of 5 (IP Configure Commit) complete.
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJY2EB3s42bA80+9kRAktLAJoDEMoFnEXGu4HbkTLP2QVAGdYN8ACfTx+Y
kLiryvylKVMvIashroxckIE=
=QLBS
-----END PGP SIGNATURE-----

Thanks for the reply. You’re right, i can’t even ping machines on the same network using the ip so it can’t be a DNS problem. What puzzles me even more is the fact that that without doing nothing i sometimes have access to the network and sometimes i can’t. It changes in minutes.
Bellow is the information u asked for. Really appreciate some help. Thanks

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 brd 127.255.255.255 scope host lo
inet 127.0.0.2/8 brd 127.255.255.255 scope host secondary lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether 00:1a:80:a4:1d:36 brd ff:ff:ff:ff:ff:ff
inet 192.168.20.58/24 brd 192.168.20.255 scope global eth0
inet6 fe80::21a:80ff:fea4:1d36/64 scope link
valid_lft forever preferred_lft forever
3: wmaster0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000
link/ieee802.11 00:1f:3b:14:c6:d5 brd ff:ff:ff:ff:ff:ff
4: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN qlen 1000
link/ether 00:1f:3b:14:c6:d5 brd ff:ff:ff:ff:ff:ff
5: vmnet1: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast state DOWN qlen 1000
link/ether 00:50:56:c0:00:01 brd ff:ff:ff:ff:ff:ff
6: vmnet8: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast state DOWN qlen 1000
link/ether 00:50:56:c0:00:08 brd ff:ff:ff:ff:ff:ff

192.168.20.0/24 dev eth0 proto kernel scope link src 192.168.20.58 metric 1
127.0.0.0/8 dev lo scope link
default via 192.168.20.1 dev eth0 proto static

search inet
nameserver 10.10.10.70
nameserver 10.10.100.29
nameserver 10.10.100.30

Checking for the NetworkManager: running

  1. Couldn’t find the rcSuSEfirewall command. But i have turned off the firewall if that’s what u wanted to know.

An update,

it seems that this problem is specific to a network. When i got home and connected to my home network everything just worked fine. This only happens at my work place.

Also, the problem occurs less when accessing IPs in the same network, although it does happen.
For example, my IP is 192.168.20.58.
When accessing an IP like 192.168.20.70 this problem occurs less often, but if i access 192.168.30.28 i loose connectivity much more often.

Well, awnsering my own question and after 2 days of fighting this
problem some guy just came to my pc and solved it in two seconds.
It seems that someone here decided to use a fixed IP and chose the IP
that the dhcp was always assigning to my mac address. So, it was
simply an IP conflict.

Still, shouldn’t a nice popup show up indicating this error ? That
would have saved my two days of problems.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

While it’s possible to detect issues like duplicate IPs at times there
is no guarantee that any single box can see that. For example if you
get on a network, request a DHCP address, and take that address your box
doesn’t know about any other boxes on the network that may be using that
address. In a switched environment there is no reason for anybody
except your box, the other box, and the switch to know that you have
that address. The switch will send packets to whomever it desires and
that’s a switch configuration issue at best. The other box could
potentially see the DHCP request depending on your network settings but
whether or not it reported the error doesn’t help you one bit. That the
other person assigned a static IP that was available via DHCP was the
heart of the problem… that should never be done. They could have
saved everybody, including themselves, time and effort by using DHCP
themselves (it’s the default for every client OS after all… just “plug
in” and go).

If every box on a network received traffic from every other box on the
network we’d all be using hubs, or have our networks setup very poorly,
and things wouldn’t work. In any case this is the joy of TCP/IP…
works well, until humans interfere (the other guy in your case). :slight_smile:

Good luck.

hpalma wrote:
> Well, awnsering my own question and after 2 days of fighting this
> problem some guy just came to my pc and solved it in two seconds.
> It seems that someone here decided to use a fixed IP and chose the IP
> that the dhcp was always assigning to my mac address. So, it was
> simply an IP conflict.
>
> Still, shouldn’t a nice popup show up indicating this error ? That
> would have saved my two days of problems.
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJZLoQ3s42bA80+9kRAvzEAJ9nJsPjkNWXXegJNl8rWH3NQpsSfgCfQsVO
CoxYLUPRcbBxczA4UI5DGLA=
=GQp1
-----END PGP SIGNATURE-----