aussie

Quote: Replacing the NIC was not your problem. YOU are the problem. The first thing that comes to mind when reading your reply is how RUDE you really are. It is not me who is a problem, it is you who is RUDE. Judging by the number of posts in your stats, I'm hopeing that somewhere in all your 1300+ posts, you were at least some help to somebody looking for help in these forums instead of being insulted by your rotten mouth and your poor use of the english language. Quote: No. MS doesn't "require" you to do jack. They also "commonly" frequently suggest editing the registry whenever you search their knowledgebase. So NO MS doesn't "require" you to edit the registry but if you want to fix/tweak a setting then you HAVE to. ??? Didn't know MS made up people's own security policies. Just because MS leave's protocols out of their OS's and/or recommends other protocols does not mean that those protocols are ideal for the situation and "messing" around with network properties is required if your setting up a network. I don't know how the heck you do it....magic? I never mentioned security policies, you did and since you did my reply is "I KNOW THAT!" I was simply stating that my setup was left at default and IPX was not loaded. Read my msg again! Quote: Their "intent" is to sell an OS to the masses with these "HUGE" features, that being their overriding goal they tend to forget all of the smaller (while no means less important) things that make up the OS. This is bad. Dos,9x,NT..All needed to be tweaked. Linux needs to be tweaked. Mac's need to be tweaked. There are various levels of "tweakage" but all to some degree require tweakage....and it never ends. UNLESS you buy a webtv/console....well even then. No. It's the U-S-E-R in almost 95% of all situations. In networking that percentage drops quite a bit but it's still pretty high. A SIMPLE answer? There are tons of different network configurations that can be configured throughout the world with XP. Just because your network was so simple to setup does not mean that it should be/will be for everyone else.....and now you can't duplicate it because you replaced your NIC. ;( I think you need to redefine your definition of tweakage.....and you definetly need more experience in computer maintentance,marketing, and networking. The rest of your message was not even worth replying to. It simply lacks substance and continuity. Your communication skills are seriously lacking. Get an education will you. :ROLLEYES

Laugh! well if thats what you do whilst sitting at your computer then good on you. Enjoy yourself. Thats what life is all about, NOT!

I have read messages after messages, in this forum, regarding all the tweaks and hacks you guy are doing to get your systems networked. This has got to be totally un-necassary because my network was working flawlessly at one stage. My stupid mistake has left me angry and frustrated now of over 5weeks with being unable to communicate with WinXP and Win2k properly. What was that big mistake i make? I removed the nic and replaced it with another after installing WinXP, thats what! When i replaced the nic i continued to have problems which i have not been able to resolve. No matter what do. I have followed every recommendation in these forums and nothing works. The motto of the story is, dont touch anything thats not broke. Think about it guys. Do you really think that MS requires users to go into the registry to delete keys so as to remove the lag time it takes to connect to another machine? Do you really think that M.S. requires users to unclick on firewall, enable IPX and mess around with the network properties like that? Do you seriously believe that their intention is to get you to enable Simple networking and and frustrate you to no end before you get a simple peer to peer network working? What kind of viable product would they have if the average user had to tweak their system to no end. This doesnt make any sense. Is it a question of hardware compatability? Could be! Has anyone tried? Those users who have working networks the first time. Do they all pretty much have the same setup(network cards, sound cards, routers, nics? etc)? What brand of nics are those users using, who got their networking portion working the first time without having to load IPX? This is where we should be looking for our answers. Could one of those users who installed XP and got the networking portion working the very first time please list their configuration? Nope, i think there is a simple answer to all of the above. Its not called "LET TWEAK XP AND GET IT TO WORK". If tweaking is the answer then how can one explain that my network worked the very first time after installing XP? Everything and i mean everthing was set at default!!!!!!!!!!! Just set up my network thru the wizard and away she went. We even copied 800 mp3 files from my win2k system to a folder on XP without incident. Something that i cannot duplicate since i replaced my nic. Food for thought guys. Think about it!

How does one set up wmiprvse as a service. What i thought was the WMI Performance Adapater in the service and setting it to automatic did not start on bootup. I then created it in the startup folder. It still refused to stat automically. There has to be an option better way than typing WMIPRVSE in run evertime you log on. Why on earth would MS create such a flaw in their program design. I can now browse my network system if i type this command but im not crazy about removing the key to do it. There must be another way to get this going without modifying the registry. -Thanks

Quote: Have you tried to enable/disable "Simple File Sharing" on the XP box? Yes i forgot to mention that is disabled on XP. Do i really have to enable IPX/SPX on both systems for this to work? I did that already, worked fine till i rebooted the xp system then once again the were huge pauses when attempting to go over to Win2k. I will say this however, when i first installed, CLEAN INSTALLED, winxp i have all of this working flawlessly. It just worked the first time thru. Then i did something stupid. I removed the Netgear nic and replaced it with a Linksys. Why did i do this? Well i heard reports that Netgear was incompatible with some mobo's. So then i put the Netgear nic back in the XP machine thinking it was somehow related to registering of hardware during installation of XP. Even when i replaced it i was still having the problems. Now i remember the setup. Origionally when this was all working IPX/SPX was not loaded. So im not sure what this thing is doing. Also after installing XP and had this working Simple Networking was enabled and everthing was working. Hmmmmmmm

I need to explain this again. None of the info above is related to the problem im having: I have the following setup: My host computer is a Win2k system: Tcp/IP w/Netbios setting from DHCP Server have also tried enable netbios of tcp/ip NO GOOD! Client for Microsoft Networks File and Print Sharing Qos Packet Scheduler Netbeui <---- Without this i cannot see XP Client My client is XP because my roomate is running it: File and Print Sharing Client for Microsoft Networks Tcp/IP w/Netbios enabled over TCP/IP Firewall is off! WMI performance adapter is set to AUTO No network passwords exists. 1) Win2k system can see XP but copying any files to XP folders hangs the win2k system and then i have to cancel out the job. What could be affecting this? I mean once you can see the XP and browse its folders what could possible go wrong in that you cannot copy files over? Get some error msg eventually saying something about unable to recognize the network. 2) Trying to access Win2k from XP hangs the system. We get the login screen but when we click on a network folder everthing just hangs. Well it takes forever to get over to the Win2k system but it eventually does. Can see network printers and even request a printouts without a problem. 3) Both systems can browse the internet without a problem. Thank you

Hello everyone, I have been reading the forum msgs and followed all the instructions i have read in these forums to network Xp and Win2k without much success. Just when i think things are working they fail miserable elsewhere and visa versa. I have followed all directions that RhinoTrip & Deadcat and Trag left but those have not worked. My big problem is getting Xp to recognize my Win2k system. I get the password logon when attempting to log into Win2k from XP but the looooonnggggg pause is simply not acceptable. I do not find any pw's or any strange settings in Network passwords. I have enabled Netbios over TCP/IP on both systems i have even uninstalled my nic and reinstalled it countless times on the XP side. A few users have reported that simply having TCP/IP, File and print sharing for MS networks and client for MS networks should work without a problem but this is not the case when i set those on both systems. At the same time enabling the additional IPX/SPX protocol also wont work. Doing so simply keeps the XP machine hung forever. Sure it eventually connects but after 10min? Now i never have a problem seeing the XP system from Win2k but trying to copy a mp2 file over to a folder on XP will evenutally hang the Win2k system. Both system are bound correctly. What else could i possibly look for? Thanks for your help guys!