xp network problem

[techsavvy1]

furustrating, don't know why this not working.

both pc connected using crossover cable. one using 2000 pro (laptop - can ping other) and other xp pro (desktop unable to ping the other). have created share on the laptop, but xp pc cannot access it.

windows 2000 pc can actually see and ping xp pc. but problem is with xp pro pc, it can't ping or see 2000 pro pc.

changed ip addresses to 192.168.0.10 and 192.168.0.6. Restarted both systems, still problems accessing or connecting

this is the message i get when i try to access it via network places on xp pro.

'\\matrix is not accessible. you might not have permission to use this network resource. contact administrator of this server to find out if you have access permission on network. path was not found'

both are on same workgroup, do not use domain. I take my laptop to office and uses the same workgroup.

tried winsockxp repair, still problem persist. tried floppy network setup from xp, tried uninstalling nic on xp and updating drivers for it,

one time i did see my 2k machine on xp network places window, but on clicking on it problem persisted, tried mapping, tried \\. have spend almost full day on simple thing that supposed to work without setting static ip add, etc. even tried creating user a/c on w2k with same credential as xp.

Any help connecting the two pcs much appreciated, cheers.

 

[bcastner]

I am a a little worried you are not using the native APIA addressing in your cross-over cable LAN. Set both workstations to obtain an IP address automaticly. Reboot both and test.

If all of the settings for Worgroup are as you say above, check:

. any software firewall. Disabling the firewall does not work. Either configure it properly, or formally uninstall the firewall for testing.

. "Hidden" firewalls. Antivirus products often include a hidden firewall component. "PC-Illan" is notorious for this.

. VPN clients. The CISCO VPN client is notorious for this.

. an Bridge device. Watch for 1394 or other Bridges being assigned if you run the Network Wizard application. Disable, and the remove them.

Please check too that "Netbios over TCP/IP" is enabled in the Advanced Settings under Internet Protocal (TCP/IP) WINS tab; and that an exception was made in the Winfows Firewall for File and Printer sharing under SP Service Pack 2.

This site may help:

http://www.michna.com/kb/wxnet.htm

 

[techsavvy1]

i deny cisco vpn client that shows up everytime i start.

have tried shutting down zone lab firewall
have tried auto IPs, that shows as 169.254.x.x
don;t have any bridges
not usinf xp sp2 yet and netbios over tcp/ip is enabled, well default is anyway.

haven't tried to disable the anti-virus as yet. i use symantec corporate v7, and free avg grisoft

i will try all your suggestion again, let you know when.

many thanks for the feedback

 

[bcastner]

Uninstall the CISCO client with Control Panel, Add/Remove Programs.

Reboot and test again.

A Deny is not good enough.

 

[bcastner]

have tried auto IPs, that shows as 169.254.x.x"

These will work.

 

[techsavvy1]

thanks, just on cisco vpn client, I have no connectivity problem at office

Also the cisco vpn client is installed on w2k machine. the xp is the problematic machine. in fact i have nothing installed on xp as yet just os, do you think i should install sp2 on it and check.

cheers.

 

[bcastner]

Yes, upgrade to Service Pack 2 on the XP machine.

But just a comment on the CISCO VPN client. Uninstall it. Do the firewall or service pack upgrades. Then reinstall it.

It attempts to identify so many things during installation to adjust itself to your settings, that a removal/reinstall would give you the best of both worlds -- you still have the client, and your LAN begins working.

By the way, that client has been frequently updated. Be certain after removal you reinstall with the current one.

 

[techsavvy1]

Cheers, it actually worked by removing the cisco vpn client. Before i was just denying it form zone lab firewall, but on uninstall xp machine could ping and see my w2k.

Thank you.

 

[bazzert]

Bcastner am I missing something I thought addresses atarting 169.254 were APIPA addreses

 

[bcastner]

There is nothing wrong with APIA addresses, they are perfectly usable.

Where they pose an issue is in the instance where there is a valid DHCP server issuing IANA legal private subnet NAT IPs. Somthing is wrong between the workstation and its conversation with the DHCP server.

As you can see from the discussion above, the CISCO VPN client acts roughly like a firewall, and was interferring with his LAN. The use of Control Panel, Add/Remove Programs to remove the CISCO client, and reinstall, allowed this client to rediscover the needed resources.