DNS Problems

[Guest]

I'm having DNS problems similar to those posted by others. I've tried ALL
the fixes suggested but with no luck.

I have a small 3 computer network, all running xp pro. I have 1 desktop
(desktop-3), another desktop (server-1) and one laptop (laptop-3). The 2
desktops are connected to a wired router that also is DHCP server. The
laptop connects to a wireless router set up as an access point.

Until today, everything worked just fine. I have a number of shares set up
on server-1 which is acting as a file/print server. Suddenly, laptop-3 could
no longer resolve the names on the network. However, desktop-3 can.

All computers can access the internet via a DSL modem attached to the router.

Here's what i know. From the laptop i can:

-I can successfully ping both internal network IP addresses and external
addresses
-I can access the server-1 shares from laptop-3 by choosing Run and enter
the server IP address
-likewise, i can map a network drive entering the IP address and folder name
(e.g. 192.168.1.1\documents)
-it *appears* that all network settings on desktop-3 and laptop-3 are
identical (or as nearly as they can be b/c desktop uses wired connection)

Additonally, i tried using a wired connection on the laptop. I disabled the
wireless connection, and ran cable directly from the laptop to the wired
router that the other 2 computers are connected to. No luck!

As I mentioned at the beginning of this post, I've tried literally all of
the suggestions made by Chuck and some posted by a few others. Nothing seems
to work.

Please, any help is greatly appreciated.

Thanks in advance,

Mark

 

[Guest]

Oh, btw, SP2 installed on all computers.

MJS

 

[Hans-Georg Michna]

I'm having DNS problems similar to those posted by others. I've tried ALL
the fixes suggested but with no luck.

I have a small 3 computer network, all running xp pro. I have 1 desktop
(desktop-3), another desktop (server-1) and one laptop (laptop-3). The 2
desktops are connected to a wired router that also is DHCP server. The
laptop connects to a wireless router set up as an access point.

Mark,

two routers? I hope you are sure that the router functions are
truly disabled in the wireless router. But I guess you are aware
of this.

Additonally, i tried using a wired connection on the laptop. I disabled the
wireless connection, and ran cable directly from the laptop to the wired
router that the other 2 computers are connected to. No luck!

Good idea for testing, because it takes one variable out of the
equation.

Please use http://www.michna.com/kb/wxnet.htm to determine the
solution.

Hans-Georg

 

[Guest]

Hans-Georg,

thanks for the reply. I went to your website and it is a wealth of
knowledge. however, i was still unable to resolve the problem. any other
suggestions?

Thanks,
MJS

 

[Guest]

MJS wrote:

thanks for the reply. I went to your website and it is a wealth of
knowledge. however, i was still unable to resolve the problem. any other
suggestions?

Thanks,
MJS

Install your own DNS server - available free here http://ntcanuck.com/

This WILL work........

 

[Guest]

Yes, I've considered my own DNS. However, what's really bugging me is that
this used to work. In fact it worked for over a year without incident.

Thanks for the suggestions.

MJS

 

[Hans-Georg Michna]

thanks for the reply. I went to your website and it is a wealth of
knowledge. however, i was still unable to resolve the problem. any other
suggestions?

Mark,

oh, that surprises me. I thought this case was not too
difficult.

What did you do?

Hans-Georg

 

[Guest]

i tried:
-repairing winsock
-flushing dns
-uninstall/reinstall TCP/IP
-resetting catalog with: netsh winsock reset catalog
-resetting tcp/ip with:netsh int ip reset c:\netsh.txt
-plus a whole bunch of other stuff that to long to list.

i may be barking up the wrng tree as i don't have a DNS server on my network
(its a peer-to-peer workgroup). know this and that WINS controls name
resolution, i considered that maybe the node names just needed time to
propagate through the network. I left the computers on overnight, but no
luck.

please, any more ideas?

 

[Hans-Georg Michna]

