Displaying 2 results from an estimated 2 matches for "our_adm".
Did you mean:
dru_adm
2004 Nov 10
0
nmblookup failing
...erver is named 'fileserver1' and its IP address is
155.2.196.251 for the purpose of this email. Here's some test
results and my smb.conf follows. Thanks in advance for the help!
* nslookup and ping work in both directions
* #smbclient //fileserver/test -U<user>
Password:
Domain=[OUR_ADM] OS=[Unix] Server=[Samba 3.0.8]
smb: \> --> I can browse the share
* #nmblookup -B fileserver1 __SAMBA__
added interface ip=155.2.196.251 bcast=152.2.255.255 nmask=255.255.0.0
querying __SAMBA__ on 127.0.0.1
Got a positive name query response from 127.0.0.1 ( 155.2.196.251 )
155.2.196.25...
2004 Nov 10
0
Initial install - networking problem
...me and have a problem with
name resolution on my test client. Samba 3.0.8 is installed on
a RHES system named 'fileserver1 (.our.xxx.edu)'. The clients
are Windows 2000 and XP systems. This is a subnet that is part of
a larger campus network. There is no Domain, just a workgroup
called 'our_adm'. I have a very simple smb.conf
file for testing. When I look at the client Network Neighborhood I can
see 'fileserver1' but when I click on it, I get "\\fileserver1
is not accessible. The network path was not found".
I included the name and ip address of the client in the
sa...