Network trouble after rebooting

  • Thread starter Thread starter James
  • Start date Start date
J

James

Lately whenever I have to reboot one of the machines on my
three system WIN XP network with D-Link router, I then
have to shut down all three machines, re-synch my cable
modem and router, then restart the three machines and run
network setup again to get them all able to access the
internet and cross talk with each other.

Any ideas on why this is occuring now, when it never did
in the past?

TIA
 
Could you possibly provide the following information:

1) Are you running firewalls on your Windows XP machines?
2) Could you clarify what you mean by "re-synch my cable modem" i.e. power
cycle?
3) Are all of the machines connected to a hub or to each other before
connecting to the router? "i.e ICS or Network Bridge"
4) Are any of the machines connected using wireless?
5) Do you know if your cable modem is using a static IP address or DHCP?
 
Not off hand.

Could you provide more details (e.g. what condition or errors are you
seeing).
 
Could you possibly provide the following information:

1) Are you running firewalls on your Windows XP machines?
2) Could you clarify what you mean by "re-synch my cable modem" i.e. power
cycle?
3) Are all of the machines connected to a hub or to each other before
connecting to the router? "i.e ICS or Network Bridge"
4) Are any of the machines connected using wireless?
5) Do you know if your cable modem is using a static IP address or DHCP?

1) running sygate personal firewall pro on all systems
2)resynch = shut down pc's; shut down router; shut down cable modem;
start cable modem; start d-ling 614+ router (with newest firmware
installed); start pc's
3)each machine connected with ethernet cable to d-link router (no
machines presently using wireless)
4)no wireless at present, but have used this option in past with
guests.
5)cox cable uses DHCP

TIA
 
Could you possibly provide the following information:

1) Are you running firewalls on your Windows XP machines?
2) Could you clarify what you mean by "re-synch my cable modem" i.e. power
cycle?
3) Are all of the machines connected to a hub or to each other before
connecting to the router? "i.e ICS or Network Bridge"
4) Are any of the machines connected using wireless?
5) Do you know if your cable modem is using a static IP address or DHCP?

1)Running Sygate personal firewall pro on all three systems.
2) Shut down computers; shut down power to D-Link router; shut down
power to cable modem; power up cable modem; power up router; power up
pc's.
3) D-Link 614+ wireless broadband router; all machines are presently
connected via ethernet cables to router ports; no wireless. HAve used
this router/configuration for many moons.
4. All connected using ethernet cable
5. Cox uses dynamic DHCP.

Problems continued after I downloaded and installed newest updates for
this d-link router yesterday.

TIA
 
James,

Thanks for the details

So as I understand it the problem your having is you can't access other
computers on the network? You should never have to reboot so I am not sure
why you are doing this, it generally resolves nothing except in the instance
where a device may be frozen.

Can you ping the DLINK device, or for that matter even use the DLINK
management tools (usually through a web interface)?

Does turning off the firewall on each of the machines on the network allow
you to ping them as well?

What IP address are you getting (do an IPCONFIG /ALL from the command
prompt).
 
Paul:

Did some manual reading today and discovered a reset button for my
D-Link router. Using a paper clip, I reset it and my network seems to
have stabilized?!? I had presumed that when I downloaded and
installed the latest firmware for the DI-614+ that it would be reset
to its factory default settings. However, that may not have been the
case?!?

Also told the Sygate Personal Pro firewall to exempt traffic
192.168.0.1-192.168.0.110 on my three machines.

In any event, I'm up and running!

TIA
 
Ah.

Typically when you do a firmware update, most hardware companies recommend
you power cycle the router or reset it via the reset button.
 
Paul:

With everything running according to Hoyle, I left all pc's for a
respite of golf on TV. Returned an hour later, and got on the internet
with no problem. Starting downloading email using Outlook (2003), and
retrieval died in mid-flight. Got out of outlook and my browser (IE 6)
went belly up, and my wife's machine could not get on the internet
either.

Shut down all machines, router and modem. Powered the modem, then the
router, then all machines, and I'm on line again with Agent, IE6 and
Outlook 2003 all working fine!

Whatever this gremlin is, its killing me. Might just go out and buy a
new router tomorrow.
 
James,

Which ISP is this? Also which modem/router did they give you?

Also please try the following things first when you have a problem.

1 - capture your settings on your computer (IPCONFIG /ALL)
2 - try pinging the DNS server, default gateway (whic have been identified
in step 1)
3 - reset the modem
4 - try to access the internet again

based upon the results of that please let us know. We can step from that
point.
 
Paul:

After latest inability to access the internet ran ipconfig /all. All
settings were as they should be. I was able to ping the DNS server
(192.168.0.1) and received all four packets back.

I have now taken the D-Link out of the loop, and am running the cable
modem directly into my PC. If I experience any further disconnects,
I'll let you know.

My ISP is HR.COX.NET

I have a 3COM homeconnect external cable modem with USB (don't use
USB). I have used this modem since 1/8/00. Tried to check on its
drivers, but it does not show up as a hardware device even when
directly connected to my ethernet card for some reason?!?
 
I finally resolved this problem with a new Toshiba THX 2600 modem. Apparently my old 3COM modem was the culprit. Although supposedly DOCSIS compliant, it never really worked well in the last few weeks.
 
It was probably DOCSIS compatible and not compliant or certified.

Glad it is working.

Apparently my old 3COM modem was the culprit. Although supposedly DOCSIS
compliant, it never really worked well in the last few weeks.
 
Back
Top