Windows XP systems on a particular VLAN cannot be seen

Hi,

We have several VLANs and a group of XP (SP2 installed) client sitting on several VLANs cannot be seen under My Network Places. First thought, whether could it be a DNS issue or a WINS issue. But, it is not, as there are several other systems which are on different VLANs that can be seen. (Well, I have requested the Cisco guy to take a look at it on the switch and see whether anything is being blocked by the switch that would cause the browsing issues in My Network places), but thought could post this here and see whether I am missing something on the Microsoft Networking side.

We got few boxes from those VLANs and put them on our VLAN. The system does not show up immediately in My Network places, but after flushingdns and registering dns we are able to see the system. But, we can see the system in our VLAN. I did the same flushdns and registerdns on those VLANs but it could not see.

Some light if could be shed could be helpful. Thanks in advance.

Please post in Plain Text Format and not RTF or HTML. It drives the
NewsReaders "wacky" when we try to reply.

Switches don't block that kind of stuff. They can't, they are only Layer2
Devices.

There is about a million things that can cause problems but the most common
thing would be that the machines are not all using the same WINS Server.
The Windows Firewall will also get in the way and should not be used on that
LAN.

There is no "flushing" and "registering",...it just takes time. Network
Places is not "live",...it is just reading the data from a Browse List and
that list is only updated based on a time frame.

188305 - Troubleshooting the Microsoft Computer Browser Service
http://support.microsoft.com/default...b;en-us;188305

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com



"John Francis" <(E-Mail Removed)> wrote in message
news:OsLxA4$(E-Mail Removed)...
Hi,

We have several VLANs and a group of XP (SP2 installed) client sitting on
several VLANs cannot be seen under My Network Places. First thought, whether
could it be a DNS issue or a WINS issue. But, it is not, as there are
several other systems which are on different VLANs that can be seen. (Well,
I have requested the Cisco guy to take a look at it on the switch and see
whether anything is being blocked by the switch that would cause the
browsing issues in My Network places), but thought could post this here and
see whether I am missing something on the Microsoft Networking side.

We got few boxes from those VLANs and put them on our VLAN. The system does
not show up immediately in My Network places, but after flushingdns and
registering dns we are able to see the system. But, we can see the system in
our VLAN. I did the same flushdns and registerdns on those VLANs but it
could not see.

Some light if could be shed could be helpful. Thanks in advance.

Hi Phillip,

Thanks for the information. Yes, these systems were originally pointing to a
WINS server which was in a cluster. The WINS server on the cluster had some
issues and one of our network guy went and disabled it. But, more than
disabling it, there was an issue with the WINS (may be it has a corrupted
database). I have not had the time to check that. In the meantime when we
hit the problem of pushing NAV updates to the workstations and since
Symantec software could not see them in the available computer list, I had
to get another WINS server up and running. We pointed the workstations to
the new WINS server. But, as of this morning we have not seen those
workstations under "My Network Places".

Its XP SP2 but, firewall services is disabled. Also other unwanted services
are disabled on those workstations like browser service etc..

Thanks,

"Phillip Windell" <@.> wrote in message
news:%(E-Mail Removed)...
> Please post in Plain Text Format and not RTF or HTML. It drives the
> NewsReaders "wacky" when we try to reply.
>
> Switches don't block that kind of stuff. They can't, they are only Layer2
> Devices.
>
> There is about a million things that can cause problems but the most
> common
> thing would be that the machines are not all using the same WINS Server.
> The Windows Firewall will also get in the way and should not be used on
> that
> LAN.
>
> There is no "flushing" and "registering",...it just takes time. Network
> Places is not "live",...it is just reading the data from a Browse List and
> that list is only updated based on a time frame.
>
> 188305 - Troubleshooting the Microsoft Computer Browser Service
> http://support.microsoft.com/default...b;en-us;188305
>
> --
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
>
>
>
> "John Francis" <(E-Mail Removed)> wrote in message
> news:OsLxA4$(E-Mail Removed)...
> Hi,
>
> We have several VLANs and a group of XP (SP2 installed) client sitting on
> several VLANs cannot be seen under My Network Places. First thought,
> whether
> could it be a DNS issue or a WINS issue. But, it is not, as there are
> several other systems which are on different VLANs that can be seen.
> (Well,
> I have requested the Cisco guy to take a look at it on the switch and see
> whether anything is being blocked by the switch that would cause the
> browsing issues in My Network places), but thought could post this here
> and
> see whether I am missing something on the Microsoft Networking side.
>
> We got few boxes from those VLANs and put them on our VLAN. The system
> does
> not show up immediately in My Network places, but after flushingdns and
> registering dns we are able to see the system. But, we can see the system
> in
> our VLAN. I did the same flushdns and registerdns on those VLANs but it
> could not see.
>
> Some light if could be shed could be helpful. Thanks in advance.
>
>

That all fits together nicely. You cannot browse across segments without
WINS. Browsing has nothing to do with DNS. It is an NT lecacy app which uses
Netbios names and broadcasts. Because broadcasts don't cross routers
browsing is limited to the local segment without WINS. WINS allows the
master browsers to see each other directly to build combined browse lists.

