another side note. make sure your shared directory names
on the shares are less then 12 charactors long or win98
and older machines will see the server but not the
directories.
>-----Original Message-----
>
>>Hello
>>
>> I just migrated over to a new Windows 2003 Active
Directory Domain. I have
>>a client in another building (17 miles away) they
connect to us through a
>>site-to-site vpn done with our firewalls (so it should
be invisible to the
>>windows servers) we are using 192.168.200.x addresses he
is using
>>192.168.201.x address (not sure if it matters but wanted
to let you know)...
>>I have installed A/D client... So my problem is he can't
browse shares on
>>any of our 2003 servers execpt one (which happens to be
the one with the PDC
>>emulator)... One post said enable browse master so I did
and it helped a
>>little, he was at least able to see the network. But
everytime he clicks to
>>open the computer he gets "name not found on network"...
WINS is set and
>>working properly, DNS is set and working properly...
Quite frankly I'm lost
>>the only thing I have not done is set the SMB signing
done a level... Hope I
>>don't have to... Please help...
>>
>>Joe S.
>>
>>
>>
>Joe,
>
>Can you ping the server resource by short name and does
it resolve to the correct IP Address? Can you Net Use to
the resource or Net View? The real
>test is connectivity; can you go the Start --> Run
\\Server\Share and access that resource directly? How
about if you use \\IP Address\Share?
>
>You are running the latest DS client for windows 98, i
would expect this to work then the issue becomes a
possible domain browsing issue.
>
>Let make sure that we have TCP connectivity and that the
client can access the resource directly using "net use".
>
>T.J. Campana [MSFT]
>Microsoft EPS Networking
>--
>This posting is provided "AS IS" with no warranties, and
confers no rights. Use of included script samples are
subject to the terms specified at
>http://www.microsoft.com/info/cpyright.htm
>
>Note: For the benefit of the community-at-large, all
responses to this message are best directed to the
newsgroup/thread from which they originated.
>
>.
>