Problem networking XP and Vista

Glad you found the problem :grinthumb

Yup, ATT Global Net would be just the extra software to have interfered.

Remember what i said about Windows Network not reflecting firewall changes immediately? wait 15 minutes or simply reboot and see if it still reports "seeing" those resources when ping doesn't work. Am pretty sure ping is required for file and printer sharing to work.

/**** Edit ****/
But do let me know if you find it otherwise (i.e. resources continue to be seen and you can actually contineu to access shared resources when ping doesn't work)

Yes I saw Lotus notes in your log
But I would actually like to see another Procexp.txt attached (from Vista, I believe)

I'd like to know which Startup affected this, or even if running this would have helped from the command line:

netsh winsock reset
netsh int ip reset
netsh interface ip delete arpcache

Wow! I guess I had miss this posting.. I guess the user is all set and running with 'Vista and XP together.

Yes which link would have you posted

AT&T Global Network Client Version 7.4.1 Beta Available

Managed VPN Edition
ftp://ftp.attglobal.net/pub/client/win32/beta/agnc_vpn.exe

I believe this version is suppose to fix the issue of SP1 in full
If you still require AT&T Global Network Client, please download the latest (above) 7.4.1 Beta

here is the process explorer result...

that kimsland wanted

ALSO. LookinAround wrote, "But do let me know if you find it otherwise (i.e. resources continue to be seen and you can actually contineu to access shared resources when ping doesn't work)"

I can report that I can still access shared resources despite being unable to ping either computer from the other. I believe the firewalls are interfering with the ping because pinging succeeds when the firewalls are turned off. Regardless, file & printer sharing are working fine (fingers crossed).

Well, thank YOU for that update. I'll have to look further into that.

That's correct. Many firewalls can disable ping replies

Ping is seldomly required, but when you enable the FW, be sure to allow
ports 139 udp and 445 tcp for all local lan addresses in both directions.

As an fyi to all....It seems it's some firewalls that are creating the dependency between ping and File and Printer Sharing!

After looking into it further, it appears there’s good reason for confusion about any dependency between ICMP ping request/replies and File and Printer Sharing (FPS). I found at least two firewalls that create that dependency (tho I don’t know why as it appears it’s not necessary for FPS functionality. Ping is damn helpful as a diagnostic tool for FPS tho apparently not required for FPS to actually work)

1. Windows Firewall
   MS own implementation of Windows Firefall (WF) was probably first in starting the confusion. In WF
   • By default: ICMP ping requests and File and Printer Sharing ports are blocked
   • Enabling File and Printer Sharing opens ports: TCP 139, 445 and UDP 137, 138
   • When port TCP 445 is enabled WF automatically enables ICMP ping
   • If you go to to WF Settings Advanced/ICMP you find WF doesn’t allow you to disable ICMP ping. In fact, you see a description “Requests of this type are automatically allowed if TCP port 445 is enabled”
2. AVG 7.5 Firewall
   I happen to use AVG 7.5 Internet Security Suite.
   • I’ve had File and Printer sharing enable in the AVG firewall and running a long while on my home network
   • While looking into the problem the OP reported in this thread, I wanted to do a test on my own hardware with ping disabled. I modified the firewall rule found under System/Replies on ICMP diagnostics. I changed the rule to block inbound ping requests. When I hit OK AVG gave me a pop-up “warning” message:
     
     “Disabling PING may have bad effects on File and Printer Sharing: If you block this system service or protocol Microsoft fsp will be blocked too. Are you sure you want to blcok this service?”
     After hitting yes, I found File and Printer Sharing no longer worked. In fact, looking into it further I found AVG actually disabled the File and Printer sharing rule!

open port 137 and the need for ping should disappear. MS port 135 is the name