It's a dynamic arp request. So is there a location to add a fixed arp request on the server having the issue? Currently it has a fixed IP address - does it need to be a dynamic one with a DHCP reservation?
Jay Dale I.T. Manager, 3GiG Mobile: 713.299.2541 Email: [email protected] Confidentiality Notice: This e-mail, including any attached files, may contain confidential and/or privileged information for the sole use of the intended recipient. If you are not the intended recipient, you are hereby notified that any review, dissemination or copying of this e-mail and attachments, if any, or the information contained herein, is strictly prohibited. If you are not the intended recipient (or authorized to receive information for the intended recipient), please contact the sender by reply e-mail and delete all copies of this message. -----Original Message----- From: Michael B. Smith [mailto:[email protected]] Sent: Monday, April 12, 2010 10:36 AM To: NT System Admin Issues Subject: RE: Initial access to server denied, then accepted This is classic duplicate IP issue. What you are seeing is multiple hosts on a LAN segment responding to something called an "ARP request". The way IP determines whether something is LOCAL is by issuing an "address resolution protocol request". It's a broadcast transmission that requests anyone having a particular IP address to respond with their MAC address. This information is stored in the "arp cache" for (by default) 2 minutes. If an upstream or downstream switch has that IP connected to their matrix, they'll respond with a proxy ARP response saying that they'll forward it. If there is no response to the ARP, then the message goes out the default gateway. This is an oversimplification, but it's the general process. You've got two hosts responding to the ARP request. From a Windows command line, "arp -a" will dump your current ARP cache, and figure out whether it's a regular ARP response or a proxy ARP response. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com -----Original Message----- From: Jay Dale [mailto:[email protected]] Sent: Monday, April 12, 2010 11:28 AM To: NT System Admin Issues Subject: RE: Initial access to server denied, then accepted Just an additional note - I disconnected from Remote Desktop to the server and tried immediately reconnecting, and it connected fine. Then I disconnected and reconnected about 5-10 minutes later, and it failed on the initial connection and succeeded on the second attempt. Jay Dale I.T. Manager, 3GiG Mobile: 713.299.2541 Email: [email protected] Confidentiality Notice: This e-mail, including any attached files, may contain confidential and/or privileged information for the sole use of the intended recipient. If you are not the intended recipient, you are hereby notified that any review, dissemination or copying of this e-mail and attachments, if any, or the information contained herein, is strictly prohibited. If you are not the intended recipient (or authorized to receive information for the intended recipient), please contact the sender by reply e-mail and delete all copies of this message. -----Original Message----- From: Jay Dale [mailto:[email protected]] Sent: Monday, April 12, 2010 9:51 AM To: NT System Admin Issues Subject: Initial access to server denied, then accepted Hey all, I recently installed BE 2010 and had an issue with it not detecting the Remote Agent on one of the servers. I tried telnetting to the server over port 10000 which the RA uses, and the first attempt failed, but the second attempt failed. I then tried a job directly to the server, and the first attempt failed, but the second attempt succeeded. I then tried to just Remote Desktop to the server - the first attempt failed, the second attempt succeeded. I went into the server EV and noticed there was one error saying there was a duplicate IP address on the network, with the MAC address being the MAC of our firewall. It is a Sonicwall TZ210. The firewall is not doing DHCP on the LAN, our SBS is doing that, but it does DHCP for the wireless. Yet the wireless subnet is totally different than the LAN subnet. Another interesting thing - the error message does not happen at the same time as the issues I'm having, and it does not repeat but once in a span of a few weeks. This morning that error is not present, but the connection issues still apply. This is a virtual server, and as far as I can tell there's no sleep or standby going on. Anybody had something like this happen before? Thanks, Jay Jay Dale I.T. Manager, 3GiG Mobile: 713.299.2541 Email: [email protected] Confidentiality Notice: This e-mail, including any attached files, may contain confidential and/or privileged information for the sole use of the intended recipient. If you are not the intended recipient, you are hereby notified that any review, dissemination or copying of this e-mail and attachments, if any, or the information contained herein, is strictly prohibited. If you are not the intended recipient (or authorized to receive information for the intended recipient), please contact the sender by reply e-mail and delete all copies of this message. ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
