Networking Problem

Tech-Archive recommends: Fix windows errors by optimizing your registry

I have a network with four PCs. Two of them are brand new running XP SP2.
One of the tow of them is completely accessible from the other computers on
the network. The other one can not even be pinged by the other computers on
the network, yet the computer that can not be accessed has no problem
accessing the internet. The computer that can not be accessed does appear in
list of network computers but attempts to connect to that machine result in
showing no shared resources or "you do not have the rights..." to conenct to
that machine. File sharing is turned on. I have already done the following:
"enable incoming ICMP Echo messages for a specific connection from the ICMP
tab of the Advanced Network Settings for a selected connection, available
from the Advanced tab of the Windows Firewall component of Control Panel"

I have tried switching routers - no success.

The only weird thing is that the unaccessilble computere has an ip address
of 192.xxx.x.110 while the other computers have 192.xxx.x.107/108/109. Is
there a reason to think that .110 is causing the problem?

Thank you all in advance.

.

Relevant Pages

  • Re: The Hard Problem for Behaviorists
    ... correct low level abstractions to define the operation of the brain with - ... Do you not know how computers work? ... you can think of this type of network like you ... when you drop a marble in hole X1, ...
    (sci.cognitive)
  • 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)
  • Re: {workgroup}"...is not accessible" after removing NWLINK
    ... I generally reboot the machine whenever I make network ... >problem is a browse service that won?t run on the XP machine using the TCP/IP ... >?The browser has forced an election on network ... >> computer, and one, or preferably two, of the Windows 98 computers. ...
    (microsoft.public.windowsxp.network_web)
  • Re: Help with 070-217
    ... The network contains 25,000 computers. ... > single Windows 2000 domain named research.contoso.com. ... > Server computers that are configured as domain controllers. ...
    (microsoft.public.cert.exam.mcse)
  • RE: Help with 070-217
    ... The network contains 25,000 computers. ... > single Windows 2000 domain named research.contoso.com. ... > Server computers that are configured as domain controllers. ...
    (microsoft.public.cert.exam.mcse)