Re: Connection-specific DNS suffix

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Richard G. Harper (rgharper_at_email.com)
Date: 05/04/04


Date: Mon, 3 May 2004 21:31:29 -0400

I hate to say it but you've run me clean out of ideas. Hopefully someone
else has a thought, otherwise ...

-- 
Richard G. Harper [MVP Win9x]  rgharper@email.com
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all.  Private mail is usually not replied to.
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm
"Peter" <moogk@notsympatico.ca> wrote in message 
news:%23HfUZ2WMEHA.3420@TK2MSFTNGP11.phx.gbl...
> Thanks again Richard.
>
> I completely removed the firewalls - it did not help.
> I tried a different router and replaced the NIC's - it did not help.
> It does seem bizzare.  For example, the "desktop" can access the "laptop"
> but if I run Net View on the "desktop" only the "desktop" is listed.  The
> "laptop" cannot access the "desktop" but if I run Net View on the "laptop"
> both computers are listed.
> Although the "desktop" can access the "laptop", it can't ping it by name
> (--- could not find host).
>
> Perhaps the operating system has an unresolvable problem.  It might be 
> time
> to bite the bullet and make a clean install of the "desktop".
>
> PJ
>
>
> "Richard G. Harper" <rgharper@email.com> wrote in message
> news:er8AcHLMEHA.2456@TK2MSFTNGP12.phx.gbl...
>> Thank you - though the details make the problem more puzzling instead of
>> less.
>>
>> You say you have no firewalls "active" on either PC - do you have 
>> anything
>> other than the Windows XP firewall on either PC?  If so you may need to
>> fully uninstall the firewall for a true test.
>>
>> The only other thing I can think of would be to check router firewall
>> settings and make sure you haven't accidentally blocked access from "B" 
>> to
>> "A" in its settings.
>>
>> The fact that "A" can see and access "B" is an almost 100% certain sign
> that
>> you have your network fully functional and correctly configured.  The
> usual
>> cause for not being able to access the other direction is a firewall
>> problem.
>>
>> -- 
>> Richard G. Harper [MVP Win9x]  rgharper@email.com
>> * PLEASE post all messages and replies in the newsgroups
>> * for the benefit of all.  Private mail is usually not replied to.
>> * HELP us help YOU ... http://www.dts-l.org/goodpost.htm
>>
>>
>> "Peter" <moogk@notsympatico.ca> wrote in message
>> news:e7IO7$DMEHA.3712@TK2MSFTNGP10.phx.gbl...
>> > Thanks Richard.
>> >
>> > The computers get their IP addresses automatically through a router.
>> > The addresses are assigned by the router and are in the same range.
>> > The network worked well for a long time.  I'm not aware of having made
> any
>> > changes prior to the problem starting.
>> > Computer A has full access to computers B but B cannot even ping A.
>> > There are no firewalls active.
>> > I ran nbtstat and netstat with most switches but am not savy enough to
> get
>> > a
>> > clear message from the results.
>> > I don't want to attach the whole set of results.  Which, if any, would
>> > help
>> > with the diagnosis?
>> > PJ
>> >
>> > "Richard G. Harper" <rgharper@email.com> wrote in message
>> > news:e9z2snDMEHA.268@TK2MSFTNGP11.phx.gbl...
>> >> Need waaayy more details to try to diagnose this.  For example:
>> >>
>> >> - How are these computers getting their IP addresses?
>> >> - Are the two addresses in the same range?
>> >> - Is this a new problem or did it just start?  Did the network work at
>> > some
>> >> point?
>> >>
>> >> -- 
>> >> Richard G. Harper [MVP Win9x]  rgharper@email.com
>> >> * PLEASE post all messages and replies in the newsgroups
>> >> * for the benefit of all.  Private mail is usually not replied to.
>> >> * HELP us help YOU ... http://www.dts-l.org/goodpost.htm
>> >>
>> >>
>> >> "Peter" <notmoogk@sympatico.ca> wrote in message
>> >> news:uAzljJDMEHA.2500@TK2MSFTNGP12.phx.gbl...
>> >> > When I run ipconfig /all, the entry for "connection-specific DNS
>> >> > suffix"
>> >> is
>> >> > blank on one of two networked XP machines.  It happens that this
>> >> particular
>> >> > machine can no longer be accessed (or even pinged) by the other.
>> >> > Is the blank suffix problem just a reporting error or does it
> indicate
>> > an
>> >> > operational problem? (I know there is a hopfix available, for which
>> >> > Microsoft may or may not decide to charge but I don't want to spend
> the
>> >> day
>> >> > on the phone if it is not really a useful exercise).
>> >> > PJ
>> >> >
>> >> >
>> >>
>> >>
>> >
>> >
>>
>>
>
> 


