Domain To Workgroup Problem

I have a windows 2000 promachine that was set up to log onto a domain
that we moved to another location. THsi location uses a peer-to-peer
network. Despite changing the it from a domanin to a workgroup under
"To rename this computer or join a domain, click Change." in the sytem
property setup screen it fails to see any of the other computers on
the network despite being able to get avalid ip address from the
router and has the ability to access the internet over the same
netwrok.

I can ping the router but none of the computers on the workgroup

COuld it be in the LSA Policies

(E-Mail Removed) wrote:
> I have a windows 2000 promachine that was set up to log onto a domain
> that we moved to another location. THsi location uses a peer-to-peer
> network. Despite changing the it from a domanin to a workgroup under
> "To rename this computer or join a domain, click Change." in the sytem
> property setup screen it fails to see any of the other computers on
> the network despite being able to get avalid ip address from the
> router and has the ability to access the internet over the same
> netwrok.
>
> I can ping the router but none of the computers on the workgroup
>
> COuld it be in the LSA Policies

If you can't ping the other computers in that network then you have a basic
TCP/IP configuration problem, nothing to do with whether the machine thinks
its in a domain or workgroup.

Check the IP address - is it on a comparable range to the other machines? Is
the subnet mask correct?

Hello,

You say that you cannot ping other computers. That makes me think that you
have a problem with the network setup. Please verify that this computer have
the same settings as all other computers, and that the IP Address, subnet
mask, and all other things is the same.

You can use "ipconfig /all" in a cmd prompt, and compare it to other
computers in your network.

--
Regards,
Kristofer Gafvert
Reply to newsgroup only. Remove NEWS if you must reply by email, but please
do not.
www.ilopia.com - FAQ and Tutorials for Windows Server 2003