John Francis wrote:
> Hi Phillip,
>
> Thanks for the information. Yes, these systems were originally
> pointing to a WINS server which was in a cluster. The WINS server on
> the cluster had some issues and one of our network guy went and
> disabled it. But, more than disabling it, there was an issue with the
> WINS (may be it has a corrupted database). I have not had the time to
> check that. In the meantime when we hit the problem of pushing NAV
> updates to the workstations and since Symantec software could not see
> them in the available computer list, I had to get another WINS server
> up and running. We pointed the workstations to the new WINS server.
> But, as of this morning we have not seen those workstations under "My
> Network Places".
> Its XP SP2 but, firewall services is disabled. Also other unwanted
> services are disabled on those workstations like browser service etc..
>
> Thanks,
>
> "Phillip Windell" <@.> wrote in message
> news:%(E-Mail Removed)...
>> Please post in Plain Text Format and not RTF or HTML. It drives the
>> NewsReaders "wacky" when we try to reply.
>>
>> Switches don't block that kind of stuff. They can't, they are only
>> Layer2 Devices.
>>
>> There is about a million things that can cause problems but the most
>> common
>> thing would be that the machines are not all using the same WINS
>> Server. The Windows Firewall will also get in the way and should not
>> be used on that
>> LAN.
>>
>> There is no "flushing" and "registering",...it just takes time.
>> Network Places is not "live",...it is just reading the data from a
>> Browse List and that list is only updated based on a time frame.
>>
>> 188305 - Troubleshooting the Microsoft Computer Browser Service
>> http://support.microsoft.com/default...b;en-us;188305
>>
>> --
>> Phillip Windell [MCP, MVP, CCNA]
>> www.wandtv.com
>>
>>
>>
>> "John Francis" <(E-Mail Removed)> wrote in message
>> news:OsLxA4$(E-Mail Removed)...
>> Hi,
>>
>> We have several VLANs and a group of XP (SP2 installed) client
>> sitting on several VLANs cannot be seen under My Network Places.
>> First thought, whether
>> could it be a DNS issue or a WINS issue. But, it is not, as there are
>> several other systems which are on different VLANs that can be seen.
>> (Well,
>> I have requested the Cisco guy to take a look at it on the switch
>> and see whether anything is being blocked by the switch that would
>> cause the browsing issues in My Network places), but thought could
>> post this here and
>> see whether I am missing something on the Microsoft Networking side.
>>
>> We got few boxes from those VLANs and put them on our VLAN. The
>> system does
>> not show up immediately in My Network places, but after flushingdns
>> and registering dns we are able to see the system. But, we can see
>> the system in
>> our VLAN. I did the same flushdns and registerdns on those VLANs but
>> it could not see.
>>
>> Some light if could be shed could be helpful. Thanks in advance.

That all fits together nicely. You cannot browse across segments without
WINS. Browsing has nothing to do with DNS. It is an NT lecacy app which uses
Netbios names and broadcasts. Because broadcasts don't cross routers
browsing is limited to the local segment without WINS. WINS allows the
master browsers to see each other directly to build combined browse lists.

John Francis wrote:
> Hi Phillip,
>
> Thanks for the information. Yes, these systems were originally
> pointing to a WINS server which was in a cluster. The WINS server on
> the cluster had some issues and one of our network guy went and
> disabled it. But, more than disabling it, there was an issue with the
> WINS (may be it has a corrupted database). I have not had the time to
> check that. In the meantime when we hit the problem of pushing NAV
> updates to the workstations and since Symantec software could not see
> them in the available computer list, I had to get another WINS server
> up and running. We pointed the workstations to the new WINS server.
> But, as of this morning we have not seen those workstations under "My
> Network Places".
> Its XP SP2 but, firewall services is disabled. Also other unwanted
> services are disabled on those workstations like browser service etc..
>
> Thanks,
>
> "Phillip Windell" <@.> wrote in message
> news:%(E-Mail Removed)...
>> Please post in Plain Text Format and not RTF or HTML. It drives the
>> NewsReaders "wacky" when we try to reply.
>>
>> Switches don't block that kind of stuff. They can't, they are only
>> Layer2 Devices.
>>
>> There is about a million things that can cause problems but the most
>> common
>> thing would be that the machines are not all using the same WINS
>> Server. The Windows Firewall will also get in the way and should not
>> be used on that
>> LAN.
>>
>> There is no "flushing" and "registering",...it just takes time.
>> Network Places is not "live",...it is just reading the data from a
>> Browse List and that list is only updated based on a time frame.
>>
>> 188305 - Troubleshooting the Microsoft Computer Browser Service
>> http://support.microsoft.com/default...b;en-us;188305
>>
>> --
>> Phillip Windell [MCP, MVP, CCNA]
>> www.wandtv.com
>>
>>
>>
>> "John Francis" <(E-Mail Removed)> wrote in message
>> news:OsLxA4$(E-Mail Removed)...
>> Hi,
>>
>> We have several VLANs and a group of XP (SP2 installed) client
>> sitting on several VLANs cannot be seen under My Network Places.
>> First thought, whether
>> could it be a DNS issue or a WINS issue. But, it is not, as there are
>> several other systems which are on different VLANs that can be seen.
>> (Well,
>> I have requested the Cisco guy to take a look at it on the switch
>> and see whether anything is being blocked by the switch that would
>> cause the browsing issues in My Network places), but thought could
>> post this here and
>> see whether I am missing something on the Microsoft Networking side.
>>
>> We got few boxes from those VLANs and put them on our VLAN. The
>> system does
>> not show up immediately in My Network places, but after flushingdns
>> and registering dns we are able to see the system. But, we can see
>> the system in
>> our VLAN. I did the same flushdns and registerdns on those VLANs but
>> it could not see.
>>
>> Some light if could be shed could be helpful. Thanks in advance.

