bvmittal
asked on
IP Conflict Message
Dear Sir,
We have a LAN of around 100 Desktop Windows Client and some Linux , Unix , Windows Servers . Yesterday all of sudden we got message of their respective IP getting Conflict at all our Computers . We tried to identify the problem but could not find anything . But surprisingly after 15 minutes the problem got over itself and no IP conflict message was there .
Sir , kindly guide me about the cause of this problem . Is it due to some Virus or any thing else . Also pl guide me that in future how to protect against such problems .
Rgds
B Mittal
We have a LAN of around 100 Desktop Windows Client and some Linux , Unix , Windows Servers . Yesterday all of sudden we got message of their respective IP getting Conflict at all our Computers . We tried to identify the problem but could not find anything . But surprisingly after 15 minutes the problem got over itself and no IP conflict message was there .
Sir , kindly guide me about the cause of this problem . Is it due to some Virus or any thing else . Also pl guide me that in future how to protect against such problems .
Rgds
B Mittal
r_naren22atyahoo
How many Workstations had this problem????
Hi,
Its look like your network have conflict with anther network same class same subnet
Do you have VLAN?
And did you check what the error msg in event viewer?
Also check from DHCP if you have it, who have conflict with who?
I don’t thing so this is virus unless new virus around
regards
Its look like your network have conflict with anther network same class same subnet
Do you have VLAN?
And did you check what the error msg in event viewer?
Also check from DHCP if you have it, who have conflict with who?
I don’t thing so this is virus unless new virus around
regards
What subnet range are you currently useing?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Other reasons I've seen (rare) that aren't rogue/issues are:
- A buggy DHCP server assigning an IP more than once... either because it's buggy, or it doesn't manage the lease properly.
- I've also had people diagnose their own problems by temporarily assigning themself a static IP in a dynamic environment... another problem.
- If a computer goes switches network connections and/or into/out of standby/hibernate, sometimes it keeps its own IP and it won't work... some users are good and go to hit REPAIR (release/renew) which fixed the conflict
I've used the "net send" command to alert conflicts before to find out what's going on.
- A buggy DHCP server assigning an IP more than once... either because it's buggy, or it doesn't manage the lease properly.
- I've also had people diagnose their own problems by temporarily assigning themself a static IP in a dynamic environment... another problem.
- If a computer goes switches network connections and/or into/out of standby/hibernate, sometimes it keeps its own IP and it won't work... some users are good and go to hit REPAIR (release/renew) which fixed the conflict
I've used the "net send" command to alert conflicts before to find out what's going on.
>- A buggy DHCP server assigning an IP more than once... either because it's buggy, or it doesn't manage the lease properly
When duplicating advice previously posted, it is polite to say "As The--Captain says" or maybe "I agree with The--Captain".
>- I've also had people diagnose their own problems by temporarily assigning themself a static IP in a dynamic
>environment... another problem.
Not the case here, unless some idiot is assigning every IP in the entire subnet to themselves by hand (an impossible task in 15 minutes).
>- If a computer goes switches network connections and/or into/out of standby/hibernate, sometimes it keeps its own IP and
>it won't work... some users are good and go to hit REPAIR (release/renew) which fixed the conflict
Also not the case here, since this would annoy a few machines at best, not every machine on the segment.
>I've used the "net send" command to alert conflicts before to find out what's going on
Yikes! You haven't disabled that service yet?!?!
Cheers,
-Jon
When duplicating advice previously posted, it is polite to say "As The--Captain says" or maybe "I agree with The--Captain".
>- I've also had people diagnose their own problems by temporarily assigning themself a static IP in a dynamic
>environment... another problem.
Not the case here, unless some idiot is assigning every IP in the entire subnet to themselves by hand (an impossible task in 15 minutes).
>- If a computer goes switches network connections and/or into/out of standby/hibernate, sometimes it keeps its own IP and
>it won't work... some users are good and go to hit REPAIR (release/renew) which fixed the conflict
Also not the case here, since this would annoy a few machines at best, not every machine on the segment.
>I've used the "net send" command to alert conflicts before to find out what's going on
Yikes! You haven't disabled that service yet?!?!
Cheers,
-Jon
Jon/TheCaptain - thanks for your reply! What you say is true, but was something slightly different than what I was getting at. A buggy DHCP server does not have to be a rogue server, which is the difference I was after. I did miss "ALL COMPUTERS" so you're correct in saying that a manually-assigned IP is not the case here. The net send service is useful in certain private-network situations. I don't think there is anything wrong with either of our replies, except for the one piece of information I missed, and thanks for pointing that out! :)
I object - Okigire has merely (if unwittingly) duplicated my advice. He says:
>A buggy DHCP server does not have to be a rogue server, which is the difference I was after
"Rogue" may not imply "buggy", but "haywire" certainly does, and I used both terms.
Cheers,
-Jon
>A buggy DHCP server does not have to be a rogue server, which is the difference I was after
"Rogue" may not imply "buggy", but "haywire" certainly does, and I used both terms.
Cheers,
-Jon