Re: Windows SBS 2003 - Suddenly cannot connect to network shares
From: Lanwench [MVP - Exchange] (lanwench_at_heybuddy.donotsendme.unsolicitedmail.atyahoo.com)
Date: 11/03/04
- Next message: Lanwench [MVP - Exchange]: "Re: POP3 Is not working"
- Previous message: Richard Morey: "POP3 Connector Lost Mail"
- In reply to: SuperGumby [SBS MVP]: "Re: Windows SBS 2003 - Suddenly cannot connect to network shares"
- Next in thread: Lanwench [MVP - Exchange]: "Re: Windows SBS 2003 - Suddenly cannot connect to network shares"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 3 Nov 2004 09:20:31 -0500
SuperGumby [SBS MVP] wrote:
> this IS NOT an SBS specific thing, it is pure AD, or maybe it should
> be considered a pure 'name resolution' item.
>
> In non-SBS land people make other excuses and blame it on them.
>
> all this is very much IMnotsoHO, of course.
>
> Windows 2000 moved towards DNS as the primary name resolution
> mechanism, XP set it in concrete. IMHO most of the thousands of posts
> I read can be blamed on incorrect name resolution.
Yes....absolutely. On the LAN side. Hence, one uses forwarders or root hints
on the internal DNS server. Where I'm getting confused is why the *external*
NIC would point to anything on the internal IP network at all in its
properties.
>
> Even I bore m'self going on about it as much as I do.
>
>>> If you have one server it should look to itself and ONLY itself.
>>
>> Yep - I know, just wondering why the external NIC would need this. I
>> know SBS is its own animal, but outside of SBS this isn't usual.
>> <shrug>.
- Next message: Lanwench [MVP - Exchange]: "Re: POP3 Is not working"
- Previous message: Richard Morey: "POP3 Connector Lost Mail"
- In reply to: SuperGumby [SBS MVP]: "Re: Windows SBS 2003 - Suddenly cannot connect to network shares"
- Next in thread: Lanwench [MVP - Exchange]: "Re: Windows SBS 2003 - Suddenly cannot connect to network shares"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|