Unable to see Windows XP computers in network

Microsoft Windows server 2008 standard -...
May 16, 2010 at 15:34:07
Specs: Windows Server 2008 Standard x64, Dual Xenon Quad Core/24Gb
Hi, I have setup a member server running
WIN2K8 standard x64 in an AD 2003 domain
and cannot see any of my Windows XP boxes
when I open the network neighborhood
window,
however I can ping by name also I can use NS
lookup to resolve by name as well. Additionally
I can ping by IP address. I just can't see the
XP systems in the network window. I have
tried to turn off the firewall and turn on network
discovery but still no luck. I am however able
to see other WIN2K8 member servers and a
WIN7 box. My thought is to reset the firewall
settings back to default and move forward from
their also I might mention that there is no third
party firewall installed.

This is a new install of Windows Server 2008 Standard X64 SP2 and not in production yet so I have the flexibility to do whatever is needed to resolve this.
It seems as if this is just something simple that I am missing because I also have several other identical servers that exhibit the same behavior.

Any help would be greatly appreciated.


See More: Unable to see Windows XP computers in network

Report •

#1
May 17, 2010 at 10:02:21
Check your Stack and make sure you are using both TCP/IP and NetBIOS. Do a port scan and see if you can see 135. If not double check you firewall.

Report •

#2
May 17, 2010 at 14:05:29
Okay so let me add some additional info that I find a bit odd:

I have two WIN2K3 boxes, a DC and a member server.

The WIN2K8 member servers can see the WIN2K3 member
server in the network window but not the DC also I was able to
successfully join the WIN2K8 servers to the domain
additionally I am able to successfully run a login script to the
WIN2K3 member server that maps network drives which is
why I think it is able to be seen in the network window.
Also the firewall is now OFF and still no change ? ? ?
The RPC service is running + I have rebooted several times to
no avail.

Anyone else having these issues that can chime in and help
out ?


Report •

#3
May 17, 2010 at 15:35:55
post a ipconfig /all from the 2008 server for review.

Report •

Related Solutions

#4
May 18, 2010 at 18:24:00
P:\>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : Betty
Primary Dns Suffix . . . . . . . : cyberdefender.com
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : cyberdefender.com

Ethernet adapter Local Area Connection 4:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : BASP Virtual Adapter
Physical Address. . . . . . . . . : E4-1F-13-2E-23-5C
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::d4a8:7c8c:c236:16a0%15(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.12(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCPv6 IAID . . . . . . . . . . . : 384048915
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-13-64-8B-05-E4-1F-13-2E-23-5C

DNS Servers . . . . . . . . . . . : 192.168.1.10
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Local Area Connection* 9:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : isatap.{31F74610-28AC-40F3-BBDB-32A65A8D2
496}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 12:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 02-00-54-55-4E-01
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes


Report •

#5
May 28, 2010 at 07:43:23
Solved !

Made the dreaded call to Microsoft and discovered that my
Broadcom NIC Teaming software was the culprit.

As soon as I broke the Team and rebooted the servers all went
back to the way it should be.

Shame on IBM for selling new servers with defective software !


Report •

#6
May 28, 2010 at 10:12:54
Wow they really didn't do any QA to test the hardware to make sure it works with well known server software. I use HP teamed NICs with no problem.

I think IBM should pick up the bill for calling Microsoft.


Report •

Ask Question