Relevant Pages

  • Re: Simple Printer Sharing/Networking Question
    ... And all 3 desktop computers are running Windows XP Pro ... We have turned on sharing for the network printers (in association with this ... caused by 1) a misconfigured firewall or overlooked firewall (including ...
    (microsoft.public.windowsxp.network_web)
  • Re: Networks : Workgroups and Domains. How Do I Use Them?
    ... in My Network Places, it may take some time for a network resource to show up. ... all of the computers must be on the same subnet. ... it depends on whether you have Simple File Sharing enabled or disabled. ... Problems sharing files between computers on a network are generally caused by 1) a misconfigured firewall or overlooked firewall; or 2) inadvertently running two firewalls such as the built-in Windows Firewall and a third-party firewall; and/or 3) not having identical user accounts and passwords on all Workgroup machines; 4) trying to create shares where the operating system does not permit it. ...
    (microsoft.public.windowsxp.network_web)
  • Re: Sharing a printer
    ... Here are general network troubleshooting steps. ... Problems sharing files between computers on a network are generally caused by 1) a misconfigured firewall or overlooked firewall; or 2) inadvertently running two firewalls such as the built-in Windows Firewall and a third-party firewall; and/or 3) not having identical user accounts and passwords on all Workgroup machines; 4) trying to create shares where the operating system does not permit it. ... On the assumption that you in fact do have a router that connects to the Internet and that your computers then connect to the router, then if you think that you have one IP for multiple computers then you probably are using a website tool such as http://whatismyip.com/ That shows the your public IP address -- the one that the rest of the world sees. ...
    (microsoft.public.windowsxp.network_web)
  • Re: Home Network with Vista & XP
    ... The 3 computers are: 1 laptop running XP Pro, 1 laptop running Vista Home Premium, and 1 desktop running XP Home. ... the vista laptop can see all terminals on the work group but the xp terminals cannot see the vista terminal in the network. ... Problems sharing files between computers on a network are generally caused by 1) a misconfigured firewall or overlooked firewall; or 2) inadvertently running two firewalls such as the built-in Windows Firewall and a third-party firewall; and/or 3) not having identical user accounts and passwords on all Workgroup machines; 4) trying to create shares where the operating system does not permit it. ...
    (microsoft.public.windowsxp.network_web)
  • Re: Networks : Workgroups and Domains. How Do I Use Them?
    ... I think the problem is from my lack of understanding whether these machines are together as a workgroup or domain. ... If I want to configure solely for a workgroup network, then I would think I do not need to provide a domain name, and vice versa for a domain network. ... It's not clear whether any of your computers is running Windows 2000 *Server.* If not, you don't have a "domain" and shouldn't be using domain names. ... Problems sharing files between computers on a network are generally caused by 1) a misconfigured firewall or overlooked firewall; or 2) inadvertently running two firewalls such as the built-in Windows Firewall and a third-party firewall; and/or 3) not having identical user accounts and passwords on all Workgroup machines; 4) trying to create shares where the operating system does not permit it. ...
    (microsoft.public.windowsxp.network_web)