|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [FW1] More network neighborhood browsing questions
Title: More network neighborhood browsing questions
With
98 you need to make sure that the Client for MS Networks is installed and that
the users are putting in their account information and hitting OK (not cancel)
at both the initial logon screen and the "No Domain server..." screen that
follows. This caches the user account so that when they do connect, their
account info is there when NT Auth needs it. Basically setup the machines
exactly as you would on your LAN.
Make
sure that you have your WINS server specified in IP for the dialup adapter as
well. This could be the root of all evil here as well. I belive there's a way to
set the browse master timeout to something higher, but the method escapes me at
the moment.
-
CQ
They
are 98 clients and I dont think they are authenticating.
My
problem is with the order of operations I guess. When the client boots do they
need to enter the same domain password in their windows logon? Then when they
dial up to the ISP that password is passed?
After you establish a dial-up connection how do you insure you get
prompted to log on to the domain. And how do you make sure its not trying to
log onto the ISP's domain?
-DP
Which OS are the clients using, and are they
authenticating to an NT domain?
I have the same browsing problem although I cant even use \\server technique!
I get the error "Not logged onto the domain" or "The sharename can
not be found"
Does the WINS server need to have an external address so that the
dialup connection can contact the master browser? I thought that went away
with FW4.0
Do I need to put the WINS server in the Encryption
Domain?
I would be happy if I could map a drive
Dave Pope
I've seen this before. The problem is that the
browse list is too slow to compile when using the vpn connection, so it
times out and shows you nothing instead. UNC names (\\server) are the
way to go.
- CQ
Hello all,
I am trying to set up SecuRemote 4.1 SP2
3DES (build 4166). My FW-1 4.1 SP2 is running on NT4.0 Sp
6a. I did everything documented in CP's references and
successfully download the topology from the FW-1. I can use
\\computername and ping the servers defined in my LMhost file.
The only problem is that I CAN'T browsing the network
neighborhood!!! Searching the mailing list archive I didn't find
any answers. Thus, I don't know where I need to change the
settings. The more strange thing is that it works only for Win2K
but not WinNT 4.0 workstation. It drives me crazy at this
point. From my ISP provider's suggestion: On Win2k and NT, you will not be able to see
the network under network neighborhood but you should be able to start
run and do \\networkmachine you are trying to access.
Am I wasting my effort here? From CP's
document, I should be able to browse NT domain through VPN, right?
Thanks in advance. I really
appreciate any hints and help.
Best Regards, Chi-lien Lee
|
|