Normally, if you have proper IP connectivity with Securemote and proper
NetBios name resolution with WINS, everything should work fine.
To debug your problem, maybe can you try a lmhost file instead of the WINS
and use nbtstat -c to show what's up in the nbt cache. To debug, try also
net view \\yourserver or net view /domain:yourdomain
----------------- FROM : ---------------
Michel Toussaint,MCSE
System Administrator
Eonic Systems NV
Mailto:[EMAIL PROTECTED]
Vcard http://www.eonic.com/vcards/mto.vcf
- From Deep Space To Deep Sea -
Web site: http://www.eonic.com
-----------------------------------------
-----Original Message-----
From: Radmacher, Dave ED0 [mailto:[EMAIL PROTECTED]]
Sent: Monday, May 29, 2000 4:37 PM
To: Firewall-1 (E-mail)
Subject: [FW1] Weird NetBIOS Issues with SecuRemote
Well... I am totally out of ideas, it appears that some of the machines that
I have set up with SecuRemote and had working flawlessly for months just
decided to stop working. Now the problem appears to be with NetBIOS. I can
access other resources over SecuRemote (ie Exchange through Outlook) I can
also resolve DNS and WINS names. The problem occurs when I go to browse
Network Neighborhood or map drives. Network Neighborhood is always wrong
(not showing the other machines on the network) and when mapping drives it
says the path can not be found. I *really* hope that someone has an idea
because I am totally fresh out.
Thanks in advance
Dave.
============================================================================
====
To unsubscribe from this mailing list, please see the instructions at
http://www.checkpoint.com/services/mailing.html
============================================================================
====
================================================================================
To unsubscribe from this mailing list, please see the instructions at
http://www.checkpoint.com/services/mailing.html
================================================================================