i tried:
-repairing winsock
-flushing dns
-uninstall/reinstall TCP/IP
-resetting catalog with: netsh winsock reset catalog
-resetting tcp/ip with:netsh int ip reset c:\netsh.txt
-plus a whole bunch of other stuff that to long to list.

i may be barking up the wrng tree as i don't have a DNS server on my network
(its a peer-to-peer workgroup). know this and that WINS controls name
resolution, i considered that maybe the node names just needed time to
propagate through the network. I left the computers on overnight, but no
luck.

please, any more ideas?

Mark,

as I see it, you have probably checked at least the first of the
two following checkboxes in http://www.michna.com/kb/wxnet.htm.
My Network Places

[ ] Computers or shares are missing in My Network Places.

[ ] Workgroup is not accessible. Or I observe one of the
following symptoms.
* I cannot access shares on other computers.
* I cannot locate other computers in the workgroup.
* When I double-click the workgroup in My Network Places, I get
the error message: Workgroup is not accessible. You might not
have permission to use this network resource. Contact the
administrator of this server to find out if you have access
permissions.
* I get the error message: Workgroup is not accessible. The list
of servers for this workgroup is not currently available.
(Instead of the word workgroup the name of your workgroup is
displayed.)
<<<

This means that you have been pointed, among a few others, at
the chapters dealing with the computer browser service. What
were the results of following the advice in these chapters?

Hans-Georg

 

[Guest]

Some additional information that I negelected to mention: i can take this
same laptop to another network and it can resolve names just fine. In fact,
i think my troubles started after i had been on this other network (which is
a domain). I didnt log onto the domain, but did access shares via
Run > servername\\sharename.

Thanks again for your help.

 

[Guest]

i tried all of the folloing with no success:

-reset winsock
-reset ip stack
-used third party winsockfix.exe.
-disabled firewall on server (Advanced, and remove the check mark from your
LAN (Local Area Network) interface to allow full local connectivity for all
types of traffic.)
-when i run net view, i get a response that list of servers is unavailable.
-i'm at laptop-3. when i run net view \\laptop-3 i get "there are no
entries in the list"
-i'm at laptop-3. when i run net view \\server-1 i get "system error 53 has
occurred. The network path is not found"
-i verfied computer browser service and all dependancies are set to start
automatically and are running.
-iset editted the registry so the local machine keeps maintains a server
list: MaintainServerList set to "yes".

No of this worked. I just deleted the DhcpNodetype value in the registry
and will now reboot. Hopefully this will work as it is the last item from
your website.

Thanks,

MJS

i tried:
-repairing winsock
-flushing dns
-uninstall/reinstall TCP/IP
-resetting catalog with: netsh winsock reset catalog
-resetting tcp/ip with:netsh int ip reset c:\netsh.txt
-plus a whole bunch of other stuff that to long to list.

i may be barking up the wrng tree as i don't have a DNS server on my network
(its a peer-to-peer workgroup). know this and that WINS controls name
resolution, i considered that maybe the node names just needed time to
propagate through the network. I left the computers on overnight, but no
luck.

please, any more ideas?

Mark,

as I see it, you have probably checked at least the first of the
two following checkboxes in http://www.michna.com/kb/wxnet.htm.
My Network Places

[ ] Computers or shares are missing in My Network Places.

[ ] Workgroup is not accessible. Or I observe one of the
following symptoms.
* I cannot access shares on other computers.
* I cannot locate other computers in the workgroup.
* When I double-click the workgroup in My Network Places, I get
the error message: Workgroup is not accessible. You might not
have permission to use this network resource. Contact the
administrator of this server to find out if you have access
permissions.
* I get the error message: Workgroup is not accessible. The list
of servers for this workgroup is not currently available.
(Instead of the word workgroup the name of your workgroup is
displayed.)
<<<

This means that you have been pointed, among a few others, at
the chapters dealing with the computer browser service. What
were the results of following the advice in these chapters?

Hans-Georg

 

[Guest]

