Folder Sharing and Networking

[Guest]

I am a system integrator for more than 10 years. Recently there is such above
problems worry me so much.
I discover this problem during my delivery to one of my client 's office. It
was a simple LAN connection to a switch of 2 computers with Windows XP Home.
When delivered the new computer system, I dismantle the loan unit from my
company and replace it with the new PC installation (Windows XP Home).
In normal case, I need only half an hour to connect up the both computer
including setup, maping, printer sharing etc. But it took me more than 2
hours onsite couldn't manage to connect two computer within the same
workgroup.
Hardware:
1 existing Windows XP Home PC with wireless connection to a Linksys router
(no broadband internet connect, only use it as a switch)
- tcpip connection, client for microsoft networks, file and printer sharing
for microsoft networks
- Dynamic IP address from Linksys router.
- All norton internet security uninstall, inclusive antivirus.
---------------------------------------------------------------------------------
- tcpip connection, client for microsoft networks, file and printer sharing
for microsoft networks
- Dynamic IP address from Linksys router.
- AVG antivirus installed.

Senario:
Before replaced with new PC, it was working fine with folder sharing etc.
After setup the new PC, with above configuration, one can not see each others
in the same workgroup. At time it not even can see the workgroup or even can
see the workgroup, it was not able to see the network computers. Sometime
only own computer appear in the workgroup.
I had tried, remove norton security, remove AVG antivirus , remove and
reinstall wireless drivers, assign fix IP for both computer. All matter
tried but no luck!!
And I had no choice to inform client that will come back when solution found.

I gone home and spending another 2 hours at home in my small network with 3
computers which were working and sharing folder all the while. But them, this
time all three computer can not see each others and it was similar to the
problem that I encounter on site. This time it is 3 PCs with Windows XP Pro
install.

I tried figure it out from microsoft forum, newsgroups and tried all
suggested matters, it was not help with guess account turn on (all the while
I turn it off was working), enable netbios over tcpip (was ok with one
computer, then the following day disappear again, and never have change to
see the network again) Netbuei installed. Until I tried using NWlink
IPX/SPX/Netbios compatible Transport Protocol installed. I know this is not
the way to configure the network, but it seem that it is working fine till
now.

Myself , as I said I am a system integrator, I had tried many possibility to
check the connection, ping router IP, ping computer, search computer (can't
locate the computer, sometime it found but was not able to access), static
IP, dynamic IP, added microsoft TCPIP.

It seem that it is windows problem, could be recent KB update issue? Could
someone gether all such issue and take note of the date. It happen somewhere
around 26/1/2006 (which I first discover the problem) Then we might be able
to narrow down to the Microsoft KB update. (Because at once I did try to
remove one at a time in my computer;
KB 908519
KB 912919
KB 905915
KB 910437
KB 896424
KB 896688
until I remove the KB 905414. I restart the computer and work for the day
but no luck for the secequene day. (this was tested with common installation,
tcpip for internet.)

Anyone had similar problem, please post or reply here so that someone can
look into this problem. To me this could be a time bomb, as all my client
using microsoft network, if this is solve, sooner or later will be alot of
them will call for such problems.

Thank in advance who can see this as big issue.

 

[Guest]

Oh, and be sure that you check into the windows firewall exceptions tab and
be sure that file and printer sharing are enabled and set for the correct
scope, say your subnet, etc. or just turn off the firewall as a test...

 

[Guest]

Have had issue many times when removing spy/malware infestations.
Usually, can reset the TCPIP settings with "netsh int ip reset c:\ipreset.log"
which does the same as old w98 uninstall/reinstall tcpip trick accomplished.
see Q299357.
Also, may need to flushh out Winsock2 especially if you see lots of weird
items in msinfo32.exe's components\network\protocol - out of the box there
are @10 items listed, proxy software can add more but the entries look
reasonable. The spy/malware entries are usually not pretty to look at etc.
For this one you have to delete the corrupted registery keys
HKEY_Local_Machine\System\CurrentControlSet\Services\Winsock and Winsock2
then reboot, then you reinstall tcpip by selecting your Lan network
connection in in control panel, properties, then install, protocol, add, have
disk, c:\windows\inf and click ok, select tcpip from list - not to be
confused with tcpip version 6, which is different. after you have done this,
reboot and good luck!>)
p.s. sometimes you have to remove the Lan adapter too!
p.p.s. Be sure to run ms spyware beta 1 and also malware removal tool before
you do anything, or the problem will just keep coming back... you may also
try using adaware with the VX2 removal addon if needed - search adaware's
support section for VX2 removal for info.

 

