well, i disabled the dns as dhcp services. i set the nic to obtain ip
automatically. then i uninstalled the nics and rebooted.
after the restart, i reset the static ip, set the services to automatic and
rebooted again.
network was available right away and all services started.
--
Gary Keramidas
Excel 2003
"Gary Keramidas" <GKeramidasAtMSN.com> wrote in message
news:...
>i had win2k3 r2 running on this server, no issues.
> i did a clean install of 2008 r2 standard. the m/b has 2 nics onboard, i use
> lan2 with an ipv4 static ip. the other nic is disabled. it's not a dc, just a
> workgroup server.
>
> when i boot up, it takes about 2 minutes before the nic is recognized. i will
> then see the network icon in the map in n/w and sharing center. but since it
> took 2 minutes to start the nic, dns isn't running and i have to manually
> start the service. event log says the network is not present.
>
> had hyper-v installed, but uninstalled it to see if it was causing the issue.
> i have themes enabled, wit the desktop experience installed, that's about it.
>
> what could cause the network to not be recognized for 2 minutes?
>
> --
>
>
> Gary Keramidas
>
>
>
|