Thanks much for this additional info James. And, the initial "DHCP failed" types of messages I get when I first boot the system do seem to right themselves fairly quickly. BTW, I was able to fix fuzzy resolution problem by changing my default screen settings. So far, so good... Even used the Package Manager application for the 1st time.
Thanks again, Nita On 12/17/08 14:56, James Carlson wrote: > Juanita Heieck writes: > >> opensolaris console login: Dec 16 00:27:23 opensolaris mDNSResponder: >> Unable to >> parse DNS server list. Unicast DNS-SD unavailable >> > > That sounds like a problem with svc:/network/dns/multicast:default. > By searching in sunsolve, appears to be CR 6741196, and is caused by a > lack of /etc/resolv.conf during an initial boot. > > I don't believe that it'll have any effect on your system, unless > you're using the mDNS-based service discovery (Bonjour). > > Most importantly, it has nothing to do with "normal" DNS used for > resolution of host names. > > >> Dec 16 00:27:34 opensolaris in.routed[534]: route 0.0.0.0/8 --> 0.0.0.0 >> nexthop >> is not directly connected. >> > > I don't think that's a problem. That's most likely due to the > reworking of the DHCP client implementation done by CR 4354207. The > client now brings up the address with a zero address, and that > confuses in.routed. It rights itself once the interface is > established. > > (Feel free to file a bug, but I don't believe it actually will cause > you any operational problems.) > > Neither of these messages describes a problem that seems related to > the issue you're having. > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/install-discuss/attachments/20081217/d7d472ca/attachment.html>
