Re: >>Two XPs can't see each other<<

From: Chuck (none_at_example.net)
Date: 02/20/04


Date: 19 Feb 2004 23:33:11 -0600

On Thu, 19 Feb 2004 18:51:35 -0800, "Wayne B."
<Mrcmosdriver@aolnott.com> wrote:

> Say Chuck, XP Home now shows up in Mshome workgroup but
>when I double click on it I keep getting this message on
>Pro and W2k --> (Mshome is not accessible. You might not
>have permission to use this network resource.
>etc,etc,etc......) This makes me believe that there is a
>firewall somewhere that I missed, but IPv6 Internet
>Connection Firewall has been disabled on both of the XPs
>already.
> On XP Home when I try to access >My network places< I
>get "Mshome is not accessible. I have Mcafee loaded on
>the Pro machine, but have it configured so that my
>network can see each other w/o interference. The XP HE is
>a friend's that was bought new (Emachine) about 3 yrs
>ago. No alterations have been made to it.
>
> Another point of interest. If APIPA deals with IPs
>within the 169.254.x.x range, how did I get 192.168.x.x
>IPs for my Pro and 2k. The Pro gets the internet thru a
>dialup connection. But that's totally seperate from my
>LAN setup. It's been like that for months.
APIPA provides for a dynamic ip address to be self-assigned to a
computer, when it specifies DHCP but there is no DHCP server
available. Your ISP, or your router, provides an ip address
dynamically when it is asked for one.

Obviously there is a DHCP server somewhere, assigning DHCP to XP Pro
and to 2K. "192.168.X.X" sounds like your DHCP server - that's a
private address range.

And obviously you either have a firewall running on XP Home, or it has
a network problem. Or what ever device is providing DHCP services to
the others has a problem. Maybe McAfee is still a problem - that
wouldn't be the first!

> This is the first time though, that I have gotten
>169.254 IPs. (Since I wiped my Pro clean and reinstalled
>it about 2 weeks ago.) I also did change the port
>connection earlier, forgot to mention that. THANX
>The Rookie/Wayne B.

Wayne,

So we need to start over. Please describe your LAN in detail - what
computers are connected, with their names, and operating system name
and version. And how does each connect to your ISP. Try to match
each with its current ip address.

Then we need to figure out what software firewalls you have.
HijackThis will provide a nice list of all process running on a
computer - including any firewalls or maybe something else like
spyware. It's free from
<http://www.majorgeeks.com/download.php?det=3155>. Open HJT, Scan,
then Save log produces a nice text file listing everything running on
the computer.

Ipconfig data would help a lot too. "ipconfig /all >c:\ipconfig.txt"
provides a nice text based file that you can paste into your next post
too.

Whatever you're comfortable with.

Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.



Relevant Pages

  • Re: Re: Cant ping win 2000 Pro
    ... >> ping each other either by name or IP address. ... > Windows 2000 Pro ... >> ports and network cables. ... > a) Firewall restrictions. ...
    (microsoft.public.win2000.general)
  • Re: Home LAN Network setup problems
    ... Home Edition and Pro respectively) from a Edimax router with wired-in Cat5E ... the other computers on the network that was supposedly created, ... firewall program on ...
    (microsoft.public.windowsxp.network_web)
  • Re: Network fails in one direction
    ... The network worked totally up to expectations when the OS config was ... This is most commonly caused by a misconfigured firewall. ... If one or more of the computers is XP Pro - and this is applicable to you ... Simple File Sharing and create identical user ...
    (microsoft.public.windowsxp.newusers)
  • Home networking
    ... I'm going to try to get the details in one message: Home Network: ... Linksys gateway router, wired to xp pro, setup as firewall. ... first machine, and was able to ping laptop, but not to xp home machine. ...
    (microsoft.public.windowsxp.network_web)
  • Re: Weird DHCP behavior
    ... > than 50 users) network. ... The setup has not changed since we had Win2000 pro ... > printer did not start receiving the print job until about 75 seconds ... On our network we have a server set up as a DHCP server and its ...
    (microsoft.public.windowsxp.general)

Loading