944,098 Members | Top Members by Rank

  • Networking Discussion Thread
  • Unsolved
  • Views: 1496
  • Networking RSS
Apr 3rd, 2006
0

BootP server issue: apparent LAN bridging

Expand Post »
I have a triple homed system (a Dell GX270 w/512MB RAM running Windows 2000 Pro SP4 fully patched): the built-in (onboard) NIC is connected to our production network, the second NIC (a 3C900B combo RJ45/BNC card) is connected to one device via BNC cable (this device is controlled via direct IP communication to the MAC address or the device's network card) and the third NIC (a 3C900B TPO card) is connected to a second device via Intel 5 port hub, and receives its' IP address via bootp (server resident on the PC).

The problem is this: The bootp server is supposed to receive an IP address request from the 2nd device upon device bootup, which it does without issue provided the production network is disconnected OR the NIC is disabled. When the production network is enabled, the resident bootp server sees requests from other similar devices on the network. The bootpserver, having been configured to respond only to requests from the 2nd device's MAC address, rejects all of these foreign requests, but in doing so cannot process the one request which it SHOULD be responding to. Today, the bootp requests were coming in at such a rate that the CPU utilization approached 100%.

The bootp server is from Agilent and should be associated only with the third NIC. Is there a way to isolate the bootp server? Is there a way to prohibit what looks to be LAN bridging? The Routing and Remote Access service is disabled.

Any and all assistance tou might be able to give me would be appreciated.
Last edited by DMR; Apr 3rd, 2006 at 6:23 pm. Reason: Removed reference to duplicate thread
Similar Threads
Reputation Points: 10
Solved Threads: 0
Newbie Poster
poppaman2 is offline Offline
6 posts
since Mar 2006

This thread is more than three months old

No one has posted to this discussion for at least three months. Please let old threads die and do not reply to them unless you feel you have something new and valuable to contribute that absolutely must be added to make the discussion complete. Otherwise, please start a new thread in this forum instead.
Message:
Previous Thread in Networking Forum Timeline: linksys WRT54G
Next Thread in Networking Forum Timeline: Port Fowarding





About Us | Contact Us | Advertise | Acceptable Use Policy
Forum Index | Build Custom RSS Feed


Follow us on Twitter


© 2011 DaniWeb® LLC