HOORAY!!!!!!!! IT WORKED!!!

After deleting the DHCPNodeType value in the registry and rebooting, the
share names are resolved.

Thanks for such a comprehensive site.

MJS

i tried all of the folloing with no success:

-reset winsock
-reset ip stack
-used third party winsockfix.exe.
-disabled firewall on server (Advanced, and remove the check mark from your
LAN (Local Area Network) interface to allow full local connectivity for all
types of traffic.)
-when i run net view, i get a response that list of servers is unavailable.
-i'm at laptop-3. when i run net view \\laptop-3 i get "there are no
entries in the list"
-i'm at laptop-3. when i run net view \\server-1 i get "system error 53 has
occurred. The network path is not found"
-i verfied computer browser service and all dependancies are set to start
automatically and are running.
-iset editted the registry so the local machine keeps maintains a server
list: MaintainServerList set to "yes".

No of this worked. I just deleted the DhcpNodetype value in the registry
and will now reboot. Hopefully this will work as it is the last item from
your website.

Thanks,

MJS

i tried:
-repairing winsock
-flushing dns
-uninstall/reinstall TCP/IP
-resetting catalog with: netsh winsock reset catalog
-resetting tcp/ip with:netsh int ip reset c:\netsh.txt
-plus a whole bunch of other stuff that to long to list.

i may be barking up the wrng tree as i don't have a DNS server on my network
(its a peer-to-peer workgroup). know this and that WINS controls name
resolution, i considered that maybe the node names just needed time to
propagate through the network. I left the computers on overnight, but no
luck.

please, any more ideas?

Mark,

as I see it, you have probably checked at least the first of the
two following checkboxes in http://www.michna.com/kb/wxnet.htm.
My Network Places

[ ] Computers or shares are missing in My Network Places.

[ ] Workgroup is not accessible. Or I observe one of the
following symptoms.
* I cannot access shares on other computers.
* I cannot locate other computers in the workgroup.
* When I double-click the workgroup in My Network Places, I get
the error message: Workgroup is not accessible. You might not
have permission to use this network resource. Contact the
administrator of this server to find out if you have access
permissions.
* I get the error message: Workgroup is not accessible. The list
of servers for this workgroup is not currently available.
(Instead of the word workgroup the name of your workgroup is
displayed.)
<<<

This means that you have been pointed, among a few others, at
the chapters dealing with the computer browser service. What
were the results of following the advice in these chapters?

Hans-Georg

 

[Hans-Georg Michna]

HOORAY!!!!!!!! IT WORKED!!!

After deleting the DHCPNodeType value in the registry and rebooting, the
share names are resolved.

Thanks for such a comprehensive site.

Mark,

well, that's good news.

I'm a bit unhappy myself about the long list of countermeasures,
but I have not found any better way to determine the precise
cause of the problems. I'm pondering the thought of writing an
analysis program, but that's a lot of work. I may never find the
time.

Hans-Georg

 

[Hans-Georg Michna]

Some additional information that I negelected to mention: i can take this
same laptop to another network and it can resolve names just fine. In fact,
i think my troubles started after i had been on this other network (which is
a domain). I didnt log onto the domain, but did access shares via
Run > servername\\sharename.

Mark,

with some luck you may have hit upon a hint worth that could
save millions of dollars, given that the problem you had is
rather widespread and certainly causes a huge damage.

Could it be that Windows itself changes the node type when a
computer is introduced into a network that has a WINS server
running?

That would make some sense, because the P-t-P node type is the
most efficient when a WINS server is present. However, it would
cause the terrible headache you have experienced when the
computer is then taken back into a network without a WINS server
and the node type not set back.

I will try to follow up on this information. Meanwhile you could
do the world a favor and try to find out whether that domain
controller has its WINS server enabled, which is fairly likely.

Unfortunately neither you or me will get a cent of the millions
of dollars we would save the world economy if we managed to
solve this problem. -)

Hans-Georg