3 PCs networked-1 on line & 1 not Help!

[Brian A.]

I have now carried out the above when the problem is there.
I did make a mistake on one line so had to repeat that line
09/03/2009 7:43:02.37 DESKTOP


Windows IP Configuration



Host Name . . . . . . . . . . . . : DESKTOP

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Mixed

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No



Ethernet adapter Local Area Connection:



Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network
Connection

Physical Address. . . . . . . . . : 00-16-76-60-83-3D

Dhcp Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 192.168.1.11

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.1.1

DHCP Server . . . . . . . . . . . : 192.168.1.1

DNS Servers . . . . . . . . . . . : 192.168.1.1

Lease Obtained. . . . . . . . . . : 09 March 2009 06:16:22

Lease Expires . . . . . . . . . . : 10 March 2009 06:16:22



Pinging 192.168.1.1 with 32 bytes of data:



Request timed out.

Request timed out.

Request timed out.

Request timed out.



Ping statistics for 192.168.1.1:

Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

Ping request could not find host www.google.com. Please check the name and
try again.

Since pinging the gateway (192.168.1.1) times out, there is no
communication between the PC and the router. As you mentioned in your first
post you could connect with the laptop but not with the PC, that would
suggest the network adapter and/or cable may be degraded. However you only
tested the PC and not the laptop when the problem last occurred. You Need
to Test Both the PC and laptop when the problem occurs to properly find out
if it is only prevalent to the PC or not.


--

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

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

 

[Brian A.]

One other thing you can do is check Orange's support:
http://help.orange.co.uk/orangeuk/support/selfservice/index.jsp

--

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

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

 

[bm]

Since pinging the gateway (192.168.1.1) times out, there is no
communication between the PC and the router. As you mentioned in your
first post you could connect with the laptop but not with the PC, that
would suggest the network adapter and/or cable may be degraded. However
you only tested the PC and not the laptop when the problem last occurred.
You Need to Test Both the PC and laptop when the problem occurs to
properly find out if it is only prevalent to the PC or not.


--

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

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

Thanks for your comments. Although I did not carry out the same test I did
observe that I could still access the Internet from the laptop
Blair

 

[bm]

Your tests results suggest one of the following problems:
- A partially defective network adapter in your desktop PC.
- A marginal network cable or connector.
- A defective hub port.
- A defective hub.
Which one it is I cannot tell. Replacing one component at a time would
reveal the culprit. Since switching the hub off and on resolves the
problem, it is likely that your the hub is to blame.

Thanks for all your patience and help I will check as you suggested
Blair

 

[Brian A.]

Thanks for your comments. Although I did not carry out the same test I
did observe that I could still access the Internet from the laptop
Blair

That places the problem being with the desktop PCs network hardware, net
protocol and or cable.
The next time it occurs:
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: Space denoted by ^. Do not type the ^.

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 it doesn’t time out then the machine has communication with the router.

ping ^ google.com
If it times out then there is no connection to the net.
If it doesn’t time out 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 Experience }
Conflicts start where information lacks.
http://basconotw.mvps.org/

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

 

[bm]

That places the problem being with the desktop PCs network hardware, net
protocol and or cable.
The next time it occurs:
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: Space denoted by ^. Do not type the ^.

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 it doesn’t time out then the machine has communication with the router.

ping ^ google.com
If it times out then there is no connection to the net.
If it doesn’t time out 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 Experience }
Conflicts start where information lacks.
http://basconotw.mvps.org/

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

Thanks for your help.
I will do as you instructed the next time it faults and will let you know
the result
Blair

 

[bm]

That places the problem being with the desktop PCs network hardware, net
protocol and or cable.
The next time it occurs:
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: Space denoted by ^. Do not type the ^.

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 it doesn’t time out then the machine has communication with the router.

ping ^ google.com
If it times out then there is no connection to the net.
If it doesn’t time out 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 Experience }
Conflicts start where information lacks.
http://basconotw.mvps.org/

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

I carried out your instructions and appear to have solved the problem.
However I will have to wait because it was an intermittent fault before, So
fingers crossed.
I will let you know any changes after a few days operation
Many thanks
Blair