Re: connectivity trouble after network failure
- From: "Joseph O'Brien" <obrien1984@xxxxxxxxxxx>
- Date: 17 Jul 2006 07:22:34 -0700
Thanks, Jollino. I think you were right about SMB using some sort of
internal DNS.
I actually figured out that I needed to add a search domain
(ourcompany.com) to the network preferences. I don't understand why
not having it there hasn't been a problem for the last 2 years, but it
seems to have fixed everything.
Joseph
Jollino wrote:
In article <1153143809.978525.17970@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>,
"Joseph O'Brien" <obrien1984@xxxxxxxxxxx> wrote:
I would say that the problem lies solely in DNS resolution, but I have
no trouble connecting through SMB.
That might be because SMB uses some sort of "internal DNS" based on
network broadcasts (often criticised for "jamming" networks).
I'd suggest you fix your DNS settings, or find another DNS to use if
your own / your company's NS is having issues. :)
--
Jollino
.
- References:
- connectivity trouble after network failure
- From: Joseph O'Brien
- Re: connectivity trouble after network failure
- From: Jollino
- connectivity trouble after network failure
- Prev by Date: Re: connectivity trouble after network failure
- Next by Date: how do you use dscl to query values
- Previous by thread: Re: connectivity trouble after network failure
- Next by thread: Re: connectivity trouble after network failure
- Index(es):