If you are running SBS2003 then you must be running a AD domain. So your
clients should be pointing to the local DNS server only. You cannot simply
use NAT as a DNS proxy with AD.
If your clients cannot resolve DNS names, the problem must be with your
DNS server. It should be configured to forward DNS requests which it cannot
handle itself to a public DNS server. Have you checked to see that the
server can resolve external DNS names?
"Stu Lock" <(E-Mail Removed)> wrote in message
news:%23%(E-Mail Removed)...
> Hi,
>
> I have been having major problems with our internal network sharing an
> Internet connection. We are running SBS2003 Standard and using the routing
> and remote access service.
>
> This has been running for months without any problems for months. Over the
> last month or so it has started becoming unreliable. Once or twice a day
> the connection stops being shared properly and I have needed to restart
> the routing & remote access service on the server to get it going again.
> No events of this failure were reported in the events logs.
>
> This moring I came in to find no access at all on the office machines. I
> narrowed it down to a DNS error and have put an external secondary DNS
> server entry in each of the client machines to get the sharing going
> again - before i was using 192.168.0.1 as the sole dns server.
>
> There was this error in the the event log this morning :
> The DNS server could not signal the service "NAT". The error was 1168.
> There may be interoperability problems between the DNS service and this
> service.
>
> Has anybody got any idea what the problem may be or how I can find out any
> more information?
>
> Thanks in advance,
>
> Stuart
>
>
|