View Single Post
  #4 (permalink)  
Old 07-07-2008, 10:26 PM
Brian A.
 
Posts: n/a
Re: The network path was not found
"Enzo Fiorillo" <efiori@hotmail.com> wrote in message
news:%23$CzB793IHA.2064@TK2MSFTNGP02.phx.gbl...
I fail to open a second pc on my small network. The error message is,
'The network path was not found".

How can i fix it?

Thanks,

Enzo Fiorillo

> "Brian A." <gonefish'n@afarawaylake> wrote in message
> news:eledih$3IHA.3480@TK2MSFTNGP03.phx.gbl...
>> "Enzo Fiorillo" <efiori@hotmail.com> wrote in message
>> news:%23$CzB793IHA.2064@TK2MSFTNGP02.phx.gbl...
>> I fail to open a second pc on my small network. The error message is,
>> 'The network path was not found".
>>
>> How can i fix it?
>>
>> Thanks,
>>
>> Enzo Fiorillo
>>
>> Right click My Network Places on the Desktop.
>> Click Properties.
>> Right click Local Area Connection.
>> Click Properties.
>>
>> Under "This connection uses....."
>> Click "Client for MS Networks".
>> Click Properties.
>> Select "Windows Locator" from the dropdown box, if disabled skip.
>> Click Ok.
>>
>> Scroll to and select Internet Protocol (TCP/IP).
>> Click Properties.
>>
>> Under the General tab make sure "Obtain an IP address automatically" is
>> selected.
>> Click the Advanced button.
>>
>> Under the DNS tab:
>> Selected "Append Primary and Parent DNS suffixes.
>> Register this connections address in DNS"
>>
>> Under the WINS tab > NetBIOS:
>> Selected Default.
>> Ok out of MNP.
>> Reboot if required.
>>
>> Test connectivity:
>> Open a command prompt, click Start > Run, type in: cmd and press Enter.
>> At the prompt type each command below and press Enter after each.
>> **Note: Command noted by =, Space noted by ^. Do not type the = or ^.
>>
>> =ping ^ 192.168.1.1 *Routers IP, change as necessary.
>> If it times out then there is no communication between the router and
>> machine.
>> If not then the machine communicates with the router.
>>
>> =ping ^ google.com
>> If it times out then there is no connection to the net.
>> If not then net connection is established and all is well.
>>
>> ping 127.0.0.1
>> If it fails it may be a TCP/IP stack problem.
>>
>> Ping each computer from the other using the UNC:
>> =ping ^ computername
>> If it fails either way there's an IP or Name resolution problem.
>>
>> If pinging times out on any address, check if the machines IP is correct
>> along with other settings.
>> = ipconfig ^ /all
>> If anything isn't correct, at the prompt type and press Enter after each
>> command:
>>
>> =ipconfig ^ /release
>> =ipconfig ^ /flushdns
>> =ipconfig ^ /renew
>> =ipconfig ^ /registerdns
>> =exit
>> If that fails reopen the command prompt, run /release and /flushdns only and
>> exit.
>>
>> Shut down the machine(s).
>> Pull the power from the router.
>> Pull the power from the modem.
>> Wait approx 30 secs.
>> Apply power to the modem and wait for it to finish synchronizing with the
>> cable.
>> Apply power to the router and wait for it to finish synchronizing with the
>> modem.
>> Power up the machine(s).
>> The machine(s) should now be assigned a new IP from the router.
>> Run ipconfig or attempt net connection to test.
>>
>>
>> --
>>
>>
>> Brian A. Sesko { MS MVP_Windows Desktop User Experience }
>> Conflicts start where information lacks.
>> http://basconotw.mvps.org/
>>
>> Suggested posting do's/don'ts: http://dts-l.com/goodpost.htm
>> How to ask a question: http://support.microsoft.com/kb/555375
>>
>>


"Enzo Fiorillo" <efiori@hotmail.com> wrote in message
news:u02WwRH4IHA.3624@TK2MSFTNGP05.phx.gbl...
> Dear Brian, thanks for your message.
> I have 2 pcs in a network, the pc1 is connected to internet.
> They run in a network with a worgroup named XXX
> I can see the pc1 and its files from pc2, but from pc2 i can not see pc1.
> I run all the tests you suggest me.
> The test which fail was ping from pc1 to pc2 using UNC. Pc2 to pc1 was
> succesfull.
> The message was "The operation failed as no adapter is in the state permisible
> from this operation"
> Have you some other hint?
> Thanks
>
>


Please provide your exact network setup, each PC's OS, how they are connected,
network properties components/protocols, router manufacturer/make/model,
firewall, etc.

--


Brian A. Sesko { MS MVP_Windows Desktop User Experience }
Conflicts start where information lacks.
http://basconotw.mvps.org/

Suggested posting do's/don'ts: http://dts-l.com/goodpost.htm
How to ask a question: http://support.microsoft.com/kb/555375




Reply With Quote