A Windows XP help forum. PCbanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » PCbanter forum » Windows 10 » Windows 10 Help Forum
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

Noob networking question - why does \\DESKTOP\pubshare\readthis.txt not work but \\192.168.1.5\pubshare\readthis.txt work just fine?



 
 
Thread Tools Rate Thread Display Modes
  #1  
Old July 13th 18, 12:45 AM posted to alt.comp.os.windows-10
Char Jackson
external usenet poster
 
Posts: 9,574
Default Noob networking question - why does \\DESKTOP\pubshare\readthis.txt not work but \\192.168.1.5\pubshare\readthis.txt work just fine?

On Thu, 12 Jul 2018 18:11:02 -0000 (UTC), Arlen Holder
wrote:

On DESKTOP: (which is the machine that isn't sharing its netBIOS name)
C:\ nslookup
Default Server: google-public-dns-a.google.com
On TOPDESK: (which is the machine that is not seeing the netBIOS name)
C:\ nslookup
Default Sserver: UnKnown
Address: 192.168.1.1

When you run that command on your typical home network, which type of
response do you see?


nslookup is the ultralite cousin of dig, a much more powerful DNS query
command available for Windows, Linux, and possibly others. Having said
that, when you run nslookup without any arguments you place it into its
interactive mode. It prints the default DNS server info and then waits
for you to issue an actual DNS query.

You can override the default DNS server for one or more DNS queries by
simply specifying a different DNS server, like so:

prompt nslookup
# puts the nslookup program into interactive mode, waiting for
additional instructions.

prompt server 8.8.4.4
# tells nslookup to use 8.8.4.4 as the authoritative DNS server for all
subsequent DNS queries, until you either set a new DNS server or you
exit the nslookup program with Ctrl-c. Specifying a DNS server here has
no effect on your Windows configuration. You're simply telling nslookup
to use a non-default server for its name resolutions.

prompt www.msn.com
# still in nslookup's interactive mode, entering a fully qualified
domain name (FQDN) tells nslookup to use the previously specified DNS
server to resolve the hostname into an IP address. nslookup performs the
query and prints the results.

prompt Ctrl-c
# press and hold the control key, press the c key, release both keys
# this exits the nslookup interactive mode and returns you to the
Command Prompt

****

Since you seem to be using nslookup to display your default DNS server,
there are other ways to do that that are arguably more direct, such as
parsing the output of "ipconfig /all", but nslookup works also.

As I think you surmised in later posts, what you're seeing above is
simply the fact that one PC is configured to use 8.8.8.8 as its DNS
server while the other points at your 192.168.1.1 device, which most
likely acts as a DNS Forwarder. Those settings have nothing to do with
your stated issue.

Ads
 




Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off






All times are GMT +1. The time now is 08:48 AM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2018, Jelsoft Enterprises Ltd.
Copyright 2004-2018 PCbanter.
The comments are property of their posters.