Archived from groups: microsoft.public.win2000.dns (
More info?)
"bob" <not@not.not> wrote in message
news:Ry4Vd.20431$Q47.10246@bignews5.bellsouth.net...
> Herb Martin wrote:
>
> > Show the IPConfig /all for at a working machine.
> > (for comparison)
>
> >>>>>>>>>>>>
>
> Windows 2000 IP Configuration
>
> Host Name . . . . . . . . . . . . : LEO
> Primary DNS Suffix . . . . . . . :
> Node Type . . . . . . . . . . . . : Hybrid
> IP Routing Enabled. . . . . . . . : No
> WINS Proxy Enabled. . . . . . . . : No
>
>
> Ethernet adapter Local Area Connection:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network
Connection
> Physical Address. . . . . . . . . : 00-08-74-B4-35-95
> DHCP Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 192.168.0.12
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.0.252
> DNS Servers . . . . . . . . . . . : 192.168.0.252
Ok, the working machine (above here) uses the
same DNS server as the failing machine.
> > What happens when you perform NSlookup (from
> > the client directly)?
> > nslookup www.google.com
> > ...and...
> > nslookup www.google.com
> > (past results from both)
>
> I don't see any difference between these commands.
Sorry. I left off the address for some (silly reason).
Second one should have been:
nslookup www.google.com 192.168.0.252
....but it isn't likely to be different.
> I posted the results two posts ago, but I did it again:
That post snippet was confused and looked like it might
be incomplete (due to editing.)
> Can't find server name for address 192.168.0.252: No response from
> server
> Default servers are not available
> Server: Unknown
> Address: 192.168.0.252
Everything above for NSLookup is irrelevent
except that it confirms we are using the same
DNS server ("Can't find name..." is a bogus
error from NSLookup's funky practices.)
It's the following line that matters:
> UnKnown can't find www.google.com: No response from server
Ok it fails -- I should have given you this
(following) line to try as the same time:
That by the way LOOKS like your DNS server
answered but couldn't resolve Google, not that
your server failed to answer.
> The lines with *** don't redirect, so I had to type them in.
I removed those but you can just COPY them from the screen
with the select AND paste them in.
So let's try this:
nslookup -time=20 www.google.com 192.168.0.252
(long timeout to make sure it isn't time sensitive)
And this:
nslookup www.learnquick.com 216.21.234.71
(can't be yahoo because that server won't resolve
just any zone for you.)
If the latter works, then you station is resolving DNS
and the problem is at the Linux router -- some kind
of filter or something odd about it's DNS server.
> > What firewalls are you running on this machine?
> > (Norton, etc?)
>
> No software firewall. Norton AV 2002 is installed, and has been since
2002.
That would be my main suspect then.
> >>It's just 5 PCs and a printer plugged into a switch. The PCs are
> >>assigned ip addresses in the 192.160.0.x range. (No DHCP, No WINS). The
> >>switch is plugged into the firewall. The firewall is plugged into the
> >>DSL router/modem.
> >
> >
> > Were the above true that would be your problem
> > (192.160.0.x is NOT your range) but it is likely
> > a type.
> >
> > IP Address. . . . . . . . . . . . : 192.168.0.5
> > Subnet Mask . . . . . . . . . . . : 255.255.255.0
> > Default Gateway . . . . . . . . . : 192.168.0.252
> > DNS Servers . . . . . . . . . . . : 192.168.0.252
> >
>
> Yes, a typo = 192.168.0.x, not 192.160.0.x
>
> For some reason the output from ipconfig /all reports "Hybrid" on this
> machine. Three of the others are also hybrid, while the final machine is
> broadcast. DHCP is not enabled on the Linux box.
That's odd especially if you didn't leave out
any lines (that's why I don't like for you to type
them in--adds uncertainty) since it doesn't show
a WINS server line.
This implies someone has messed with the
registry or the NICs have a WINS server listed
but that it cannot be contacted (because it doesn't
exist?)
But again it is unrelated to your real problem unless
it is an indication of these machines have been
hacked (not necessarily in a bad way.)
> I assume that it's the default value, because I didn't set it.
Not unless there is a WINS server listed.
> On the machine that can't seem to resolve names into IP addresses, I
> can't print. The printer is a standard netowrk printer.
There is no "standard" so that is meaningless but
I presume you mean an IP printer attached directly
to the network.
And the "can't print" report is near meaningless
unless you try to connect by name and IP and say
precisely what the errors are.
Can you ping the printer? (Always try ping by
both name and IP and specify which works...)
> The printer
> works fine (I can print from the other machines), and I haven't changed
> any settings on the PC that now can't print.
>
> On the other hand, the PC with the problems is able to navigate to the
> other computers on the network by name -- for example if I click on
> network neighborhood, I can see the other machines and double click on
> them and open their shared folders.
That is probably due to NetBIOS name resolution
which in your case is broadcast based.
If the Printer is not a "Windows" machine it would
not respond to NetBIOS and so would only be available
by IP and not by name since you have no internal DNS
resolution (it appears.)
C-ServerNameGoesHere
Facebook
Twitter
Instagram