XPSP2 Networking nightmare

[cwyman]

I have 1 computer with XPSP1 and a laptop with XPSP2. They are on a DHCP peer to peer environment. Yesterday I managed to get both machines to see each other and map to each other with little difficulty. Today, the XPSP1 can see itself in the Workgroup Computers view, but not the XPSP2. When I click on View workgroup computers on the XPSP2 I get <Worgroup> is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions. The list of servers forthis workgroup is not currently available.

The XPSP2 can access the share drive on XPSP1 only by going through IE and putting in \\ipaddress\share drive name, but cannot view through workgroup computers nor mapping a drive.

The XPSP1 cannot access XPSP2 no matter what method. It can see the XPSP2 if I turn off the firewall on XPSP2, but it still cannot map a drive.

Any thoughts on what I can do here. I need to figure out all the loopholes for XPSP2 so that I can make sure I can support this when it comes out next month.

TIA,

Carrie

 

[bcastner]

I have not had this problem. Under the Firewall, Exceptions, double-click File and Printer Sharing, Change Scope, and select Subnet.

 

[linney]

Is this any use to you?

http://www.microsoft.com/technet/community/columns/cableguy/cg0204.mspx

 

[MasterofNone]

Not surprised your having network problems with SP2 as MS has decided to mess about with TCP/IP, and managed to make a right pigs ear of it. The following is a very common issue and whilst this is not your problem, yours could be a further problem with the TCP/ip stack.

'TCP/IP has reached the security limit imposed on the number of concurrent TCP connect attempts'.

Apparently the error is something to do with timeouts, but is causing the tcp stack to shutdown. This will be remedied in the final SP2 (hopefully)

 

[cwyman]

I'm going to try and start over from the beginning here. I tried the add scope bit, but that didn't seem to work so I am going to restore back to the day before I upgraded to XPSP2 and make sure that all of my networking ducks are in a row and then try to upgrade again.

My theory is that the day before I upgraded I was trying to setup sharing between my two computers and was experiencing a similar problem. So in going back to that day I did perform a critical upgrade of about 4 or 5 patches so we shall see if it isn't the patches causing the problems.

If it is then I shall restore to prior to the patch installation and respond here to let everyone know what I find.

Wish me luck

 

[cwyman]

Okay step 1 complete. Restored back to day ms critical updates were patched but before SP2. I was indeed still showing signs of networking problems, but before I went and did another restore I checked my firewall. Did I forget about that?!?!?! Okay, well, I added my address range to the firewall and holy cow I see both machines and map to each other .

Now working on step 2 - going back to SP2. Keeping you up to date on the latest saga of MS SVU

 

[MasterofNone]

Would suggest ignoring SP2 until the bugs are worked out. why bill felt the need to mess with the TCP/IP stack I will never know

 

[cwyman]

Good news today....

Upgraded to SP2 and now seems all hunky dory!! Both machines can still see and map to each other.

Apparently I'm too stupid to remember that in addition the the Windows firewall I also have to configure my Norton Firewall.

I guess the reason I really forgot is my engineer is using me as a guinea pig for DHCP on our network and so my IP range actually changed from it's original range!!

Oh well, live and learn I always say.

I wish I could say that SP2 was all fun a glory, but Siebel 7.5 doesn't play well AT ALL!!! But that's another story.

See ya at the next post