Unable to connect to network using Windows7 machine - Page 2

Gordiep13 · ‎10-18-2012

We are trying to rollout a Windows7 build laptop onto our network. We have 2 x 2950sx switches connected to 2 x 3560G.

When the laptop is plugged into a port on the 2950 it gets an IP address in the correct subnet and all the correct settings as assigned by the DHCP scope, but it is unable to ping any IP address. It will not even ping the default gateway or any other client on the same subnet. If a Windows XP build laptop is connected to the same port there is no connectivity problems.

Each 2950 has a fibre connection into the 3560 and there is a port-channel connecting the 2 x 3560's.

After the windows7 laptop is connected to the 2950 the mac address for the laptop shows against the trunk port connected to the 3560(e.g laptop is connected to port fa0/7 but mac address shows against gi0/1). When you login to the 3560 the mac address shows that it is on the 2950 through the connected trunk port.

There are other 2960 switches connected to the 3560 and when the Windows7 laptop is connected to a port on that switch there are no problems. It gets an IP address and can connect to all resources. When the laptop is connected directly into the 3560 it works without any problems.

Does anyone know why the Windows7 laptop would not register its mac address against its connected port? After you clear the mac address table from the 2950 the Windows7 mac address appears in the table even though it is no longer connected, still listed against the trunk port connected to the 3560.

Thanks

JohnTylerPearce · ‎10-19-2012

What does the MAC table look like on port fa0/7 on that specific access switch?

Gordiep13 · ‎10-19-2012

When the Windows7 laptop is connected to port fa0/7 there are no entries in the mac table against that port.

JohnTylerPearce · ‎10-19-2012

What happens if you try to ping anything, does the MAC show up? Also, what is port Gi0/1 on that switch connected to?

And can you post the configuration of 'show spanning-tree vlan 90'?

Gordiep13 · ‎10-19-2012

You cannot ping anything from the Widows7 client. As long as the Windows7 client is connected to port Fa0/7 nothing ever appears in the mac address table against port Fa0/7.

The sh cdp neigh command above shows that the 3560 core L3 is connected to port gi0/1. This is the gateway for VLAN90.

Spanning-tree config for the switch is listed below -

WIS129105#sh spanning-tree vlan 90

VLAN0090

Spanning tree enabled protocol rstp

Root ID Priority 8282

Address 0017.e08b.c800

Cost 4

Port 25 (GigabitEthernet0/1)

Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec

Bridge ID Priority 32858 (priority 32768 sys-id-ext 90)

Address 0018.b9d6.6800

Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec

Aging Time 300

Interface Role Sts Cost Prio.Nbr Type

---------------- ---- --- --------- -------- --------------------------------

Gi0/1 Root FWD 4 128.25 P2p

Gi0/2 Desg FWD 4 128.26 P2p

turnera · ‎10-19-2012

Got a firewall on that Win 7 box? Try turning it off and see if that makes any difference.

Gordiep13 · ‎10-19-2012

No firewall enabled on the windows7 build

turnera · ‎10-19-2012

Can you even ping the loopback on the laptop? (127.0.0.1)

We are talking basics here, but lets at least see if something is working on that machine.

Muhammad Thanveer · ‎10-20-2012

Yes If you are able to ping loopback thats fine from win7 box side.

Might be Anti Virus issue if it is installed in the win7 box.

Try this link for info:

http://www.cisco.com/en/US/products/hw/switches/ps708/products_tech_note09186a00807347ab.shtml#troubleshoot

Regards
Thanveer
"Everybody is genius. But if you judge a fish by its ability to climb a tree, it will live its whole life believing that it is a stupid."

Gordiep13 · ‎10-25-2012

Hi Everyone,

Thanks for all your responses. We have managed to resolve the issue.

The 2950 switches were replaced with 2 new 2960G and the problem persisted.

After this we created a new VLAN(VLAN91) and moved the Windows7 build PC's into this VLAN and created and new DHCP scope for VLAN91. The Windows7 build was able to get an IP address in this new VLAn and also connect to the rest of the network without any problems.

At this point we decided that we could see no other clear problems and the only course left was to reboot the 2 core 3560G's. During the reboot we also upgraded the IOS from 12.2(46) to 12.2(58). After the reboot of the 2 devices was completed the Windows7 build machines were moved back into VLAN90 and they started working. They got an IP address and were also able to connect to the whole corporate network.

Would still like to know what caused this but it is working now and everyone is happy.

Thanks again