samantha20
asked on
Networking ME, Win 98 & DSL Router
Hi,
I have two computers and a netgear DSL Router which I have networked together.
The Router uses DHCP.
Computer One is a Windows ME
Computer Two is a Windows 98
Both computers can successfully access the DSL. Both computers can ping eachother. Computer two can successfully browse computer one. Computer one, however, cannot do the same with Computer two. The "helpful" message is: 'Network is busy'.
Prior to ME, Computer One had windows 98 installed which worked fine.
I have tried reinstalling the drivers to no avail...
Thoughts?
TIA,
Sam
I have two computers and a netgear DSL Router which I have networked together.
The Router uses DHCP.
Computer One is a Windows ME
Computer Two is a Windows 98
Both computers can successfully access the DSL. Both computers can ping eachother. Computer two can successfully browse computer one. Computer one, however, cannot do the same with Computer two. The "helpful" message is: 'Network is busy'.
Prior to ME, Computer One had windows 98 installed which worked fine.
I have tried reinstalling the drivers to no avail...
Thoughts?
TIA,
Sam
Sometimes Windows 98 has a MS Family logon client running on it. Take that off. ANd if AOL is runing it always puts a bunch of junk on. When I come accross a problem slike this I usally just go with the basics , 1-A Client (CLient for MS Networks) 2- the Device (the network card of coarse) 3- Protocol like TCP/IP.
Netbois can sometimes be a pain in the but so of coarse make sure they can atleast ping eachother, maybe wait a few minutes and try it again.
Netbois can sometimes be a pain in the but so of coarse make sure they can atleast ping eachother, maybe wait a few minutes and try it again.
first are they both in the same work group?
can you do a find-->computer and find the other?
also
Assuming your network settings have been properly configured:
The Vnetbios.vxd file might be missing or damaged, or the following registry key might be missing:
HKEY_LOCAL_MACHINE\System\
Try downloading and applying this:
http://download.microsoft.com/download/winme/update/13387/winme/en-us/272991usam.exe
To resolve this behavior if you cannot apply the fix, verify that the Vnetbios.vxd file is in the Windows\System folder, and then verify that there is a registry entry for the file:
1. Click Start, point to Programs, point to Accessories, and then click MS-DOS Prompt.
2. At the command prompt, type cd \, and then press ENTER.
3. Type cd windows, and then press ENTER.
4. Type cd system, and then press ENTER.
5. Type dir vnetbios.vxd /ah, and then press ENTER.
If the file is reported as found, verify that there is a correct registry entry for it. If you receive the "file not found" error message, click Extract File in the System Configuration Utility tool (Msconfig.exe), and then extract the file to the Windows\System folder.
To manually re-create the registry key for the Vnetbios.vxd file, use Registry Editor and create the following key:
HKEY_LOCAL_MACHINE\System\
In the Vnetbios key, create the following values:
Value name: NetClean
Value type: Binary
Value data: 01
Value name: Start
Value type: Binary
Value data: 00
Value name: StaticVxD
Value type: String
Value data: vnetbios.vxd
Warning: Be sure to backup your registry before you do all this!!
can you do a find-->computer and find the other?
also
Assuming your network settings have been properly configured:
The Vnetbios.vxd file might be missing or damaged, or the following registry key might be missing:
HKEY_LOCAL_MACHINE\System\
Try downloading and applying this:
http://download.microsoft.com/download/winme/update/13387/winme/en-us/272991usam.exe
To resolve this behavior if you cannot apply the fix, verify that the Vnetbios.vxd file is in the Windows\System folder, and then verify that there is a registry entry for the file:
1. Click Start, point to Programs, point to Accessories, and then click MS-DOS Prompt.
2. At the command prompt, type cd \, and then press ENTER.
3. Type cd windows, and then press ENTER.
4. Type cd system, and then press ENTER.
5. Type dir vnetbios.vxd /ah, and then press ENTER.
If the file is reported as found, verify that there is a correct registry entry for it. If you receive the "file not found" error message, click Extract File in the System Configuration Utility tool (Msconfig.exe), and then extract the file to the Windows\System folder.
To manually re-create the registry key for the Vnetbios.vxd file, use Registry Editor and create the following key:
HKEY_LOCAL_MACHINE\System\
In the Vnetbios key, create the following values:
Value name: NetClean
Value type: Binary
Value data: 01
Value name: Start
Value type: Binary
Value data: 00
Value name: StaticVxD
Value type: String
Value data: vnetbios.vxd
Warning: Be sure to backup your registry before you do all this!!
ASKER
Thanks for responses. Here's where I am so far
1) no passwords are asked so probably not an issue
2) the VNetBios.vxd was not there but installing the patch did not solve the issue (other than restoring the file)
3) Registry entries are correct
4) both computers can ping eachother
5) The 98 machine can see the ME machine
6) The work groups match between the machines
7) Trying to "find" the 98 machine on the ME machine fails
-Sam
1) no passwords are asked so probably not an issue
2) the VNetBios.vxd was not there but installing the patch did not solve the issue (other than restoring the file)
3) Registry entries are correct
4) both computers can ping eachother
5) The 98 machine can see the ME machine
6) The work groups match between the machines
7) Trying to "find" the 98 machine on the ME machine fails
-Sam
Is something shared on both
file and printer sharing enabled on both?
the NetBIOS (computer) name not more than 15 characters, contains no spaces or special characters
same work group?
file and printer sharing enabled on both?
the NetBIOS (computer) name not more than 15 characters, contains no spaces or special characters
same work group?
also no firewalls?
ASKER
Thanks, Steve - here is latest:
1) yes, directories shared on both
2) yes, file and printer sharing enabled
3) computer name not more than 15 chars
4) yes, same work group
5) no firewalls
6) clicking on network neighborhood on Win ME shows: "Unable to browse the network, network is busy"
-Sam
1) yes, directories shared on both
2) yes, file and printer sharing enabled
3) computer name not more than 15 chars
4) yes, same work group
5) no firewalls
6) clicking on network neighborhood on Win ME shows: "Unable to browse the network, network is busy"
-Sam
ASKER
Thanks, Steve - here is latest:
1) yes, directories shared on both
2) yes, file and printer sharing enabled
3) computer name not more than 15 chars
4) yes, same work group
5) no firewalls
6) clicking on network neighborhood on Win ME shows: "Unable to browse the network, network is busy"
-Sam
1) yes, directories shared on both
2) yes, file and printer sharing enabled
3) computer name not more than 15 chars
4) yes, same work group
5) no firewalls
6) clicking on network neighborhood on Win ME shows: "Unable to browse the network, network is busy"
-Sam
try removing evereything from the properties of network neighborhood, reboot and reinstall
ASKER
... tried it to no avail.
Don't know whether this helps or not:
I made the ME machine the master browser and disabled the same on the 98 machine. Now when I go to network neighborhood I can at least see the 98 machine. If I click on it, however, I still get the network is busy message. Again, the latter is different than what I started with, which was the inability to even drill into network neighborhood. I'm no stranger to networking, having successfully done it with 98 & linux & Win2K. I've got to assume this is a ME specific issue.
-Sam
Don't know whether this helps or not:
I made the ME machine the master browser and disabled the same on the 98 machine. Now when I go to network neighborhood I can at least see the 98 machine. If I click on it, however, I still get the network is busy message. Again, the latter is different than what I started with, which was the inability to even drill into network neighborhood. I'm no stranger to networking, having successfully done it with 98 & linux & Win2K. I've got to assume this is a ME specific issue.
-Sam
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Steven -
I'm on the road until next Monday. I'll try mapping with UNC path then .... thnx for the suggestions
Sam
I'm on the road until next Monday. I'll try mapping with UNC path then .... thnx for the suggestions
Sam
samantha20:
This old question needs to be finalized -- accept an answer, split points, or get a refund. For information on your options, please click here-> http:/help/closing.jsp#1
EXPERTS:
Post your closing recommendations! No comment means you don't care.
This old question needs to be finalized -- accept an answer, split points, or get a refund. For information on your options, please click here-> http:/help/closing.jsp#1
EXPERTS:
Post your closing recommendations! No comment means you don't care.
No comment has been added lately, so it's time to clean up this TA.
I will leave the following recommendation for this question in the Cleanup topic area:
Split: stevenlewis {http:#8265084} & rschuit {http:#8266718}
Please leave any comments here within the next seven days.
PLEASE DO NOT ACCEPT THIS COMMENT AS AN ANSWER!
Julian Crawford
EE Cleanup Volunteer
I will leave the following recommendation for this question in the Cleanup topic area:
Split: stevenlewis {http:#8265084} & rschuit {http:#8266718}
Please leave any comments here within the next seven days.
PLEASE DO NOT ACCEPT THIS COMMENT AS AN ANSWER!
Julian Crawford
EE Cleanup Volunteer
i konw it's a stupid question but... happens.