![]() This is an open-source TCP and UDP port scanner, which scans the IP address range you choose for a predefined list of commonly used ports. You can also add the app to the Start menu to see the current IP on a live tile. The app also displays a Windows notification when the IP changes. Or maybe you’d like to keep a log in case you need it for future audits.Īfter opening the app, you see a log of all the Internet IPs you’ve connected through, which includes the dates and times. Perhaps you need to know your public IP for security reasons when accessing remote servers. I can even go: "wbinfo -N venus" (where venus is a Windows UNC pc host name on the LAN), and it responds: "192.168.0.12" (which is venus' IP address).This is a very simple app that can be quite useful if you want to track the internet (WAN) IP addresses you connect through. To start winbindd, I also have to go: "winbindd", and then the windbind daemon starts and stays up. Some more info: Afer installing samba 3.3.2, smbd and nmbd do not start on their own, and I have to go: "smb start" - then they start fine. "ssh: Could not resolve hostname venus: Name or service not known",Īnd in: ffp/var/log/samba/log.winbindd it says again: " (where a.txt is the file I'd like to copy), it says: Rsync -v "venus:e/my Documents/Temp/a.txt. When I try to copy a file from the Windows PC to the NAS, going: Request_len_recv: Invalid request size received: 1844 (expected 2096)" "winbindd/winbindd.c:request_len_recv(616) I can even go: "wbinfo -N venus" (where venus is a Windows UNC pc host name on the LAN), and it responds: "192.168.0.12" (which is venus' IP address).īut, when I go: "ping venus", it says: "ping: bad address: venus", and in the log file: ffp/var/log/samba/log.winbindd I have installed samba version 3.3.2, using funpkg. If the DNS server cannot resolve the name locally it forwards the request "up" the chain to another DNS server (typically the DNS server of your ISP) for resolution, then caches that lookup (assuming it is a caching DNS server) for a period of time to make future lookups faster.Įxperts: thank you for your help so far. Other clients then make a lookup request to the DNS server sending the host name and get an IP address in return. As far as I know these are your only options.įor a DNS server to work properly with dynamic IP assignments, the CLIENT system must broadcast an IP lease request via a DHCP broadcast, then it must update the DNS server with its host name and assigned/leased address. Then you can either use the IP addresses, modify the hosts file or install and configure a true DNS server. Since your network is small there is no reason not to assign static IP addresses instead of using DHCP assigned addresses. To do what you want you need to run a REAL DNS server or modify the HOSTS file. Windows systems "find" each other through a variety of means. A DNS server provides host name resolution (IP lookup). The DHCP server just assigns IP addresses from a table but does not perform all the functions of a DHCP server. NAS = DLink DNS-323 = Network Attached StorageĭHCP Server = Dynamic Host Control Protocol Server ![]() Unfortunately, similarities in naming of items I think is confusing you.įor one thing, a DNS server is NOT your hardware DNS323 (NAS) - unless you install and configure DNS server software on it of course - not there by default. So it seems that Samba is up and working fine on the DNS-323, serving as the master browser.īut how do I refer to the Windows PC's by name, from the DNS-323? On "Mars", going: nbtstat -a dlink-85ab12 There is also a router (whose IP address is: 192.168.0.1) serving as the Internet Gateway for the entire SOHO network, also serving as the DHCP server and DNS resolver.ģ. The Windows PCs can access the shared HDDs on the DNS-323 fine.Ģ. In other words: in the Telnet shell, when I go: "ping Venus" or "ping mars" is says: bad address: venus, "UNC names"), without writing an explicit /etc/hosts file. My question is: how do I refer to the Windows PCs from the DNS-323 box, using their share names (aka (It shows on the network as: "dlink-85ab12") a DNS-323 running ffp 0.5 that I'm accessing via Telnet. A WinXP SP2 pc (let's call it "Venus"), (whose IP address is: 192.168.0.50)Ģ. I have a small home Windows network, comprising:ġ. Hi experts - I hope you can help me with this (possibly trivial) question (I think it's basic Samba):
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |