<html>
<P>Hi,</P>
<P>You need to make your Win2003 DC the DNS server. The clients will be attempting to look up stuff such as the _kerberos and other service zones on the DNS server and getting very upset with the response they are receiving! :-)</P>
<P>You will just need to get the DC DNS to then submit all other domain queries to the Debian Box.</P>
<P>NT4 never used DNS for anything (Bill hated the whole idea of the internet back then I think).</P>
<P>Regards,</P>
<P>John.<BR>
<BR>
<BR>
<B>On Fri Jan 20 12:42 , 'Jonathan Young' <jonathan@pcphix.com> sent:<BR>
<BR>
</P></B>
<BLOCKQUOTE style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #5167c6 2px solid; MARGIN-RIGHT: 0px"><BR>
Just a really fast query for a new job that I have just started which has<BR>
me stumped... It is a 50/50 Windows/Linux situation, so I hope this<BR>
won't be deemed 'off-topic'.<BR>
<BR>
I am more or less looking for inspiration and ideas - a place to start.<BR>
<BR>
Here goes...<BR>
<BR>
A Windows NT box is being used a file server and logon server -<BR>
effectively it is the PDC. No problem.<BR>
<BR>
A Debian box is being used with a DSL-300 modem in bridge mode to provide<BR>
DNS and act as a gateway. As me for more information if you need it!<BR>
<BR>
The various Windows XP clients on the network see the Linux box as the<BR>
Default Gateway and DNS server on 192.168.1.1, but they log in to<BR>
(authenticate) and get their ** WINS ** service from the Windows NT box<BR>
on 192.168.1.128 - the default gateway remains 192.168.1.1 which has a<BR>
second network card in it (eth1) which is 192.168.0.1 with the modem on<BR>
192.168.0.2 and everything works!!<BR>
<BR>
All is going well until the Windows NT box needs to be replaced...<BR>
<BR>
The new Windows 2003 Server box appears to do the job.<BR>
<BR>
However...<BR>
<BR>
For no reason in particular (or so it seems so far), Windows logon's<BR>
take a long time (around 2 mins) and occasionally what seems to be a<BR>
timeout on the network connection seems to cause applications to hang. <BR>
The XP machines log errors ranging from 'Application error in<BR>
blah.exe' to 'Domain Controller Unavailable' even after a successful<BR>
logon.<BR>
<BR>
If the Debian box is running the DNS and default gateway; the Windows<BR>
2003 Server box is supplying WINS and authentication, where could the<BR>
bottle neck be???<BR>
<BR>
Any hints, tips or ideas are very much appreciated and more information<BR>
is available on demand (I have remote access to both servers).<BR>
<BR>
<BR>
--<BR>
Jonathan Young<BR>
Director of PC-PHIX<BR>
<A href="javascript:top.opencompose('jonathan@pcphix.com','','','')">jonathan@pcphix.com</A><BR>
<BR>
Phone: 0410 455 674<BR>
Web: <A href="parse.pl?redirect=http%3A%2F%2Fwww.pcphix.com%2F" target=_blank><FONT color=red>http://www.pcphix.com/</FONT></A><BR>
_______________________________________________<BR>
PLUG discussion list: <A href="javascript:top.opencompose('plug@plug.org.au','','','')">plug@plug.org.au</A><BR>
<A href="parse.pl?redirect=http%3A%2F%2Fwww.plug.org.au%2Fmailman%2Flistinfo%2Fplug" target=_blank><FONT color=red>http://www.plug.org.au/mailman/listinfo/plug</FONT></A><BR>
Committee e-mail: <A href="javascript:top.opencompose('committee@plug.linux.org.au','','','')">committee@plug.linux.org.au</A><BR>
</BLOCKQUOTE>
</html><BR>