RE: Folder Sharing and Networking

Tech-Archive recommends: Fix windows errors by optimizing your registry

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.

"tnetinc" wrote:

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.

"Patrick" wrote:

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.

.

Relevant Pages

  • Re: 2503/WS-1103 intermittant ping
    ... blade installed on my network. ... The router seems to perform OK except ... when I ping the ethernet connection, I only get back every other ping. ... BRI0 is administratively down, line protocol is down ...
    (comp.dcom.sys.cisco)
  • Re: DECnet, LAT, Cterm over IP/GRE - Timeout?
    ... Brief use of MOP protocol. ... Exclusively LAT protocol. ... Was a CTERMconnection like described in #5 set up at the same time? ... TCP/IP is more tolerant of some types of network disturbances than LAT ...
    (comp.os.vms)
  • Re: About Information Hiding Design Rules
    ... EALREADY Connection already in progress ... ENETRESET Connection aborted by network ... ENOTCONN The socket is not connected ... EPFNOSUPPORT Protocol family not supported ...
    (comp.lang.c)
  • Re: XP file sharing problem
    ... Insert your Windows XP CD into the CD-ROM drive and browse to the ... Click Protocol, and then click Add. ... Double click the Network icon and click the Configuration tab. ... Click Close to close the "Local Area Connection Properties" dialog box. ...
    (microsoft.public.windowsxp.network_web)
  • Re: SQLExpresss losing connection to VB6 application
    ... the server, the un-avaibility of a network protocol, firewall setting, ... there is a disconnection of the external network. ... I would suggest to try using a named pipe in all times with SQL-Express ... Troubleshooting connection problem: ...
    (microsoft.public.sqlserver.connect)