  Kalford Seems To Be An Rtfm Problem. Premium,MVM join:2001-03-20 Ontario
·Rogers Hi-Speed
| IP conflicts when new server plugged into Network.
Hi Folks,
I just started staging a new server yesterday and I've got a weird one. (at least to me it is).
The box is running server 2003 and has dual network cards in it. Both cards are set up with static IP's and are properly assigned those IPs when I plug into the network.
The problem I am having is that while I can connect no problem to the box, every time I plug it into the network I am also getting IP conflicts on my network with 2 other systems (that are assigned different static IP addresses).
(Note: dhcp isn't running anywhere on my network.)
Note: the new box originally had AD and DNS running but I've since removed those services.
Any ideas?
If I am missing something obvious, please only kill half of my ego. 
Thanks. -- Through My Eyes |
|
 B Premium,MVM join:2000-10-28
| Changes are that in addition to their primary addresses, the older server NICs have secondary (or more) static IP addresses that you've overlooked.
If you leave the new box off, can you ping any of "its" addresses on the old network?
-- B -- In a realm outside causality and function |
|
  Kalford Seems To Be An Rtfm Problem. Premium,MVM join:2001-03-20 Ontario
·Rogers Hi-Speed
edit: March 15th, @12:12AM
| nope. no pings to the new box addresses when it's unplugged.
I tried one test where I gave the new nic's addresses on a different subnet and as soon as I plugged it in, the same two older systems (one's an XP box running an email server, one's a user's desktop) still immediately popped up with an IP conflict.
The new server itself doesn't report any IP conflicts and oddly enough appears to be able to ping the other two boxes. Tracert also returns the right host names on the other machines. . . . . even though the other machines have themselves lost connectivity to the rest of the network because of the conflict.
I removed the drivers for the network cards, did a full shutdown, pull power cords, rebooted and then re-installed the drivers on the new box, re-assigned different IP's (never used on my network) and still had the same conflicts with the other 2 boxes.
I also put up some popping foam on the wall to bang my head against.  -- Through My Eyes |
|
  AndyAsselin
@telus.net | reply to Kalford Simply why don,nt you try ping ip on network that you try assign to network from one you machine that all ready connected |
|
  Steve Security is inefficient Consultant join:2001-03-10 Tustin, CA
| reply to Kalford First: what kinds of systems are reporting the IP address conflicts, and what are the MAC addresses in questions?
You can get a great clue here by looking up the contested MACs via this site: »www.coffer.com/mac_find/ It may tell you Dell or Xerox or whatever, and provide some other clue.
But I've seen these before with old gear with bad firmware related to multicast stuff, so if I were onsite I've have Wireshark fired up right away to watch for who's responding to ARP requests. -- Stephen J. Friedl | Unix Wizard | Microsoft Security MVP | Tustin, California USA | my web site |
|
 BosstonesOwn
join:2002-12-15 Everett, MA clubs:
·Comcast Formerly ..
| reply to Kalford Check the DHCP pools. Some times those ips can be caught in the pool where some one actually pulled it but never released it before they shutdown or left the network. Sometimes especially on large pools with long lease times they will stay active and the dhcp server will throw that error.
I concur with wireshark and watching the ARP requests. There may be rogue boxes on the network you don't know about with a firewall on them blocking ping requests. -- "It's always funny until someone gets hurt......and then it's absolutely friggin' hysterical!" |
|
  Steve Security is inefficient Consultant join:2001-03-10 Tustin, CA
| reply to Kalford said by Kalford :Note: dhcp isn't running anywhere on my network. Why the heck not? It's nuts to run a network of any substantial size w/o DHCP... -- Stephen J. Friedl | Unix Wizard | Microsoft Security MVP | Tustin, California USA | my web site |
|
  TheGiant Next Year Is Here.
join:2001-03-28 Knoxville, TN edit: March 15th, @12:19PM
| reply to Kalford Could it be a naming problem? Do the new and old servers have the same name? |
|
  ekiM Oh Well
join:2001-01-06 /usr/home clubs:
| reply to Kalford Look for issues with the network (router, switches and NAT). You haven't really described the network involved. Something may be making a routing decision based upon stale information. -- "I can't sing, I ain't pretty and my legs are thin." |
|
 angussf Premium join:2002-01-11 Tucson, AZ
| reply to Kalford said by Kalford :nope. no pings to the new box addresses when it's unplugged. Just because there's no PING response doesn't mean there isn't something at that IP address; by default XP w/ SP2 doesn't respond to ICMP echo requests, you have to enable it in the firewall.
Have you tried scanning both the existing LAN and the new box on its own LAN to see what IP addresses is it trying to use? FWIW I would do this with the freeware IPSCAN program from Angryziber, it's really handy, and it'll try to find active IPs using methods other than pinging:
Angry IP Scanner - program for analyzing networks »www.angryziber.com/w/Home Download here: Download - Angry IP Scanner - program for analyzing networks »www.angryziber.com/w/Download Source code for cross-platform version here: »https://ipscan.svn.sourceforge.net/svnroot/ipscan/
HTH
A |
|
  Kalford Seems To Be An Rtfm Problem. Premium,MVM join:2001-03-20 Ontario
