Re: Problems joining NT Workstation to XP Pro Workgroup

Please Disregard.

It turned out to be the copy of Norton Firewall I had running on the NT
machine. Once I turned off the firewall I was able to see the test share I
had setup on the C drive. I saw somebody else's post that had a firewall
issue.

I guess this would bring up a new question. Is there anyway to allow
traffic through a firewall to access a share on the computer?

TIA

Jeff Gibson
Intercept Solutions
Nashville, TN

"Jeff Gibson" <jgibson@xxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:%23MBSj0pTIHA.5160@xxxxxxxxxxxxxxxxxxxxxxx
Looking for suggestions on what I might be missing here.

I have a machine that is running Windows NT Workstation 4.0 SP6. I want
to join it to a small workgroup of computers I have running at my office.
The workgroup has been setup on my XP Pro machine. I have an XP Home
machine and a Windows 2000 laptop that have all joined the workgroup with
no problem. Everything is connected to a 16 port switch/hub.

This is what I have done so far.

I connected the NT Workstation machine to the hub and I am able to access
the internet with no problem.

I went under the network properties on the NT Workstation machine and
assigned it to my "development" workgroup. When I pressed ok it put up a
message with something to the effect of "Welcome to the "development"
workgroup".

Now back on my Windows XP Pro machine where the workgroup was configured,
if I go under the "development" workgroup under Microsoft Windows Network,
I can see the NT machine in my list of computers associated with the
workgroup. Along with all my other machines.

The problem comes in when I try to look at the shared drives under the NT
Workstation machine from the XP Pro network neighborhood. When I click on
the machines computer name I get the following error.

*----------------------------------------------------------------x*
\\NTDEV is not accessible. You might not have permission to use this
network resource. Contact the administrator of this server to find out if
you have access permissions.

The network path was not found.
*-----------------------------------------------------------------*

Any suggestions on what part of the puzzle might be missing here. It
really looks like I'm almost there.

TIA for any help.

Jeff Gibson
Intercept Solutions
Nashville, TN



.

Relevant Pages

  • Re: Workgroup is not accessible.
    ... The only network connection with the ... firewall set was the dial-up connection, ... Even when it accesses the workgroup, ...
    (microsoft.public.windowsxp.network_web)
  • Re: Setting up a network using XP and Vista
    ... In XP I have gone to Network Set Up Wizard the default Workgroup is MSHOME. ... a misconfigured firewall or overlooked firewall (including a stateful ...
    (microsoft.public.windowsxp.general)
  • Re: Can not find other devices on Network
    ... The link you specified shows the workgroup the way it displays in XP. ... Network traffic as trusted. ... start by running the Network Setup Wizard on all machines (see ... by 1) a misconfigured firewall or overlooked firewall (including a stateful ...
    (microsoft.public.windows.vista.networking_sharing)
  • Re: Can not find other devices on Network
    ... The link you specified shows the workgroup the way it displays in XP. ... Network traffic as trusted. ... start by running the Network Setup Wizard on all machines (see ... by 1) a misconfigured firewall or overlooked firewall (including a stateful ...
    (microsoft.public.windows.vista.networking_sharing)
  • Re: Home Network - problem adding PC to Workgroup
    ... But I CAN't seem to get it recognized by or get it to recognize the other pcs in the workgroup. ... start by running the Network Setup Wizard on all machines. ... Problems sharing files between computers on a network are generally caused by 1) a misconfigured firewall; or 2) inadvertently running two firewalls such as the built-in Windows Firewall and a third-party firewall; and/or 3) not having identical user accounts and passwords on all Workgroup machines; 4) trying to create shares where the operating system does not permit it. ...
    (microsoft.public.windowsxp.network_web)
Loading