Very perplexing network problem.

[pickle]

All suggestions have been followed. Still no joy.
I'm starting to get a bit irriteted at this thing.
Totally out of ideas.
Any more on your end anyone??

Thanks,
PIC

I'll come back with router names and models as suggested.
I forgot to do that.

Thanks.

 

[Not-My-Real-Name]

I think that's the problem. I think it means that PC didn't get assigned a
local 192. IP address by DHCP so it assigned itself 169.etc.

This can also happen if your machines are infected with LSP based
trojans/virus.
As a matter of fact I just fixed one like this yesterday.

Machine could PING machines on other subnets (I had to hard code the
192.168.1.x address, it was getting 169.x.x.x).

However nslookup, tracert, PINGs, etc failed to any external address.

The machine failed after running a Spyware remover by the user. Apparently
these LSP based trojans/viruses hack into your IP stack and mess with it.
Once removed, they can hose the dll files required for proper TCP/IP
function.

This may explain behavior relating to the desktops, but in this case there
may be an underlying issue with how these bridges are connected. Diagram
please! ;-)

 

[Not-My-Real-Name]

I second that.

Common practice is to set your workgroup to a collective noun (ex Flowers
or
Planets) and name your PC's.... Earth, Mars Venus etc

Avoid spaces in workgroup and PC names. Some network protocols have a
problem with this (so I'm told).

You can have duplicate names, it would depend on the protocols used.
However not usually when using MS networking.

Underscores and blanks are a no no using DNS so it would be best not to use
these.

I personally have never tried creating two machines with the same names but
in different workgroups. I should try it just for fun.

 

[pickle]

Sorry fot the delay in getting back. It's hard to troubleshoot when you
only get a half hour or so per day to do so. It makes it time consuming.

I'm beginning to see a pattern emerge.
Each desktop, by itself with no other machine hooked to the network
(including the wireless) seems to connect and run just fine.
I ran mine and it stayed connected for about an hour until I shut it down.
I ran the wife's all night and in the morning, it was still connected.
I'd like to run mine for a day or so as well to see.

Anyway, the appearence is that it is a conflict between the machines. I
have a hard time with this because we are using the same settings that
we have used for several years with no problems.

This leaves the wireless connection. I guess the wireless hub could be
backfeeding or something and knocking out the router. The settings in
the network config of the wireless laptop are also the same as they have
been for a long time with no problems.

I wonder what in a wireless hub would cause this. I'll be more
conclusive in a few days when I have been able to leave each machine
connected, by itself, and see if it cuts out.

Or I could run out and get a new wireless hub but I don't want to do
that at this stage.

What do you guys think of this?

 

[RS]

One thing that might solve your problem is to plug your modem directly into
the wireless hub uplink port. From there, plug your LAN computers directly
into the wireless hub.

Is there a specific reason you are routing to a linksys hub and then
wireless hub? Your signals might be degrading too much in the cross over...

You might be able to do without the linksys hub, if your wireless hub allows
for LAN connections (which most do).

-RS

 

[pickle]

One thing that might solve your problem is to plug your modem directly into
the wireless hub uplink port. From there, plug your LAN computers directly
into the wireless hub.

Is there a specific reason you are routing to a linksys hub and then
wireless hub? Your signals might be degrading too much in the cross over...

You might be able to do without the linksys hub, if your wireless hub allows
for LAN connections (which most do).

-RS

The wireless hub does not allow for this. However, we purchased a
better Linksys router with a hub built in so that elininated the LAN hub.
Now we just have the router / hub combo and the wireless hub.


Two days and the system is still up with only the wife's machine plugged
in. It's a slow way to troubleshoot but it's probably effective.

 

[Butterfield]

All suggestions have been followed.

really?? And it's still not working? Even with hard coded i/p
addresses? What error msgs do you get in the log when you did that??
Butterfield

 

[pickle]

really?? And it's still not working? Even with hard coded i/p
addresses? What error msgs do you get in the log when you did that??
Butterfield

I'll check and let you know. I am doing some further troubleshooting
steps and so far it looks good. I'll know more in a couple of days.

PIC