<(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> I have a windows 2000 promachine that was set up to log onto a domain
> that we moved to another location. THsi location uses a peer-to-peer
> network. Despite changing the it from a domanin to a workgroup under
> "To rename this computer or join a domain, click Change." in the sytem
> property setup screen it fails to see any of the other computers on
> the network despite being able to get avalid ip address from the
> router and has the ability to access the internet over the same
> netwrok.
>
> I can ping the router but none of the computers on the workgroup
>
> COuld it be in the LSA Policies

You say that this machine gets a valid IP address and can access the
Internet, but cannot "see" other machines on the network. This sounds like a
name resolution problem. Are you sure it is in the same workgroup as the
other LAN machines?

Check that you can ping to and from the machine by IP address on the
LAN. If this works, IP routing is working. Then try to ping by name. What
happens? What happens if you do "net view \\machinename" at a command prompt
on another machine on the LAN?

<(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> I have a windows 2000 promachine that was set up to log onto a domain
> that we moved to another location. THsi location uses a peer-to-peer
> network. Despite changing the it from a domanin to a workgroup under
> "To rename this computer or join a domain, click Change." in the sytem
> property setup screen it fails to see any of the other computers on
> the network despite being able to get avalid ip address from the
> router and has the ability to access the internet over the same
> netwrok.
>
> I can ping the router but none of the computers on the workgroup
>
> COuld it be in the LSA Policies

THe mnachine has a valid IP address in the proper range. It cannot
ping other machines in the workgroup and other machines in the
workgroup cannot ping it.


It cannot however ping the router

"net view \\machinename" a Yields a error 53 the network path not
found while doing it for any other machine on the netwrok show the
resources of that machinf

The internet on the machine in question works fine





On Sun, 21 Dec 2003 09:21:40 +1100, "Bill Grant" <bill_grant at
bigpond dot com> wrote:

> You say that this machine gets a valid IP address and can access the
>Internet, but cannot "see" other machines on the network. This sounds like a
>name resolution problem. Are you sure it is in the same workgroup as the
>other LAN machines?
>
> Check that you can ping to and from the machine by IP address on the
>LAN. If this works, IP routing is working. Then try to ping by name. What
>happens? What happens if you do "net view \\machinename" at a command prompt
>on another machine on the LAN?
>
><(E-Mail Removed)> wrote in message
>news:(E-Mail Removed).. .
>> I have a windows 2000 promachine that was set up to log onto a domain
>> that we moved to another location. THsi location uses a peer-to-peer
>> network. Despite changing the it from a domanin to a workgroup under
>> "To rename this computer or join a domain, click Change." in the sytem
>> property setup screen it fails to see any of the other computers on
>> the network despite being able to get avalid ip address from the
>> router and has the ability to access the internet over the same
>> netwrok.
>>
>> I can ping the router but none of the computers on the workgroup
>>
>> COuld it be in the LSA Policies
>

THe mnachine has a valid IP address in the proper range. It cannot
ping other machines in the workgroup and other machines in the
workgroup cannot ping it.


It cannot however ping the router

"net view \\machinename" a Yields a error 53 the network path not
found while doing it for any other machine on the netwrok show the
resources of that machinf

The internet on the machine in question works fine





On Sun, 21 Dec 2003 09:21:40 +1100, "Bill Grant" <bill_grant at
bigpond dot com> wrote:

> You say that this machine gets a valid IP address and can access the
>Internet, but cannot "see" other machines on the network. This sounds like a
>name resolution problem. Are you sure it is in the same workgroup as the
>other LAN machines?
>
> Check that you can ping to and from the machine by IP address on the
>LAN. If this works, IP routing is working. Then try to ping by name. What
>happens? What happens if you do "net view \\machinename" at a command prompt
>on another machine on the LAN?
>
><(E-Mail Removed)> wrote in message
>news:(E-Mail Removed).. .
>> I have a windows 2000 promachine that was set up to log onto a domain
>> that we moved to another location. THsi location uses a peer-to-peer
>> network. Despite changing the it from a domanin to a workgroup under
>> "To rename this computer or join a domain, click Change." in the sytem
>> property setup screen it fails to see any of the other computers on
>> the network despite being able to get avalid ip address from the
>> router and has the ability to access the internet over the same
>> netwrok.
>>
>> I can ping the router but none of the computers on the workgroup
>>
>> COuld it be in the LSA Policies
>

If what you say is true, then you have a hardware problem. Make sure that
the cable is okay, and that the switch (if any), is working correctly.

--
Regards,
Kristofer Gafvert
Reply to newsgroup only. Remove NEWS if you must reply by email, but please
do not.
www.ilopia.com - FAQ and Tutorials for Windows Server 2003


<(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> THe mnachine has a valid IP address in the proper range. It cannot
> ping other machines in the workgroup and other machines in the
> workgroup cannot ping it.
>
>
> It cannot however ping the router
>
> "net view \\machinename" a Yields a error 53 the network path not
> found while doing it for any other machine on the netwrok show the
> resources of that machinf
>
> The internet on the machine in question works fine
>
>
>
>
>
> On Sun, 21 Dec 2003 09:21:40 +1100, "Bill Grant" <bill_grant at
> bigpond dot com> wrote:
>
> > You say that this machine gets a valid IP address and can access the
> >Internet, but cannot "see" other machines on the network. This sounds
like a
> >name resolution problem. Are you sure it is in the same workgroup as the
> >other LAN machines?
> >
> > Check that you can ping to and from the machine by IP address on the
> >LAN. If this works, IP routing is working. Then try to ping by name. What
> >happens? What happens if you do "net view \\machinename" at a command
prompt
> >on another machine on the LAN?
> >
> ><(E-Mail Removed)> wrote in message
> >news:(E-Mail Removed).. .
> >> I have a windows 2000 promachine that was set up to log onto a domain
> >> that we moved to another location. THsi location uses a peer-to-peer
> >> network. Despite changing the it from a domanin to a workgroup under
> >> "To rename this computer or join a domain, click Change." in the sytem
> >> property setup screen it fails to see any of the other computers on
> >> the network despite being able to get avalid ip address from the
> >> router and has the ability to access the internet over the same
> >> netwrok.
> >>
> >> I can ping the router but none of the computers on the workgroup
> >>
> >> COuld it be in the LSA Policies
> >
>

THe mnachine has a valid IP address in the proper range. It cannot
ping other machines in the workgroup and other machines in the
workgroup cannot ping it.


It cannot however ping the router

"net view \\machinename" a Yields a error 53 the network path not
found while doing it for any other machine on the netwrok show the
resources of that machinf

The internet on the machine in question works fine

Changed cables no change. Am able to get another machine to work on
same network station

Also how can it be a cable problem if I can access the internet?

Must be in the software settings

How could I have a cable problem if On Sun, 21 Dec 2003 11:04:49
+0100, "Kristofer Gafvert" <(E-Mail Removed)> wrote:

>If what you say is true, then you have a hardware problem. Make sure that
>the cable is okay, and that the switch (if any), is working correctly.