"John Francis" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> Symantec software could not see them in the available computer list, I had
> to get another WINS server up and running. We pointed the workstations to
> the new WINS server. But, as of this morning we have not seen those
> workstations under "My Network Places".

Do any of them show in the WINS server? If there are none, then the WINS is
not running right. If there are some but not all, then make sure the TCP/IP
Config of the client machines (and the NAV Server) has the correct WINS
Server (and none other) and reboot the machines.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/IS...cessRules.html

Microsoft Internet Security & Acceleration Server: Guidance
http://www.microsoft.com/isaserver/t...dance/2004.asp
http://www.microsoft.com/isaserver/t...dance/2000.asp

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp

Deployment Guidelines for ISA Server 2004 Enterprise Edition
http://www.microsoft.com/technet/pro...isaserver.mspx
-----------------------------------------------------

Phillip:

WINS is running properly. All the machines are registering. There isn't a
problem. And those machines, which I had mentioned yesterday, they are also
seen in WINS, but they cannot be seen using My Network places. Any more
thoughts.

thanks,

"Phillip Windell" <@.> wrote in message
news:(E-Mail Removed)...
> "John Francis" <(E-Mail Removed)> wrote in message
> news:%(E-Mail Removed)...
>> Symantec software could not see them in the available computer list, I
>> had
>> to get another WINS server up and running. We pointed the workstations to
>> the new WINS server. But, as of this morning we have not seen those
>> workstations under "My Network Places".
>
> Do any of them show in the WINS server? If there are none, then the WINS
> is
> not running right. If there are some but not all, then make sure the
> TCP/IP
> Config of the client machines (and the NAV Server) has the correct WINS
> Server (and none other) and reboot the machines.
>
> --
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
> -----------------------------------------------------
> Understanding the ISA 2004 Access Rule Processing
> http://www.isaserver.org/articles/IS...cessRules.html
>
> Microsoft Internet Security & Acceleration Server: Guidance
> http://www.microsoft.com/isaserver/t...dance/2004.asp
> http://www.microsoft.com/isaserver/t...dance/2000.asp
>
> Microsoft Internet Security & Acceleration Server: Partners
> http://www.microsoft.com/isaserver/partners/default.asp
>
> Deployment Guidelines for ISA Server 2004 Enterprise Edition
> http://www.microsoft.com/technet/pro...isaserver.mspx
> -----------------------------------------------------
>
>
>

Then you probably need to look at the browser troubleshooter (KB 188305)
to see where it is failing. Browstat.exe is available in the support tools
on the server CD.

Felix wrote:
> Phillip:
>
> WINS is running properly. All the machines are registering. There
> isn't a problem. And those machines, which I had mentioned yesterday,
> they are also seen in WINS, but they cannot be seen using My Network
> places. Any more thoughts.
>
> thanks,
>
> "Phillip Windell" <@.> wrote in message
> news:(E-Mail Removed)...
>> "John Francis" <(E-Mail Removed)> wrote in message
>> news:%(E-Mail Removed)...
>>> Symantec software could not see them in the available computer
>>> list, I had
>>> to get another WINS server up and running. We pointed the
>>> workstations to the new WINS server. But, as of this morning we
>>> have not seen those workstations under "My Network Places".
>>
>> Do any of them show in the WINS server? If there are none, then the
>> WINS is
>> not running right. If there are some but not all, then make sure the
>> TCP/IP
>> Config of the client machines (and the NAV Server) has the correct
>> WINS Server (and none other) and reboot the machines.
>>
>> --
>> Phillip Windell [MCP, MVP, CCNA]
>> www.wandtv.com
>> -----------------------------------------------------
>> Understanding the ISA 2004 Access Rule Processing
>> http://www.isaserver.org/articles/IS...cessRules.html
>>
>> Microsoft Internet Security & Acceleration Server: Guidance
>> http://www.microsoft.com/isaserver/t...dance/2004.asp
>> http://www.microsoft.com/isaserver/t...dance/2000.asp
>>
>> Microsoft Internet Security & Acceleration Server: Partners
>> http://www.microsoft.com/isaserver/partners/default.asp
>>
>> Deployment Guidelines for ISA Server 2004 Enterprise Edition
>> http://www.microsoft.com/technet/pro...isaserver.mspx
>> -----------------------------------------------------