If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Win ME & 2000 Networking
I have a 3 computer wireless network using Netgear
adapters. The computer with Windows ME can not browse the other 2 pcs(running XP Home & Win 2000) on the network. The 2000 pc can browse the other 2 pcs and the XP can browse the other 2 pcs. Drives & folders are set for sharing on the other 2 pcs. I can get internet access on all 3 pcs. I can ping from the ME computer to the other 2 pcs. I have all 3 pcs set up in the workgroup named "WORKGROUP". All pcs have file & printer sharing enabled. Netgear suggested installing NetBEUI which I installed on the ME and 2000 pcs, but this did not solve the problem. I also went thru the Windows ME home networking wizard but this did not solve the problem. Any suggestions? |
#2
|
|||
|
|||
In article , "Jerry"
wrote: I have a 3 computer wireless network using Netgear adapters. The computer with Windows ME can not browse the other 2 pcs(running XP Home & Win 2000) on the network. The 2000 pc can browse the other 2 pcs and the XP can browse the other 2 pcs. Drives & folders are set for sharing on the other 2 pcs. I can get internet access on all 3 pcs. I can ping from the ME computer to the other 2 pcs. I have all 3 pcs set up in the workgroup named "WORKGROUP". All pcs have file & printer sharing enabled. Netgear suggested installing NetBEUI which I installed on the ME and 2000 pcs, but this did not solve the problem. I also went thru the Windows ME home networking wizard but this did not solve the problem. Any suggestions? I disagree with Netgear, Jerry. In my experience, adding a protocol to a malfunctioning Windows network can make the problem worse, especially when XP is involved. Even if the network works after adding another protocol, it won't work optimally, because the additional protocol is a bandage covering up a basic problem that still exists. It's better to fix the basic problem and have an optimal network setup. Remove NetBEUI from all computers, and make sure that TCP/IP is the only protocol. Is the problem that ME can't see the other computers at all? If so, make sure that: 1. A firewall program isn't blocking access, and: 2. NetBIOS over TCP/IP is enabled on all computers. 3. Browse Master is disabled on ME. Is the problem that ME sees the other computers but can't access the shared disks and folders that it sees because "access is denied"? If so, create matching user accounts on all computers, with the same user name and password. -- Best Wishes, Steve Winograd, MS-MVP (Windows Networking) Please post any reply as a follow-up message in the news group for everyone to see. I'm sorry, but I don't answer questions addressed directly to me in E-mail or news groups. Microsoft Most Valuable Professional - Windows Networking http://mvp.support.microsoft.com Steve Winograd's Networking FAQ http://www.bcmaven.com/networking/faq.htm |
#3
|
|||
|
|||
On Sun, 15 Aug 2004 22:15:29 -0600, "Steve Winograd [MVP]"
wrote: In article , "Jerry" wrote: I have a 3 computer wireless network using Netgear adapters. The computer with Windows ME can not browse the other 2 pcs(running XP Home & Win 2000) on the network. The 2000 pc can browse the other 2 pcs and the XP can browse the other 2 pcs. Drives & folders are set for sharing on the other 2 pcs. I can get internet access on all 3 pcs. I can ping from the ME computer to the other 2 pcs. I have all 3 pcs set up in the workgroup named "WORKGROUP". All pcs have file & printer sharing enabled. Netgear suggested installing NetBEUI which I installed on the ME and 2000 pcs, but this did not solve the problem. I also went thru the Windows ME home networking wizard but this did not solve the problem. Any suggestions? I disagree with Netgear, Jerry. In my experience, adding a protocol to a malfunctioning Windows network can make the problem worse, especially when XP is involved. Even if the network works after adding another protocol, it won't work optimally, because the additional protocol is a bandage covering up a basic problem that still exists. It's better to fix the basic problem and have an optimal network setup. Remove NetBEUI from all computers, and make sure that TCP/IP is the only protocol. Is the problem that ME can't see the other computers at all? If so, make sure that: 1. A firewall program isn't blocking access, and: 2. NetBIOS over TCP/IP is enabled on all computers. 3. Browse Master is disabled on ME. Is the problem that ME sees the other computers but can't access the shared disks and folders that it sees because "access is denied"? If so, create matching user accounts on all computers, with the same user name and password. Steve, How do you disable Browse Master on ME? Thank you, Lou |
#4
|
|||
|
|||
In article , Lou
wrote: Steve, How do you disable Browse Master on ME? Thank you, Lou 1. Go to Control Panel | Network. 2. Double click "File and Printer Sharing" in the list of components. 3. Specify "Disabled" as the value for Browse Master. -- Best Wishes, Steve Winograd, MS-MVP (Windows Networking) Please post any reply as a follow-up message in the news group for everyone to see. I'm sorry, but I don't answer questions addressed directly to me in E-mail or news groups. Microsoft Most Valuable Professional - Windows Networking http://mvp.support.microsoft.com Steve Winograd's Networking FAQ http://www.bcmaven.com/networking/faq.htm |
#5
|
|||
|
|||
-----Original Message----- In article , Lou wrote: Steve, How do you disable Browse Master on ME? Thank you, Lou 1. Go to Control Panel | Network. 2. Double click "File and Printer Sharing" in the list of components. 3. Specify "Disabled" as the value for Browse Master. -- Best Wishes, Steve Winograd, MS-MVP (Windows Networking) Please post any reply as a follow-up message in the news group for everyone to see. I'm sorry, but I don't answer questions addressed directly to me in E-mail or news groups. Microsoft Most Valuable Professional - Windows Networking http://mvp.support.microsoft.com Steve Winograd's Networking FAQ http://www.bcmaven.com/networking/faq.htm . I got the Windows ME computer to see the other computers in the network by removing the IPX protocol which was installed along with the TCP/IP protocol. Thanks. |
#6
|
|||
|
|||
In article , "Jerry"
wrote: I got the Windows ME computer to see the other computers in the network by removing the IPX protocol which was installed along with the TCP/IP protocol. Thanks. You're welcome, Jerry. You might have seen messages in this news group that recommend adding the IPX protocol as a necessary step in solving all networking problems. That advice appears here so often that some people who haven't tried it might think that it must be true. You've confirmed what I've been saying for years: 1. Windows networks work best with the same single protocol on all computers. 2. Adding another protocol, even on just one computer, can make the network unreliable. -- Best Wishes, Steve Winograd, MS-MVP (Windows Networking) Please post any reply as a follow-up message in the news group for everyone to see. I'm sorry, but I don't answer questions addressed directly to me in E-mail or news groups. Microsoft Most Valuable Professional - Windows Networking http://mvp.support.microsoft.com Steve Winograd's Networking FAQ http://www.bcmaven.com/networking/faq.htm |
#7
|
|||
|
|||
The only advice I have seen about IPX is for DIAGNOSING networking problems.
I don't see any post that says it's required or recommended as a permanent solution or requirement for networking. So, if you're referring to my tips, you've obviously misunderstood them. If IPX solves the networking problem, some people just leave it alone because it works and they are frustrated and don't want to diagnose any further. That's entirely their choice. It's up to the end user to make that decision and not a requirement or pre-requisite of a 'properly configured' or 'working network.' Hope that clears up any mis-understanding. Carey "Steve Winograd [MVP]" wrote in message ... In article , "Jerry" wrote: I got the Windows ME computer to see the other computers in the network by removing the IPX protocol which was installed along with the TCP/IP protocol. Thanks. You're welcome, Jerry. You might have seen messages in this news group that recommend adding the IPX protocol as a necessary step in solving all networking problems. That advice appears here so often that some people who haven't tried it might think that it must be true. You've confirmed what I've been saying for years: 1. Windows networks work best with the same single protocol on all computers. 2. Adding another protocol, even on just one computer, can make the network unreliable. -- Best Wishes, Steve Winograd, MS-MVP (Windows Networking) Please post any reply as a follow-up message in the news group for everyone to see. I'm sorry, but I don't answer questions addressed directly to me in E-mail or news groups. Microsoft Most Valuable Professional - Windows Networking http://mvp.support.microsoft.com Steve Winograd's Networking FAQ http://www.bcmaven.com/networking/faq.htm |
#8
|
|||
|
|||
In article , "Carey Holzman"
wrote: I got the Windows ME computer to see the other computers in the network by removing the IPX protocol which was installed along with the TCP/IP protocol. Thanks. You're welcome, Jerry. You might have seen messages in this news group that recommend adding the IPX protocol as a necessary step in solving all networking problems. That advice appears here so often that some people who haven't tried it might think that it must be true. You've confirmed what I've been saying for years: 1. Windows networks work best with the same single protocol on all computers. 2. Adding another protocol, even on just one computer, can make the network unreliable. The only advice I have seen about IPX is for DIAGNOSING networking problems. I don't see any post that says it's required or recommended as a permanent solution or requirement for networking. So, if you're referring to my tips, you've obviously misunderstood them. If IPX solves the networking problem, some people just leave it alone because it works and they are frustrated and don't want to diagnose any further. That's entirely their choice. It's up to the end user to make that decision and not a requirement or pre-requisite of a 'properly configured' or 'working network.' Hope that clears up any mis-understanding. Carey Your web site doesn't mention any form of the word "diagnose". It claims to "fix every peer-to-peer networking problem that anyone has ever reported over two years with Windows". Your first tip says to install IPX, and you insist that people follow your steps: "If you want your network to work properly, you must follow each step exactly." Your web site doesn't say to remove IPX after diagnosing or fixing a problem. I've diagnosed and fixed problems on dozens of networks in person, and I've diagnosed and fixed problems on thousands of networks in the news groups, without ever installing IPX, recommending that someone else install IPX, or following the other steps on your web site. -- Best Wishes, Steve Winograd, MS-MVP (Windows Networking) Please post any reply as a follow-up message in the news group for everyone to see. I'm sorry, but I don't answer questions addressed directly to me in E-mail or news groups. Microsoft Most Valuable Professional - Windows Networking http://mvp.support.microsoft.com Steve Winograd's Networking FAQ http://www.bcmaven.com/networking/faq.htm |
#9
|
|||
|
|||
I may have to make that clarification, as it was once there on my web-site,
but it has been through several revisions and through such, may have been lost in the shuffle. It's all well and good that your diagnosis technique does not require IPX. I'm sure you'll agree there is more than one way to diagnose any computer problem. I can only speak for what has personally worked for me. I have resolved each and every network problem I've ever encountered using my techniques. That is my experience. I cannot speak or promote your experience over mine, except to say that what works for you may not work or be acceptable to others, and my tips are no different in that respect. What concerns me is that you seem to suggest I am some how profiting and/or endangering the stability or reliability when you make libelous claims. What do you suppose my motivation is? What goal do you think I am trying to accomplish? I assure you, we're both here for the same purpose. We should be backing up and supporting each other, even though our ways are different. That's what enriches this forum - diversity. I had a company redesign and maintain my site. I will double check to see if the "This is not a how-to INSTALL, but rather a how-to DIAGNOSE" statement was somehow left out of the revised page. Had you (or anyone else) brought that to my attention, I would have had it corrected sooner. Thanks for your understanding and cooperation. Carey "Steve Winograd [MVP]" wrote in message ... In article , "Carey Holzman" wrote: I got the Windows ME computer to see the other computers in the network by removing the IPX protocol which was installed along with the TCP/IP protocol. Thanks. You're welcome, Jerry. You might have seen messages in this news group that recommend adding the IPX protocol as a necessary step in solving all networking problems. That advice appears here so often that some people who haven't tried it might think that it must be true. You've confirmed what I've been saying for years: 1. Windows networks work best with the same single protocol on all computers. 2. Adding another protocol, even on just one computer, can make the network unreliable. The only advice I have seen about IPX is for DIAGNOSING networking problems. I don't see any post that says it's required or recommended as a permanent solution or requirement for networking. So, if you're referring to my tips, you've obviously misunderstood them. If IPX solves the networking problem, some people just leave it alone because it works and they are frustrated and don't want to diagnose any further. That's entirely their choice. It's up to the end user to make that decision and not a requirement or pre-requisite of a 'properly configured' or 'working network.' Hope that clears up any mis-understanding. Carey Your web site doesn't mention any form of the word "diagnose". It claims to "fix every peer-to-peer networking problem that anyone has ever reported over two years with Windows". Your first tip says to install IPX, and you insist that people follow your steps: "If you want your network to work properly, you must follow each step exactly." Your web site doesn't say to remove IPX after diagnosing or fixing a problem. I've diagnosed and fixed problems on dozens of networks in person, and I've diagnosed and fixed problems on thousands of networks in the news groups, without ever installing IPX, recommending that someone else install IPX, or following the other steps on your web site. -- Best Wishes, Steve Winograd, MS-MVP (Windows Networking) Please post any reply as a follow-up message in the news group for everyone to see. I'm sorry, but I don't answer questions addressed directly to me in E-mail or news groups. Microsoft Most Valuable Professional - Windows Networking http://mvp.support.microsoft.com Steve Winograd's Networking FAQ http://www.bcmaven.com/networking/faq.htm |
#10
|
|||
|
|||
Steve,
As a symbol of my sincerity in truly wanting to help others with regards to the information contained on my web-site, I make you this offer: If there is any additional installation/diagnostic information you would like to see to make my page 'acceptable' in your eyes, submit it to me in e-mail and I make certain that it gets added, word-for-word, to the site with full credit to you. There is no space limitation and you will be free to add anything you feel would be an alternative or more complete solution to what is already offered there. If you are unwilling to do that, then I ask you with all due respect to please cease any future disparaging comments about my site or tips. Carey "Steve Winograd [MVP]" wrote in message ... In article , "Carey Holzman" wrote: I got the Windows ME computer to see the other computers in the network by removing the IPX protocol which was installed along with the TCP/IP protocol. Thanks. You're welcome, Jerry. You might have seen messages in this news group that recommend adding the IPX protocol as a necessary step in solving all networking problems. That advice appears here so often that some people who haven't tried it might think that it must be true. You've confirmed what I've been saying for years: 1. Windows networks work best with the same single protocol on all computers. 2. Adding another protocol, even on just one computer, can make the network unreliable. The only advice I have seen about IPX is for DIAGNOSING networking problems. I don't see any post that says it's required or recommended as a permanent solution or requirement for networking. So, if you're referring to my tips, you've obviously misunderstood them. If IPX solves the networking problem, some people just leave it alone because it works and they are frustrated and don't want to diagnose any further. That's entirely their choice. It's up to the end user to make that decision and not a requirement or pre-requisite of a 'properly configured' or 'working network.' Hope that clears up any mis-understanding. Carey Your web site doesn't mention any form of the word "diagnose". It claims to "fix every peer-to-peer networking problem that anyone has ever reported over two years with Windows". Your first tip says to install IPX, and you insist that people follow your steps: "If you want your network to work properly, you must follow each step exactly." Your web site doesn't say to remove IPX after diagnosing or fixing a problem. I've diagnosed and fixed problems on dozens of networks in person, and I've diagnosed and fixed problems on thousands of networks in the news groups, without ever installing IPX, recommending that someone else install IPX, or following the other steps on your web site. -- Best Wishes, Steve Winograd, MS-MVP (Windows Networking) Please post any reply as a follow-up message in the news group for everyone to see. I'm sorry, but I don't answer questions addressed directly to me in E-mail or news groups. Microsoft Most Valuable Professional - Windows Networking http://mvp.support.microsoft.com Steve Winograd's Networking FAQ http://www.bcmaven.com/networking/faq.htm |
|
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
wanting to upgrade to 2000 | Lisa | General | 2 | August 12th 04 08:05 PM |
FAQ: Win98 users: Upgrading to WinXP, IE6, etc. | JM | Setup & Installation | 6 | July 26th 04 01:44 PM |
FAQ: Win98 users: Upgrading to WinXP, IE6, etc. | JM | Improving Performance | 6 | July 26th 04 01:44 PM |
Downgrade Windows 2000 Server to Windows ME | Derek Erb | Setup & Installation | 4 | July 19th 04 04:21 PM |
Dual Boot with windows 2000 | jc | General | 6 | June 18th 04 02:11 PM |