Re: SAMBA configuration - Machine name

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



William Hooper wrote:
Quoting the FAQ on the nu2.nu page:

Q: I've loaded the network drivers (tcp), all OK. When I use "net use f:
\\192.168.10.15\c$" I get "Error 53: The computer name specified in the
network path cannot be located".

A: You cannot use IP-based machine names when using Microsoft client. You
need to enter the real machine name: "net use f: \\servername\c$".

I'm not using IP addresses in the net commands.

I think the other post about opening port 137 for UDP has merit.  The only
time I've had to mess with this I've had a fully functioning DNS server to
resolve the names.


AIUI, the names used here have NOTHING to do with the IP names
whatsoever, nor with DNS. They have to do with SMB, which is
entirely different. Or, to put it another way, these names get
used when the transport is NETBEUI rather than TCP/IP. So they
can't be tied to TCP/IP or even just IP.

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!


[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux