Network cable unpluged - Local area Connection is now connected problem
I'm constantly getting this "Network cable unplugged - Local area Connection
is now connected" on my cable connected Futjisi Siemens with a built-in
Realtek RTL8139/810 net-adaptor and is really disconnecting-connecting.
I have tried to do all the things which were advised at
http://winhlp.com/wxnet.htm,+ some more, but no luck.
This problems started when I bought a new D-Link Xtreme G DI-624-
54(108)Mbps wireless Router, which I again changed into a new TopCom
Skyracer Pro WBR 654- 54(108)Mbps wireless router.
In the beginning it seems to be alright, but gradually also this router has
starting giving me the same problems.
If I connect my cabled PC direct to my Thompson Speedtouch 510 router, I
never experience this problem. Also if I turn off the wireless option in
TopCom router every thing goes without any problem.
It also seems like if I'm up and connected to the network with my laptop,
the problems on my cabled PC also seems to disappear.
So as far as I can see, there isn't any direct hardware error on any of my
systems (also replaced cables), but rather some strange mismatch and the
wireless system causes my cabled PC to disconnect- connect all the time!? I
have tried all the different settings I can on both router and Realtek
netadaptor without any improvement.
Another thing which also seem odd, is that almost every time I try to fix
Winsock or resetting IP stack, it seems like the problems disappear for a
while (hours or so). But not sure if this mean anything or just by change!??
Have anyone experienced the same and have any solution on my problem?
Could the build-in RTL-8139/810 and wireless router system some how be
incompatible?
If so, has anyone any advise on how to disable the netadaptor for to install
a new one? (Tried this a few days ago, but the PC still found the old one
and I never got it to work).
My equipmet history is as follow:
1 Fujitsu Siemens Scaleo 600 with a built in Realtek RTL8139/810 netadaptor,
Full size ATX Motherboard (fixed IP)
1 Dell Inspiron 8600 wireless (fixed IP)
1 Thompson Speedtouch 510 router
1 TopCom Skyracer Pro WBR 654 (54/108) router (disabled DHCP)
All PC's running XP home SP2
Trend Micro Pc-cillin Internet Security
Re: Network cable unpluged - Local area Connection is now connected problem
It sounds like you are complicating things a little. I would do the
following:
1) pick the router you want to use, and stick with it. Too much hardware
gets confusing.
2) Keep it simple. Use the 192.168.1.0/24 (mask = 255.255.255.0) range on
all devices.
3) Make sure the router has an address of 192.168.1.1, and that the PC's
have addresses of 192.168.1.x --> where x is not 1.
4) If the router can do DHCP, let it, unless you really need static
addresses for your clients.
Re: Network cable unpluged - Local area Connection is now connected problem
Maybe, but since I use fixed internal IP, the router range (sett in the
router) shouldn't have any impackt!.... I think??
The reason for changing from my first 11 (22) Mbps, was that this just
stopped working during a setup change. This was probably one of a million or
so change, but during this prosess I got a power-shutdown in the house. And
after that I was never able to reset it.
So that's why I bought a new D-Link G DI-624 and it was at that point when I
started getting this problem. After checking out some public comments for
same product and same problem at amazon.com, I just used my 30 days option
to change it into the present one.
When thinking back on it, I was never able to get out on the net with my PC,
using "receive IP-address automatically" and that's why I started using
fixed. Later, when introduced wireless into my net I also kept this option
and disabled DHCP on my router for safety reason
Re: Network cable unpluged - Local area Connection is now connected problem
What you see above in my post, is all we can see in the Microsoft Public
Newsgroup, "microsoft.public.windows.server.networking." Techarena
pulls/pushes posts from this group. Unfortunately many folks in techarena do
not realize this and respond to older posts, such as what you did. Posts
expire after 90 days.So when we see an empty post such as yours, we are not
able to help.
It would be beneficial to start a fresh thread, stating your problem you are
experiencing, and related, pertinent facts and error messages in the event
logs, to better assist you.