Xserve Bad MAC address - Unable to reach DNS

Question

I have just set up our new Xserver, and have had many difficulties diagnosing network problems. I am able to log into the system via ssh using it's fixed ip number and domain name, but I am unable to use the server admin tools to connect to the system (The Xserve is rack-mounted at a remote location, we have no monitor or graphics card installed. According to /var/log/system.log, when the system boots, it is unable to locate DNS, and is unable to properly set its hostname. While I can log in, I am unable to reach (ping) any outside host. I am certain the DNS IP numbers are correct in the network settings (both resolve.conf and networksetup properly report it).
However, after reviewing the /var/log/system.log and using networksetup command-line inquires, I have determined the MAC addresses for the two en0 and en1 ports are incorrect in the system log. networksetup reports the correct DNS IP numbers and hostname... but the MAC addresses do not match the ones in the system.log
Is my only alternative to re-install the OS? or is there an easier way to correct the problem via a command-line?
When I set up the system the MAC addresses, I read them and the serial number from the tab on the back of the Xserve. It was so poorly printed I was unable to properly distinguish between an "E" and a "3" or and "8" or an "F"... it was nearly impossible to read the numbers in the pull-out tab in the back of the machine because too much ink was used in the printing... I even used a magnifying glass!

Answer 1

Well, it took over a week for Apple to get the replacement install DVD to me, and I finally did successfully re-install the OS. I followed a previous posters advice and only used one ethernet port for both my regular and LOM ethernet setup, and that seems to have been the ticket.
This whole process would have been a lot easier if we had added the graphics card for the Xserve. I would have used it only once, but it would have saved me a days instead of trying to do a headless boot nad setting up over a network. My other tibbit of advice is to do the install plugged into the network you plan on using. In my case, the location we co-locate our servers was initially hesitant to let me in the main computer room to do the setup, and I tried doing it in their office location on a different LAN. I should have insisted at the beginning I needed to be in the computer room. Highly inconvienent though, freezing, hundreds of fans in the room going, setting up my client system on a chair, etc. This is my third server install, and all three were very difficult to perform. Once these servers are running though, they still take a tiny fraction of the time mantaining compared to our old Solaris/Windows systems!