Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Browsing to a dial up client
0 views
Skip to first unread message
Charles Blair
Aug 16, 2001, 4:52:49 PM8/16/01
to
I have a Win2K server running RRAS. All the remote clients are running
TCP/IP only, and they cannot register their NetBIOS name for browsing when
dialing in. Ping and other applications that run by straight IP can connect
fine. But if I try connecting to the remote client by UNC it cannot find
the path. I have tried using DNS, WINS, and LMHOSTS for resolution but
still cannot connect to a dial-in client. The clients can register their
name/address in DNS and WINS but communications back through the dial-up
error out. If anyone knows a workaround for this problem (other than
installing NetBEUI on the client), it would be much appreciated.
TCP/IP only, and they cannot register their NetBIOS name for browsing when
dialing in. Ping and other applications that run by straight IP can connect
fine. But if I try connecting to the remote client by UNC it cannot find
the path. I have tried using DNS, WINS, and LMHOSTS for resolution but
still cannot connect to a dial-in client. The clients can register their
name/address in DNS and WINS but communications back through the dial-up
error out. If anyone knows a workaround for this problem (other than
installing NetBEUI on the client), it would be much appreciated.
Thanks in advance for any help
Charles Blair
charle...@hotmail.com
Charles Blair
Aug 17, 2001, 1:58:48 PM8/17/01
to
That is one of the other problems. Installing NetBEUI is not a viable
option for the fix. RRAS would recognize the client NetBEUI name, if it was
installed. But I need a workaround where RRAS would pull the client name
from a WINS directory or DNS, which it currently is not doing. I just don't
understand why it doesn't currently work. I have a client dial-in. I can
ping the client by name and IP. I would think that by initiating a UNC
session to the client by using either netbios \\client\c$ or DNS
\\client.company.com\c$ that it would go to the WINS or DNS server to
translate the name to IP and then complete the path. The only reason I can
see why it would not is because the client cannot register its name in the
browse list. This might explain the netbios path but the DNS path should go
straight to the DNS server for resolution. That was supposed to be the big
thing in 2000, was to finally get rid of WINS and NetBEUI and complete all
connections through DNS. I guess MS didn't make it as bulletproof as
claimed
option for the fix. RRAS would recognize the client NetBEUI name, if it was
installed. But I need a workaround where RRAS would pull the client name
from a WINS directory or DNS, which it currently is not doing. I just don't
understand why it doesn't currently work. I have a client dial-in. I can
ping the client by name and IP. I would think that by initiating a UNC
session to the client by using either netbios \\client\c$ or DNS
\\client.company.com\c$ that it would go to the WINS or DNS server to
translate the name to IP and then complete the path. The only reason I can
see why it would not is because the client cannot register its name in the
browse list. This might explain the netbios path but the DNS path should go
straight to the DNS server for resolution. That was supposed to be the big
thing in 2000, was to finally get rid of WINS and NetBEUI and complete all
connections through DNS. I guess MS didn't make it as bulletproof as
claimed
"Joshua Tree" <d...@dimensionpoint.com> wrote in message
news:OMYsbVpJBHA.600@tkmsftngp05...
> My clients are configured to connect using
> both TCP/ip and NetBeui. They need NetBeui.
> But that doesn't solve my problem, yet it may
> solve yours
>
>
"Charles Blair" <charle...@hotmail.com> wrote in message
news:usogMTpJBHA.1332@tkmsftngp04...
0 new messages