·Rogers Hi-Speed
| reply to Steve said by Steve :said by Kalford :Note: dhcp isn't running anywhere on my network. Why the heck not? It's nuts to run a network of any substantial size w/o DHCP... Laziness. (it's not that substantial a network.)
I'll run through the various suggestions on Monday (I'm actually having a weekend off this weekend ).
ekiM's suggestion to check the switches and routers is also something that crossed my mind last night.
I'll also throw the new box on it's own subnet and have a look what it's doing there.
Thanks for the suggestions so far folks. -- Through My Eyes |
|
  ttiiggy Premium join:2001-03-27
| reply to Kalford Check Advanced Settings. This is XP. Do you have multiple IPs in there on your new server or on the other boxes? |
|
  Kalford Seems To Be An Rtfm Problem. Premium,MVM join:2001-03-20 Ontario
·Rogers Hi-Speed
| I've checked that on all 3 boxes, all were good (including the wireless on the laptop). I also checked all the gateway and dns settings on all boxes. Everything there looks good. -- Through My Eyes |
|
  jlramirez Premium join:2004-10-01 Montgomery, IL clubs:
edit: March 16th, @12:44AM
| reply to Steve said by Steve: .It's nuts to run a network of any substantial size w/o DHCP...
I wouldn't go that far. Static addressing has its place as well. Keep in mind there are differing opinions (and that is it, opinions) on the matter and there is no one right.] -- Fiber Optics is the future of high-speed internet access. Stop by the BBR Fiber Optic Forum.
|
|
  Vchat20 Landing is the REAL challenge
join:2003-09-16 Warren, OH
·Time Warner VOIP
·RoadRunner Cable
| Personally, I'd go with the best of both worlds and run a dhcp system and force everyone to be fed static ip's by the dhcp server based on mac addy. MUCH less hassle keeping track and you still have referencable ip's for each box. Then again, that's just me. I, too, hate keeping track of manually assigned static ip's even on a small 5 machine home network since I'd need to go into each box to make any changes if required. 'Least with the dhcp assignment route, can keep the box's NIC set for auto and organize the whole network as you see fit from a central location.
Granted it wont SOLVE people manually setting their own ip and wreaking havoc on the network, but the machines you are in control of will be properly accounted for. |
|
 DigitalXeron There is a lack of sanity
join:2003-12-17 Hamilton, ON
·Cogeco Cable
·Bell Sympatico
edit: March 17th, @01:09AM
| reply to Steve said by Steve :said by Kalford :Note: dhcp isn't running anywhere on my network. Why the heck not? It's nuts to run a network of any substantial size w/o DHCP... From experience: Servers should not be configured via DHCP, workstations, sure, but servers no, because you really can't have servers changing IP addresses or tripping over each other when it's renew time -- yes, you can do static DHCP but that's a single point of failiure -- what if the DHCP server goes down and IP leases expired? ouch. a good sum of other servers left inaccessible, just a good record of which server has which IP(s) is all you need really. -- --Kradorex Xeron
|
|
  Killer Max
@rr.com
thumbs down from: Cabal 
| reply to Kalford said by Kalford :Note: dhcp isn't running anywhere on my network. Smart man. DHCPee should only be used for laptops or other portable devices that roam from network to network. It is too problematic to be trusted unless absolutely necessary. Can't beat an iron clad static IP. Now, back off the soap box, did you try "arp -a" from a dos prompt ? Ping the IP in question just before issuing the command to be sure that it is still alive in the arp table. The arp -a command returns all IP addresses and the MAC address associated with them in the whole network. |
|
  coxta Ultramundane Premium join:2000-07-15 LALALALALALA
·Pacific Bell - SBC
| reply to Kalford Severs static and clients DHCP, but I use permenant leases. It's easier to tell who is who.
Kalford, Microsoft doesn't like multihoming. That's the way I ran my mail server for years, it works, but Microsoft tech support said MS would not support it. -- I've never been drunk, but often I've been overserved.
|
|
  Kalford Seems To Be An Rtfm Problem. Premium,MVM join:2001-03-20 Ontario
·Rogers Hi-Speed
| reply to Kalford Update on this issue.
I started back from scratch with the intent of going through everything I had tried before as well as everything suggested here.
This time round I lost the network protocols. (I dunno - don't ask)
Summary version. I wiped the box and re-installed from scratch.
Everything is working fine now.
Drywaller's are in tomorrow to repair the head-size hole in my office wall. -- Through My Eyes |
|