we had the same problem when performing an IDR restore on a compaq server
with two onboard gigabit ethernet adapters.
we are still trying to find a better solution, but the following workaround
helped solving the "strange network behaviour":

"After the restore is complete,
reboot the computer in "Safe Mode" (without networking).
logon as Administrator (not domain-administrator).
open the Device Manager: under Network Adapters select each entry:
(in this case
NC7780
NC7780 #2
Direct Parallel Port
WAN Miniport (IP)
WAN Miniport (L2TP)
WAN Miniport (PPTP)
and choose Properties // Update Driver : Let the system search for better
drivers on the local harddisk. Better drivers are found in folders under
the WINNT directory.

reboot the computer.
logon as Domain-Administrator.
open the Device Manager and uninstall both entries for the (NC7780) ethernet
adapters.

reboot the computer.
logon as Domain-Administrator.
open the device Manager.
wait until the PopUp "New hardware found" appears and the network adapters
are recognised.
(this should happen automatically)

right-click the icon My network places on the desktop and select Properties:
both network adapters should appear as LAN Connection 3 and LAN Connection
4 (numbers can vary).

Configure both Adapters and (if used) compaq teaming settings, according
to the server config sheet.

If the teaming setup fails, uninstall and reinstall the compaq teaming drivers
(normally not necessary).

Verify the netowrk settings by entering "ipconfig /all" at a command line.
"

We do still have an open call at Veritas regarding this issue, so if anyone
else is also working on this problem, I'd be interested in his/her opinion&tips.



"john carroll" wrote:
>
>In wishing to create a spare drive, I did a IDR restore to an "exact" IDE
>drive from my original and all went very well except I loss my network adapter
>and cannot install/reinstall. A network adapter shows up as "WAN miniport
>(L2TP)" and was extremely difficult to remove. It is now removed but I
cannot
>install any network adapter.
>
>MS has Q318715 out there that describes the problem and I wondering if anyone
>has had this expierence and what their final outcome was and what action
>was taken to resolve it. MS suggests an in place upgrade "might" work.
>
>Thanks in advanced
>John Carroll
>ejohncarroll@hotmail.com