Andy Green wrote:
Mike McCarty wrote:
I've read all the help available on SAMBA available from GNOME.
I've got an MSDOS (6.0) machine with MSCLIENT over TCP/IP running
on it, and a Fedora Core 2 machine, using static IP addresses.
Each machine can successfully ping the other. But when I try
to establish a share connection from the MSDOS machine to the
Linux machine, the MSDOS machine cannot find the Linux machine.
JMCCARTY@AMD586 Q:\NET> net use * \\presario\tmp
[several second pause]
Error 53: The computer name specified in the network path cannot
be located.
Not much of a Samba user, but when I stuggled through getting it working
I found Swat was helpful. Some things only worked properly when
windbindd was running, check
service winbind status
# service winbind status
winbindd is stopped
# service winbind start
Starting Winbind services: [ OK ]
Ok, that may have been part of the problem. But so far no change.
Also make sure you poked some holes in your firewall
iptables -I INPUT -p tcp --dport 137:139 -j ACCEPT
iptables -I INPUT -p tcp --dport 445 -j ACCEPT
If it still didn't work I would fire up tcpdump and look to see if the
Linux box is broadcasting its existence and name.
Well, did that, and it still won't work. I run tcpdump on my Linux
box (I guess it would receive it's own broadcasts)
# tcpdump
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes
14:33:19.813047 IP router.1900 > 239.255.255.250.1900: UDP, length 255
14:33:19.814104 IP router.1900 > 239.255.255.250.1900: UDP, length 273
14:33:19.814377 IP 172.17.205.79.32866 >
dns1.hstntx.sbcglobal.net.domain: 34300+ PTR?
250.255.255.239.in-addr.arpa. (46)
14:33:19.815211 IP router.1900 > 239.255.255.250.1900: UDP, length 327
14:33:19.818405 IP router.1900 > 239.255.255.250.1900: UDP, length 319
14:33:19.822840 IP router.1900 > 239.255.255.250.1900: UDP, length 249
14:33:19.823936 IP router.1900 > 239.255.255.250.1900: UDP, length 291
14:33:19.827165 IP router.1900 > 239.255.255.250.1900: UDP, length 323
14:33:19.831890 IP router.1900 > 239.255.255.250.1900: UDP, length 269
14:33:19.833005 IP router.1900 > 239.255.255.250.1900: UDP, length 321
14:33:19.836184 IP router.1900 > 239.255.255.250.1900: UDP, length 315
14:33:19.893608 IP dns1.hstntx.sbcglobal.net.domain >
172.17.205.79.32866: 34300 NXDomain 0/1/0 (103)
^^^^^^^^^^^^^ Linux machine
14:33:19.894420 IP 172.17.205.79.32866 >
dns1.hstntx.sbcglobal.net.domain: 13696+ PTR?
201.11.164.151.in-addr.arpa. (45)
14:33:19.950079 IP dns1.hstntx.sbcglobal.net.domain >
172.17.205.79.32866: 13696* 1/1/1 (123)
^^^^^^^^^^^^^ Linux machine
14:33:19.950549 IP 172.17.205.79.32866 >
dns1.hstntx.sbcglobal.net.domain: 8012+ PTR?
79.205.17.172.in-addr.arpa. (44)
14:33:20.006866 IP dns1.hstntx.sbcglobal.net.domain >
172.17.205.79.32866: 8012 NXDomain* 0/1/0 (100)
^^^^^^^^^^^^^ Linux machine
I don't see anything in there that looks like this machine
broadcasting itself.
Mike
--
p="p=%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,p,34);}
This message made from 100% recycled bits.
You have found the bank of Larn.
I can explain it for you, but I can't understand it for you.
I speak only for myself, and I am unanimous in that!
