Slackware This Forum is for the discussion of Slackware Linux.
|
| Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
 |
GNU/Linux Basic Guide
This 255-page guide will provide you with the keys to understand the philosophy of free software, teach you how to use and handle it, and give you the tools required to move easily in the world of GNU/Linux. Many users and administrators will be taking their first steps with this GNU/Linux Basic guide and it will show you how to approach and solve the problems you encounter.
Click Here to receive this Complete Guide absolutely free. |
|
 |
07-21-2005, 04:48 PM
|
#1
|
|
Member
Registered: Dec 2004
Distribution: Slackware
Posts: 104
Rep:
|
when trying to mount a windows share I'm getting
3360: tree connect failed: ERRDOS - ERRnomem (Insufficient server memory to perform the requested function.)
SMB connection failed
Code:
mount -t smbfs //192.168.1.102/backup /mnt/backup -o username=jeff
I can view shares with konquerer just fine, what gives? System should have plenty of memory. This worked fine yesterday and nothing has changed.
|
|
|
|
07-22-2005, 07:22 AM
|
#2
|
|
Senior Member
Registered: Jun 2004
Location: Argentina (SR, LP)
Distribution: Slackware
Posts: 3,145
Rep:
|
Did you by any chance, rebooted (or turned off the Windows machine) without unmounting it first on Linux? If my memory doesn't fail, that caused me a problem like yours.
I think my memory is bad  : http://www.pclinuxonline.com/modules...=4845&forum=18
Last edited by gbonvehi; 07-22-2005 at 07:23 AM.
|
|
|
|
07-22-2005, 07:41 AM
|
#3
|
|
Member
Registered: Dec 2004
Distribution: Slackware
Posts: 104
Original Poster
Rep:
|
Quote:
Originally posted by gbonvehi
Did you by any chance, rebooted (or turned off the Windows machine) without unmounting it first on Linux? If my memory doesn't fail, that caused me a problem like yours.
I think my memory is bad : http://www.pclinuxonline.com/modules...=4845&forum=18
|
well, the drive that was mounted is an external drive with a share on windows and I think I turned that drive off and unplugged it, so how would I go about fixing this?
|
|
|
|
07-22-2005, 07:46 AM
|
#4
|
|
Senior Member
Registered: Jun 2004
Location: Argentina (SR, LP)
Distribution: Slackware
Posts: 3,145
Rep:
|
I don't remember now if I had the same problem that you have, but try, before turning off and unplugging the drive, unmounting it from Linux (you'll have to try this next time you boot Linux).
If that wasn't the problem, try editing the Windows registry like that link suggests.
|
|
|
|
07-22-2005, 08:31 AM
|
#5
|
|
Member
Registered: Dec 2004
Distribution: Slackware
Posts: 104
Original Poster
Rep:
|
Quote:
Originally posted by gbonvehi
I don't remember now if I had the same problem that you have, but try, before turning off and unplugging the drive, unmounting it from Linux (you'll have to try this next time you boot Linux).
If that wasn't the problem, try editing the Windows registry like that link suggests.
|
I'll try it later when I get home, but seems kinda rediculous to have to edit the registry for this to work again.
|
|
|
|
07-22-2005, 08:35 AM
|
#6
|
|
Member
Registered: Oct 2003
Location: Sweden
Distribution: Slackware64-current
Posts: 676
Rep:
|
I'm not sure if I get the correct picture here, but since my possible solution is so simple I'll give it a shot anyway.
I got the same (or similar?) error while trying to mount a w2k share on my Slack laptop using samba. Simply rebooting the w2k box solved it.
Please forgive me if I'm off topic here, that means it tie to start the weekend!
Cheers, Leon.
Last edited by BroX; 07-22-2005 at 08:36 AM.
|
|
|
|
07-22-2005, 09:31 AM
|
#7
|
|
Senior Member
Registered: Jun 2003
Distribution: arch, slackware 10.2
Posts: 2,020
Rep:
|
do umount /mnt/backup -l to make sure your box knows it's unmounted. then try to mount it again. if that fails, i guess it couldn't hurt to reboot windows since it appears to be low on memory. i had to install w2k yesterday, and it rebooted itself at least a dozen times while installing and putting on other programs and updates. it seems to be what windows does best. 
|
|
|
|
07-22-2005, 11:05 AM
|
#8
|
|
Member
Registered: Dec 2004
Distribution: Slackware
Posts: 104
Original Poster
Rep:
|
I appreciate the effort to reply, but pointing out to restart my computer isn't much help. I both unmounted the share and rebooted both my windows and linux boxes before posting here, obviously that didn't work.
|
|
|
|
07-22-2005, 11:55 AM
|
#9
|
|
Senior Member
Registered: Jun 2003
Distribution: arch, slackware 10.2
Posts: 2,020
Rep:
|
Quote:
Originally posted by jcombs_31
I appreciate the effort to reply, but pointing out to restart my computer isn't much help. I both unmounted the share and rebooted both my windows and linux boxes before posting here, obviously that didn't work.
|
well, it's not really so obvious since you never mentioned either rebooting your linux machine (which you shouldn't have to do in most cases anyway) or that you properly unmounted it before turning off your share drive.
the other solutions i've seen from doing a quick google search all have to do with editing the windows registry to fix the ipstack, which someone else also mentioned and linked to. here's another one, with a big "Solved" in the title:
http://rokulabs.com/forums/viewtopic...102ebe5496deec
did you try that yet? 
|
|
|
|
07-22-2005, 12:04 PM
|
#10
|
|
Member
Registered: Dec 2004
Distribution: Slackware
Posts: 104
Original Poster
Rep:
|
Quote:
Originally posted by synaptical
well, it's not really so obvious since you never mentioned either rebooting your linux machine (which you shouldn't have to do in most cases anyway) or that you properly unmounted it before turning off your share drive.
the other solutions i've seen from doing a quick google search all have to do with editing the windows registry to fix the ipstack, which someone else also mentioned and linked to. here's another one, with a big "Solved" in the title:
http://rokulabs.com/forums/viewtopic...102ebe5496deec
did you try that yet?
|
You're right, I guess I should have mentioned it, I'll try the registry edit later and let you know if it works.
|
|
|
|
07-24-2005, 10:54 AM
|
#11
|
|
Member
Registered: Dec 2004
Distribution: Slackware
Posts: 104
Original Poster
Rep:
|
The registry edit fixed the problem.
|
|
|
|
01-04-2006, 06:48 PM
|
#12
|
|
LQ Newbie
Registered: Jan 2006
Posts: 1
Rep:
|
Addition to Regedit Fix
The regedit-fix worked to me as well, but the correct path is:
HKLM\System\CurrentControlSet\Services\lanmanserver\parameters
The key to be changed is named:
IRPStackSize
and should be changed from 11 (0x0b) to 15 (0x0f) or 20 (0x14)
THX and greetings.
|
|
|
|
| Thread Tools |
Search this Thread |
|
|
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -5. The time now is 10:37 AM.
|
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|