Re: Reverting Wireless to Wired Network.
- From: "Steve Winograd [MVP]" <winograd@xxxxxxxxx>
- Date: Sat, 14 May 2005 22:15:54 -0600
In article <#ubS4rPWFHA.3424@xxxxxxxxxxxxxxxxxxxx>, "James O.
Thompson" <thethompsons@xxxxxxxx> wrote:
>I have a three computer home network (2 XP Pro's SP2 and 1 2000 Pro).
>Originally, they were networked with thin ethernet cards, no hub and a
>shared DSL broadband attached to one of the XP machines.
>
>I "upgraded" this to a wireless network using encryption but didn't like the
>frequent disconnects so I tried restoring the network to the thin ethernet
>configuration. Now none of the three computers can talk to anything,
>including themselves.
>
>If I ping 127.0.0.1 all computers respond correctly but if I ping their
>local IP addresses all of them time out. They all have IP address in the
>169.254.x.y range and all have a status of "Limited or no connectivity". If
>I force an IP address (rather than let them be automatically configured) the
>status is then OK but still they can't even ping their local addresses.
>
>I suspect something about the encryption has carried over from the wireless
>setup. I note that the adapters properties have Authentication 802.1x
>enabled, whatever that is. I've tried disabling that but it doesn't seem to
>fix the problem.
>
>I'm not sure if I should have a dhcp server and, if so, on which machine it
>should be running. I don't see such a service running on any of the
>machines, only dchp clients. Is there a way to start such a server?
>
>Can anyone help?
>
> Jim Thompson
I don't think that wireless encryption and 802.1x authentication have
any effect on a wired network, Jim. Something else must be causing
the problems.
On the XP Pro SP2 computers, type this line at a command prompt, then
reboot. It can cure some difficult networking problems:
netsh winsock reset catalog
To get a DHCP server on your network, you can either enable ICS on one
of the computers or install a home broadband router. Without a DHCP
server, computers that are configured to obtain an IP address
automatically assign themselves compatible 169.254.x.x/255.255.0.0 IP
addresses and should be able to communicate with each other.
When a computer can't ping its own IP address, the most likely problem
is a firewall program (Norton, McAfee, ZoneAlarm, PC-cillin, Sygate,
etc) that has been misconfigured or improperly installed/uninstalled.
Disconnect all computers from the Internet, disable XP's Windows
Firewall, and uninstall all firewall programs. If you've previously
uninstalled a firewall program, reinstall it and then uninstall it.
Then, go to Start | Run | Msconfig, disable any firewall remnants in
the Startup and Services tabs, and reboot.
Once the computers can talk to each other, enable XP's Windows
Firewall, or reinstall firewall programs and configure them to allow
access by other computers on the LAN. Don't use both Windows Firewall
and a firewall program on the same computer -- use one or the other.
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)
Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.
Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com
.
- Follow-Ups:
- Re: Reverting Wireless to Wired Network.
- From: James O. Thompson
- Re: Reverting Wireless to Wired Network.
- References:
- Reverting Wireless to Wired Network.
- From: James O. Thompson
- Reverting Wireless to Wired Network.
- Prev by Date: Re: Need help interpretting browstat output
- Next by Date: Re: Need help interpretting browstat output
- Previous by thread: Reverting Wireless to Wired Network.
- Next by thread: Re: Reverting Wireless to Wired Network.
- Index(es):
Relevant Pages
|
Loading
