I am a little confused about all this. First of all, our
workstations do NOT log into a PDC. They log into a
Netware 6 Server. Now we have a Microsoft server at a
main location that is doing some peer file sharing.

At our branches I am trying to map a drive to that
server. Problem #1, NetBios is used for name resolution,
but can not be routed. Is that not retarded? Problem #2,
to fix this, the general feeling seems to be set up a WINS
server. Well, I don't want to do that because a. I don't
really know anything about WINS, and b. SHOULDNT I BE ABLE
TO DO THIS WITH DNS? If I map to the IP address, then
when I try to open a file, it asks me if I want to save it
to disk or open it.

I tried to add the name to the hosts file and map that way
and it works, but EXTREEEEEEEEEMLY slow.

Any ideas? Here are the specifics: Windows 2000 Server SP
4. Windows XP SP 1 workstations, T1 WAN link, different
subnets, we do have a Windows NT 4.0 DNS server in house,
IP only. Mapping works at our main branch, but I fear it
is because it is using NetBios for name resolution here
(doesn't need routing).

Ryan

"RAM - Attemp by certain large vendors to shove their
propietary technology solutions down your enterprise." ~
From Novell Ad

"Ryan McAtee" <(E-Mail Removed)> wrote in message news:<906901c40858$6728ae00$(E-Mail Removed)>...
>
> Any ideas? Here are the specifics: Windows 2000 Server SP
> 4. Windows XP SP 1 workstations, T1 WAN link, different
> subnets, we do have a Windows NT 4.0 DNS server in house,
> IP only. Mapping works at our main branch, but I fear it
> is because it is using NetBios for name resolution here
> (doesn't need routing).

If you don't want to use WINS, set up the workstations
with LMHOSTS files. But WINS isn't that hard to set up and
it is much more flexible than keeping control of a bunch of
LMHOST files, especially if you are using DHCP and providing
the NetBIOS name server address. The WinNT DNS server could
host it as well.

You should be able to use IP addresses or names (net use *
\\111.111.111.1\share or \\host.company.com\share) and that
should not be as slow as you describe. You might want
to check the traffic and see what is slowing things down.

--
M Hickman

In addition, you should add the records rather to the DNS server than to the
hosts file. If the mapped network is slow, then it's misconfigured, i.e.
broadcasts too much and/or validates the credentials too often and/or
retransmits too many segments etc. If you cannot deploy WINS servers in the
remote locations and in every subnet, you should implement the lmhosts file
with preloaded records approach. NetBIOS over TCP/IP overcomes any routed
environment.

"Jetro" <no.spam@internet> wrote in message news:<(E-Mail Removed)>...
> If you cannot deploy WINS servers in the
> remote locations and in every subnet, you should implement the lmhosts file
> with preloaded records approach. NetBIOS over TCP/IP overcomes any routed
> environment.

WINS servers are not needed in every location and subnet. A single
WINS server should be sufficient (a second would be needed as a failsafe
only). The clients just need to be told the IP address of the WINS
server(s -- which can be done by DHCP. Install WINS, setup DCHP to
parcel out the WINS location(s) along with the workstation's IP and DNS
servers locations and that is about it.

--
M Hickman

Right. WAN connection misled me, but I think the branch services should be
there for the redundancy.

>-----Original Message-----
>Right. WAN connection misled me, but I think the branch
services should be
>there for the redundancy.
>

Thanks, guys. I set up the WINS server right on the
server I am trying to access and it works great for name
resolution. Still very slow, so I must have some other
problems going on. Will investigate. Thanks for your
help.