barkin
asked on
WinXP-Win2k Home Network Probs. Help.
I have two computers, one running Win2K and the other running WinXP. Both have installed NetBEUI and TCP/IP protocols for local networking as well as internet access. Both PCs connect directly into a HUB, and the hub connects to the cable modem. We both have ZoneAlarm Pro installed.
This setup has worked well (until recently) allowing us to share files between PCs and connect to the interent. I've been hearing that NetBEUI is dead and to go exclusively TCP/IP for local networking and internet access. Unfortunately without NetBEUI we were completely unable to communicate between PCs.
1. With our current network layout how exactly do I get local networking (and retain internet access) without NetBEUI installed?
2. Originally the setup had one PC as Win2K and the other Win98SE. The network layout was identical to what I have now only the local networking was much more snappier. That is, when I accessed the LAN folder of the other PC the connection would be established in about 1 sec allowing me to peruse the other PCs file system. Now with the Win2K-WinXP setup this connection can take about 1 minute and even then I can receive an error message stating the folder is unaccessable. After about 5 minutes the folder will be available. Why is local networking between Win2K-WinXP so much slower compared to my old setup?
3. Only recently my WinXP system has been having troubles transferring files between local PCs. The transfer rate was normally perhaps 1 meg/sec (or so, maybe more) and now its a miserable 30kb/sec. The system just crawls. What happened?
This setup has worked well (until recently) allowing us to share files between PCs and connect to the interent. I've been hearing that NetBEUI is dead and to go exclusively TCP/IP for local networking and internet access. Unfortunately without NetBEUI we were completely unable to communicate between PCs.
1. With our current network layout how exactly do I get local networking (and retain internet access) without NetBEUI installed?
2. Originally the setup had one PC as Win2K and the other Win98SE. The network layout was identical to what I have now only the local networking was much more snappier. That is, when I accessed the LAN folder of the other PC the connection would be established in about 1 sec allowing me to peruse the other PCs file system. Now with the Win2K-WinXP setup this connection can take about 1 minute and even then I can receive an error message stating the folder is unaccessable. After about 5 minutes the folder will be available. Why is local networking between Win2K-WinXP so much slower compared to my old setup?
3. Only recently my WinXP system has been having troubles transferring files between local PCs. The transfer rate was normally perhaps 1 meg/sec (or so, maybe more) and now its a miserable 30kb/sec. The system just crawls. What happened?
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.
Windows XP Networking Snafus Fixed (maybe)
Many of you have written to me about problems with File Sharing on Windows XP computers. I feel your pain! I've
experienced the same problem and for the life of me, I could not figure out what the deal was. Jim Brady wrote in
to me and shared this very helpful info:
"Tom,
A frustrating problem I often see on message boards for XP goes like this:
On my home/office network, I used to be able to access files and subfolders that are in my XP machine, which is
the server. Now, I get an error that doesn't make any sense: "you may not have permission to access this
resource. Check with your network administrator." And in the same error box, a second note: "Not enough server
storage to process this command" Turns out, it's a cure for the common anti-virus. When installing NAV and other
antivirus programs, they alter a registry key that XP depends on for simple network tasks. Elusive, because MS
lists the fix under NT. Of course, Windows XP networking is based on the NT kernel. SO HERE IS THE FIX that
worked for me.
Quoting MS:
To resolve this behavior, increase the IRPStackSize value on the server: Click Start , and then click Run . Type
regedt32 , and then click OK . Navigate to the following key:
HKEY LOCAL MACHINE\System\CurrentCont
In the right pane, double-click the IRPStackSize value.
NOTE: If the IRPStackSize value does not already exist, use the following procedure to create it:
In the Parameters folder of the registry, right-click the right pane. Point to New, and then click DWord Value. Type
IRPStackSize.
IMPORTANT: Type "IRPStackSize" exactly as it is displayed because the value name is case-sensitive.
Change the Base to decimal. In the Value Data box, type a value that is larger than the value that is listed. If you
created the IRPStackSize value using the procedure described in step 4, the default value is 15. It is recommended
that you increase the value by 3. Therefore, if the previous value was 11, type 14 , and then click OK. Close the
Registry Editor. Restart the computer. If the problem persists after you complete the preceding procedure, try to
increase the value of IRPStackSize even more. The maximum value for Windows 2000 is 50 (0x32 hex)"
-------------
I hope this helps !
Many of you have written to me about problems with File Sharing on Windows XP computers. I feel your pain! I've
experienced the same problem and for the life of me, I could not figure out what the deal was. Jim Brady wrote in
to me and shared this very helpful info:
"Tom,
A frustrating problem I often see on message boards for XP goes like this:
On my home/office network, I used to be able to access files and subfolders that are in my XP machine, which is
the server. Now, I get an error that doesn't make any sense: "you may not have permission to access this
resource. Check with your network administrator." And in the same error box, a second note: "Not enough server
storage to process this command" Turns out, it's a cure for the common anti-virus. When installing NAV and other
antivirus programs, they alter a registry key that XP depends on for simple network tasks. Elusive, because MS
lists the fix under NT. Of course, Windows XP networking is based on the NT kernel. SO HERE IS THE FIX that
worked for me.
Quoting MS:
To resolve this behavior, increase the IRPStackSize value on the server: Click Start , and then click Run . Type
regedt32 , and then click OK . Navigate to the following key:
HKEY LOCAL MACHINE\System\CurrentCont
In the right pane, double-click the IRPStackSize value.
NOTE: If the IRPStackSize value does not already exist, use the following procedure to create it:
In the Parameters folder of the registry, right-click the right pane. Point to New, and then click DWord Value. Type
IRPStackSize.
IMPORTANT: Type "IRPStackSize" exactly as it is displayed because the value name is case-sensitive.
Change the Base to decimal. In the Value Data box, type a value that is larger than the value that is listed. If you
created the IRPStackSize value using the procedure described in step 4, the default value is 15. It is recommended
that you increase the value by 3. Therefore, if the previous value was 11, type 14 , and then click OK. Close the
Registry Editor. Restart the computer. If the problem persists after you complete the preceding procedure, try to
increase the value of IRPStackSize even more. The maximum value for Windows 2000 is 50 (0x32 hex)"
-------------
I hope this helps !
barkin:
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 a recommendation in the Cleanup topic area that this question is:
PAQ / Split points between edmonds_robert and lrmoore
Please leave any comments here within the next seven days.
PLEASE DO NOT ACCEPT THIS COMMENT AS AN ANSWER!
Dimante
EE Cleanup Volunteer
I will leave a recommendation in the Cleanup topic area that this question is:
PAQ / Split points between edmonds_robert and lrmoore
Please leave any comments here within the next seven days.
PLEASE DO NOT ACCEPT THIS COMMENT AS AN ANSWER!
Dimante
EE Cleanup Volunteer
ASKER