Date   : Sun, 25 Oct 2009 21:22:19 +0000
From   : gary@... (Gary McCallum)
Subject: Master Ethernet Upgrade

>>>
>>
>> so should:
>> (d) *mount \\192.168.100.55\Public user pword but it also gives  
>> "Host not
>> known".
>
> That last one should work, provided the reverse lookup is happening,  
> which
> it sounds like it isn't.
>
> Let me see if I can get the Win2k machine at work added to the  
> domain and
> mess about for a bit there, if we need to do some off-list packet  
> sniffing
> I'll let you know,
> Sprow.
>
>

A quick heads up, if when you get the host resolution problem solved  
you still can't connect, look into packet signing in either the domain  
security policy or the local security policy of the file server.   
Windows 2003 by default won't talk to machines which can't digitally  
sign packets, OS X up to version 10.4 in particular has this problem  
when talking to Windows 2003.  However I don't know what effect (if  
any) this has on a Windows 2000 file server with a 2003 DC as the last  
time I had to manage a Windows 2000 file server I was only supporting  
Windows clients.

You can turn this off at domain level or a server level if need be.

Gary