[Guest]

Thanks for your respond. I had try your suggestion till removed winsock and
winsock2 in NIC properties. But not luck yet. Will try this evening to remove
NIC adapter.

But I can see more and more posting in regards to such issue. I just wonder
any Microsoft engineer to test with 2 computer fully patch with cross wire
trying to simulate the problem. I am sure you will find something strange.

 

[Guest]

I have also found some nic's don't auto negotiate the speed/duplex very well.
In fact some hubs don't either. You might also try using the nic advanced
properties to manually set the speed/duplex for say 10mb and half duplex -
the slowest, then slowly ramp up. The auto feature may not be working as it
should.

 

[Guest]

On a side note: I come from a Novell background, read 1980's 90's, and used
ipx all the time. When the internet happened, I found use for it again, as
unlike netbeui, ipx can be easier to route across lan segments, and since
it's not tcpip, when you share files and prn's on your workgroup using ipx,
you can remove f&p sharing from tcpip, and worry somewhat less about exposing
your lan to the internet, or nosey neighbors if your using wireless.
Nowadays, with XP so ip-centric, and the ability of worms and such to exploit
shares regardless of protocol, I just use ip and load-up on the security
software.

 

[Guest]

Yes, ipx is the most easier protocol for network connection. But thought this
was in the pass, now we are talking about tcpip which is more common use
protocol globally.
The question is I don't understand that why in the pass that network work
with tcpip and now we had to configure the protocol to ipx?
Are we going backward?

Within my service LAN environment, I see all having the same problem
recently. And I was told from another group of desktop support also facing
the same problem. These people are in LAN desktop support for many years.
But, just couldn't understand out of sudden that the network share folder and
workgroup access problem.

Look at the posting under this network discussion. There are more and more
such posting, but I don't see anyone giving good advise. This issue is
nothing to do with adapter, dynamic ip, file sharing turn on or off, switch,
wireless etc. It is quite firm that is from windows update. Because only
windows update can cause all LAN having the similar problem. All working LAN
have different environment with different antivirus installation. If this is
only happen to only one incident, it could be some hardware or configuration
problem. But now it seem that more and more Windows user having such problem.

I would appreciate that any Mcrosoft Engineer here that can trigger this
issue to the development team to find oout the cause of it.

 

[Guest]

I guess a large part of it is MS' server centric point of view. If you have
windows server 2003 with Exchange Server supporting domain logins on XP Pro
then everything is easier. Outlook is easier. logins are easier, you get real
security on your shared files locally... Instead of letting p2p be developed
fully, ms just cuts out major security and authentication abilities from XP
Pro and then cuts even more from XP Home. With Home you can't even put a
password on a local share: W95 can do that! So every one who buys a DELL home
computer who wants to share files between their home desktop and work laptop
must also expose their data to neo-hacker junior with his spyware infested
kazaa/winmx gamer pc! I just had to figure out how to let a home client of
mine let a tenent they rent a small bedroom to share cable internet access
without exposing their own home office pc's shared folders... They have XP
Home, so I had to add a second router just for the tenent to use and cascade
them so that each was on a different network so that the tenent couldn't
browse the owner's pc's! When they had all W95/98 pc's I just put a password
on the share and was reasonably safe. Anyway, sorry for the rant... p2p is
here to stay, but security is sorely lacking at the most rudimentary levels,
unless you spend some big bucks! Frustrating... I guess I should look for a
3rd party addon secuity app just for local shares...

 

[sini008]

see i'm a System admin & I had not faced this type of severe
situations u had got. I think there is nothing wrong in the OS, the
type of problem u r facing is
1. may be the Ethernet card defect.
2. may be the cross wire problem.
3. network installation problem.
4. Network Driver installation may be wrong or search for the new
driver file.
suggestion from me is ,
1. replace the ethernet card with another which is working & check.
2. check the cross wire connection with 2 working n/w PC's
3. remove physically the Lan card then boot, check if any network card
driver file is there in Device manager. If not shutdown , put lan card
boot.If it detects automatically its fine or try some other thing.
also if gets installed then open N/w places-right click lan properties
- lan properties -advanced see the windows firewall is not enabled. if
its enabled then disable it.
try
a. ping <IP_address of local system>
b. run \\<local computer name> & reply to me abt ur situation to
(e-mail address removed). I'll definitely try to solve the problem.
4. check for the Driver in the Internet & install.

sini
Bangalore, India

 

[Guest]

Hi sini

Sorry! I didn't login here to see your message. I will try your advise and
reply to you. But I still think that Microsoft could be blocking the feature.
Thank you!