Home All Groups Group Topic Archive Search About

One-Way View of Workgroup

Author
18 Oct 2006 7:07 PM
SteveG
I'm connecting two computers for a friends, via a D-Link DI-624 router. Both
have Windows XP Home SP2. Computer A has two printers attached, with printer
sharing enabled and unique names for each. Each computer has a unique ID. In
Network Setup Wizard, I selected "connection through a router", and ran it on
each machine. Computer "A" sees the workgroup computers, but cannot access
"B", even though "B"'s printer and file sharing is on, as well as sharing the
"C" drive.
Computer "B" cannot see the workgroup computers, and when trying to add
either of "A"'s printers via the wizard, "B" cannot get any further than
seeing "Microsoft Windows Network" in the wizard's box, but it will not
expand and no printers can be seen. Any help?

--
Thank you for advice & ideas!

Author
18 Oct 2006 8:09 PM
Malke
SteveG wrote:

> I'm connecting two computers for a friends, via a D-Link DI-624
> router. Both have Windows XP Home SP2. Computer A has two printers
> attached, with printer sharing enabled and unique names for each. Each
> computer has a unique ID. In Network Setup Wizard, I selected
> "connection through a router", and ran it on each machine. Computer
> "A" sees the workgroup computers, but cannot access "B", even though
> "B"'s printer and file sharing is on, as well as sharing the "C"
> drive. Computer "B" cannot see the workgroup computers, and when
> trying to add either of "A"'s printers via the wizard, "B" cannot get
> any further than seeing "Microsoft Windows Network" in the wizard's
> box, but it will not expand and no printers can be seen. Any help?
>

This is most commonly caused by a misconfigured firewall. Running the
Network Setup Wizard turns on the XPSP2 Windows Firewall. If you aren't
running a third-party firewall or have an antivirus with "Internet Worm
Protection" (like Norton 2005/06) which acts as a firewall, then you're
fine. However, if you have third-party firewall software you'll need to
configure it to allow the Local Area Network traffic as trusted. I
usually do this with my firewalls with an IP range. Ex. would be
192.168.1.0-192.168.1.254. Obviously you would substitute your correct
subnet.

If that doesn't work for you, here is an excellent network
troubleshooter by MVP Hans-Georg Michna. Take the time to go through it
and it will usually pinpoint the problem area(s) -
http://winhlp.com/wxnet.htm

Malke
--
Elephant Boy Computers
www.elephantboycomputers.com
"Don't Panic!"
MS-MVP Windows - Shell/User
Author
19 Oct 2006 12:31 AM
SteveG
Malke,
Thanks. I though I'd adjusted the network range for that very purpose, but I
might have missed it. I'm going in now to configure NIS 2006 on both machines
and will try again. Appreciate your patience and understanding.
Steve
--
Thank you for advice & ideas!


Show quoteHide quote
"Malke" wrote:

> SteveG wrote:
>
> > I'm connecting two computers for a friends, via a D-Link DI-624
> > router. Both have Windows XP Home SP2. Computer A has two printers
> > attached, with printer sharing enabled and unique names for each. Each
> > computer has a unique ID. In Network Setup Wizard, I selected
> > "connection through a router", and ran it on each machine. Computer
> > "A" sees the workgroup computers, but cannot access "B", even though
> > "B"'s printer and file sharing is on, as well as sharing the "C"
> > drive. Computer "B" cannot see the workgroup computers, and when
> > trying to add either of "A"'s printers via the wizard, "B" cannot get
> > any further than seeing "Microsoft Windows Network" in the wizard's
> > box, but it will not expand and no printers can be seen. Any help?
> >
>
> This is most commonly caused by a misconfigured firewall. Running the
> Network Setup Wizard turns on the XPSP2 Windows Firewall. If you aren't
> running a third-party firewall or have an antivirus with "Internet Worm
> Protection" (like Norton 2005/06) which acts as a firewall, then you're
> fine. However, if you have third-party firewall software you'll need to
> configure it to allow the Local Area Network traffic as trusted. I
> usually do this with my firewalls with an IP range. Ex. would be
> 192.168.1.0-192.168.1.254. Obviously you would substitute your correct
> subnet.
>
> If that doesn't work for you, here is an excellent network
> troubleshooter by MVP Hans-Georg Michna. Take the time to go through it
> and it will usually pinpoint the problem area(s) -
> http://winhlp.com/wxnet.htm
>
> Malke
> --
> Elephant Boy Computers
> www.elephantboycomputers.com
> "Don't Panic!"
> MS-MVP Windows - Shell/User
>