|
|
|
|
|
|
|
|
 |
 |
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] RE: [FW1] More network neighborhood browsing questions
If there is a network card in the PC ensure that tcp is not bound to the network card or that there are no settings in the tcp properties for the network card. This can impact on dialup and WINS settings ,default gateway dns etc. make sure these are all defined in the properties for the dialup connection. In Client for MS Networks make sure the tick box login to domain is ticked and the domain entered ensure the workgroup is set to the name of the domain sugest you preload the PDC details into the lmhosts. (not lmhosts.sam this is only a sample file) Read Q180094 Q190648 Q134304 Q150800 from microsofts technet (available online at MS) Also check what version of dialup networking you are using. regards Dean -----Original Message----- From: [email protected] [mailto:[email protected]] Sent: Wednesday, 14 February 2001 10:11 AM To: [email protected]; [email protected]; [email protected] Subject: RE: [FW1] 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 -----Original Message----- From: Pope, David [mailto:[email protected]] Sent: Tuesday, February 13, 2001 4:09 PM To: '[email protected]'; Pope, David; [email protected] Subject: RE: [FW1] More network neighborhood browsing questions 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 -----Original Message----- From: [email protected] [mailto:[email protected]] Sent: Tuesday, February 13, 2001 3:41 PM To: [email protected]; [email protected]; [email protected] Subject: RE: [FW1] More network neighborhood browsing questions Which OS are the clients using, and are they authenticating to an NT domain? -----Original Message----- From: Pope, David [mailto:[email protected]] Sent: Tuesday, February 13, 2001 3:31 PM To: '[email protected]'; [email protected] Subject: RE: [FW1] More network neighborhood browsing questions I have the same browsing problem although I cant even use \\server <file://\\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 -----Original Message----- From: [email protected] [mailto:[email protected]] Sent: Tuesday, February 13, 2001 3:16 PM To: [email protected] Subject: RE: [FW1] More network neighborhood browsing questions 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 -----Original Message----- From: [email protected] [mailto:[email protected]] Sent: Tuesday, February 13, 2001 2:43 PM To: [email protected] Subject: [FW1] More network neighborhood browsing questions 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 *************************************************** This e-mail is not an official statement of the Waikato Regional Council unless otherwise stated. Visit our website http://www.ew.govt.nz *************************************************** ================================================================================ To unsubscribe from this mailing list, please see the instructions at http://www.checkpoint.com/services/mailing.html ================================================================================
|
||||||||||
 |
 |
 |
 |
 |
 |
 |
 |
 |
|
