Vista

[Guest]

We have a mixed Server 2000 / 2003 enviroment with XP workstations. We have
added 3 Vista workstations. There is one Windows 2000 server that the Vista
workstations cannot connect to.
Cannot ping name or address of the Window 2000 server from Vista
workstations.
Cannot ping name or address of the Vista workstations from the 2000 server.
The Vista computers are comprised of 2 Toshiba laptops and one Dell desktop.
All latest updates drivers have been applied.
Any help would be appreciated.

Regards,
Robert

 

[Robert L [MVP - Networking]]

posting the results of ipconfgi /all here may help.

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
We have a mixed Server 2000 / 2003 enviroment with XP workstations. We have
added 3 Vista workstations. There is one Windows 2000 server that the Vista
workstations cannot connect to.
Cannot ping name or address of the Window 2000 server from Vista
workstations.
Cannot ping name or address of the Vista workstations from the 2000 server.
The Vista computers are comprised of 2 Toshiba laptops and one Dell desktop.
All latest updates drivers have been applied.
Any help would be appreciated.

Regards,
Robert

 

[Guest]

This is the ipconfig /all from my Vista laptop. When I ping the server
sometimes I might get one reply but the others time out, or sometimes it
replies normally. It is not consistant. Please see below... btw - The server
in question 192.168.0.7 is also our DHCP server - so I know there is
communiction going on.

C:\Users\rknight>ipconfig /all

Windows IP Configuration

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

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : pnf.com
Description . . . . . . . . . . . : Intel(R) PRO/1000 PL Network Connection
Physical Address. . . . . . . . . : 00-16-D4-93-EF-F6
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::7de8:de09:420e:f93c%8(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.0.110(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Tuesday, May 08, 2007 8:53:22 AM
Lease Expires . . . . . . . . . . : Friday, May 11, 2007 8:53:21 AM
Default Gateway . . . . . . . . . : 192.168.0.15
DHCP Server . . . . . . . . . . . : 192.168.0.7
DHCPv6 IAID . . . . . . . . . . . : 201332436
DNS Servers . . . . . . . . . . . : 192.168.0.16
Primary WINS Server . . . . . . . : 192.168.0.7
NetBIOS over Tcpip. . . . . . . . : Enabled

Wireless LAN adapter Wireless Network Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/Wireless 3945ABG Network
Con
nection
Physical Address. . . . . . . . . : 00-19-D2-61-25-05
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 6:

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

Tunnel adapter Local Area Connection* 7:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Local Area Connection* 9:

Connection-specific DNS Suffix . : pnf.com
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::5efe:192.168.0.110%19(Preferred)
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 192.168.0.16
NetBIOS over Tcpip. . . . . . . . : Disabled

Here are results from a couple of pings...

C:\Users\rknight>ping 192.168.0.7

Pinging 192.168.0.7 with 32 bytes of data:

Reply from 192.168.0.7: bytes=32 time=2ms TTL=128
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.168.0.7:
Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 2ms, Average = 2ms

C:\Users\rknight>ping -t 192.168.0.7

Pinging 192.168.0.7 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.

 

[Steve Stoffregen]

I had the same problem with just some of my Windows 2000 servers. Make sure
you have Service Pack 4 applied on the servers and they should show up then.

 

[Guest]

Thanks for the reply Steve.
The server in question does have SP4 applied and all critical updates.
I have also tried changing the advanced setting for Link Speed & Duplex for
the NIC from Auto Negotiation to 100Mbps Full Duplex. This had no affect.

Regards,
Robert

 

[Guest]

I ran Network Monitor on the Win 2000 Server and when I did a capture I was
able to ping both ways, connect to shares and connect using Remote Desktop.
When I stopped the capture I was again unable to ping or connect to shares.
(also worked when doing a port scan) Anyhow, after many hours on the phone
with Microsoft the problem has been resolved. What fixed it was installing
the latest NIC drivers. (even though we have 2 other identicle servers, all
running the same version of NIC driver, which do not exhibit this issue)

Regards,
Robert

 

[Guest]

I jumped the gun on this one. The issue has NOT been resolved. I am still
working with Microsoft. I have since tried connecting the server to different
switches using different patch cords. The server has duel NICs. Have tried
using the secondary NIC.

 

[Guest]

This issue has been resolved. We were getting the wrong mac address for the
Windows 2000 server on the Vista clients when doing an "arp -a" command. It
turned out to be an alias command in the configuration on our Cisco Pix
Firewall. The line was not needed. We removed it and are now able to
communicate normally between the server and the Vista clients.