Excellent.
Use of the NBTStat utility, under those circumstances, would have failed to provide NetBIOS
information while a ping would work.
Hopefully you played with this command and know how to use it as a NetBIOS level diagnostic
tool.
--
Dave
| Dave,
|
| I fixed the problem, I noted that under the advanced tcp/ip settings under
| the WINS tab, Netbios over IP was disabled, the problem has been resolved.
|
| Thanks for your input,
|
| Jordan
|
| | > When placed in the LMhosts file, the #PRE loads the IP address, host name
| and Domain into a
| > cache. Therefore it doesn't have to resolve a name to IP or Domain, the
| workstation "knows"
| > the info already.
| >
| > LMHosts == LAN Manager Hosts Table, a NetBIOS table use to specifically
| identify NetBIOS
| > names to IP addresses and Domains in MS Networking environments.
| >
| > --
| > Dave
| >
| >
| >
| >
| > | > | And what exactly does the
| > |
| > | 192.168.1.X SERVER-NAME #PRE #DOM:AD_DOMAIN_NAME
| > |
| > | command do? just authorize yourself in active directory??
| > |
| > |
| > | | > | > Replies are inline...
| > | >
| > | > | > | > | The workstations are on the same lan segment
| > | > |
| > | > | The DC is on the same LAN
| > | > |
| > | > | I am not using wins..
| > | > |
| > | > | I have not inputed an entry in the lmhosts file, should I? and if so
| how
| > | > | would i go about that?
| > | > |
| > | >
| > | > Yes -- use on workstation
| > | > 192.168.1.X SERVER-NAME #PRE #DOM:AD_DOMAIN_NAME
| > | >
| > | > | I have not tried that nbtstat command, what does it do????
| > | >
| > | > Execute the following for syntax...
| > | > NBTSTAT /?
| > | >
| > | > Ping uses TCP/IP to check if a host is "live".
| > | >
| > | > MS Networking use NetBIOS over IP so you use NBTSTAT to find if the
| two
| > | platforms can
| > | > communicate using NetBIOS.
| > | >
| > | > Dave
| > | >
| > | >
| > | >
| > |
| > |
| >
| >
|
|
