Jump to content

Network Share Unaccessible


Recommended Posts

Guest T. Duprex
Posted

I have a network of three computers, two running windowsxp and one running

windows98. Networking between all three is okay except for one of the XPs.

This XP,\\ACER_PENT, can see every other computer's shares and read them.

However when I attempt to access the shares of the \\ACER_PENT from either

of the other two computers I get a message that \\ACER-PENT <filename> is

not accessible. The shares show up on My Network Places, but when I attempt

to access I get the not accessible message.

 

What could the problem be on \\ACER_PENT?

 

TIA

  • Replies 13
  • Created
  • Last Reply

Popular Days

Guest John John (MVP)
Posted

Re: Network Share Unaccessible

 

Try here: http://www.chicagotech.net/accesserrors.htm

 

John

 

T. Duprex wrote:

> I have a network of three computers, two running windowsxp and one running

> windows98. Networking between all three is okay except for one of the XPs.

> This XP,\\ACER_PENT, can see every other computer's shares and read them.

> However when I attempt to access the shares of the \\ACER_PENT from either

> of the other two computers I get a message that \\ACER-PENT <filename> is

> not accessible. The shares show up on My Network Places, but when I attempt

> to access I get the not accessible message.

>

> What could the problem be on \\ACER_PENT?

>

> TIA

Guest Malke
Posted

Re: Network Share Unaccessible

 

"T. Duprex" <tduprexATlandmark.net> wrote:

> I have a network of three computers, two running windowsxp and one running

> windows98. Networking between all three is okay except for one of the XPs.

> This XP,\\ACER_PENT, can see every other computer's shares and read them.

> However when I attempt to access the shares of the \\ACER_PENT from either

> of the other two computers I get a message that \\ACER-PENT <filename> is

> not accessible. The shares show up on My Network Places, but when I

> attempt to access I get the not accessible message.

>

> What could the problem be on \\ACER_PENT?

 

Probably either a firewall or username issue. See below.

 

Problems sharing files between computers on a network are generally caused

by 1) a misconfigured firewall or overlooked firewall (including a stateful

firewall in a VPN); or 2) inadvertently running two firewalls such as the

built-in Windows Firewall and a third-party firewall; and/or 3) not having

identical user accounts and passwords on all Workgroup machines; 4) trying

to create shares where the operating system does not permit it.

 

A. Configure firewalls on all machines to allow the Local Area Network (LAN)

traffic as trusted. With Windows Firewall, this means allowing File/Printer

Sharing on the Exceptions tab. Normally running the Network Setup Wizard on

XP will take care of this for those machines.The only "gotcha" is that this

will turn on the XPSP2 Windows Firewall. If you aren't running a

third-party firewall or have an antivirus with "Internet Worm

Protection" (like Norton 2006/07) which acts as a firewall, then you're

fine. With third-party firewalls, I usually configure the LAN allowance

with an IP range. Ex. would be 192.168.1.0-192.168.1.254. Obviously you

would substitute your correct subnet. Do not run more than one firewall. DO

NOT TURN OFF FIREWALLS; CONFIGURE THEM CORRECTLY.

 

B. For ease of organization, put all computers in the same Workgroup. This

is done from the System applet in Control Panel, Computer Name tab.

 

C. Create matching user accounts and passwords on all machines. You do not

need to be logged into the same account on all machines and the passwords

assigned to each user account can be different; the accounts/passwords just

need to exist and match on all machines. DO NOT NEGLECT TO CREATE

PASSWORDS, EVEN IF ONLY SIMPLE ONES. If you wish a machine to boot directly

to the Desktop (into one particular user's account) for convenience, you

can do this. The instructions at this link work for both XP and Vista:

 

Configure Windows to Automatically Login (MVP Ramesh) -

http://windowsxp.mvps.org/Autologon.htm

 

D. If one or more of the computers is XP Pro or Media Center, turn off

Simple File Sharing (Folder Options>View tab).

 

E. Create shares as desired. XP Home does not permit sharing of users' home

directories or Program Files, but you can share folders inside those

directories. A better choice is to simply use the Shared Documents folder.

 

Malke

--

MS-MVP

Elephant Boy Computers - Don't Panic!

FAQ - http://www.elephantboycomputers.com/#FAQ

Guest T. Duprex
Posted

Re: Network Share Unaccessible

 

"T. Duprex" <tduprexATlandmark.net> wrote in

news:Xns9AF25F72C5429pinger@207.46.248.16:

 

I have resolved the problem.

 

Did a search in Goggle Groups and eventually found that the problem can be

caused by IRPSTackSize being non-existent or too small. In my case it

didn't exist. I initially tried a decimal value of 15, which didn't work. I

then increased it to 30 and had success.

 

HKLM\System\CurrentControlSet\Services\lanmanserver\parameters\IRPStackSize

 

As a final note it was the second half of the error message that said that

the server may not have enough capacity that really was the clue.

Search Goggle groups for IRPStackSize and there are a bunch of messages to

give you more detailed information.

Guest John John (MVP)
Posted

Re: Network Share Unaccessible

 

Now is a fine time to give us all of the error message. If you had

mentioned the "Not enough server storage is available..." part of the

message you would have gotten a fix in no time flat from the respondents

here.

 

John

 

T. Duprex wrote:

> "T. Duprex" <tduprexATlandmark.net> wrote in

> news:Xns9AF25F72C5429pinger@207.46.248.16:

>

> I have resolved the problem.

>

> Did a search in Goggle Groups and eventually found that the problem can be

> caused by IRPSTackSize being non-existent or too small. In my case it

> didn't exist. I initially tried a decimal value of 15, which didn't work. I

> then increased it to 30 and had success.

>

> HKLM\System\CurrentControlSet\Services\lanmanserver\parameters\IRPStackSize

>

> As a final note it was the second half of the error message that said that

> the server may not have enough capacity that really was the clue.

> Search Goggle groups for IRPStackSize and there are a bunch of messages to

> give you more detailed information.

>

>

>

Guest Malke
Posted

Re: Network Share Unaccessible

 

"T. Duprex" <tduprexATlandmark.net> wrote:

> "T. Duprex" <tduprexATlandmark.net> wrote in

> news:Xns9AF25F72C5429pinger@207.46.248.16:

>

> I have resolved the problem.

>

> Did a search in Goggle Groups and eventually found that the problem can be

> caused by IRPSTackSize being non-existent or too small. In my case it

> didn't exist. I initially tried a decimal value of 15, which didn't work.

> I then increased it to 30 and had success.

>

>

HKLM\System\CurrentControlSet\Services\lanmanserver\parameters\IRPStackSize

>

> As a final note it was the second half of the error message that said that

> the server may not have enough capacity that really was the clue.

> Search Goggle groups for IRPStackSize and there are a bunch of messages to

> give you more detailed information.

 

Yes Sunshine, but you DIDN'T EVER TELL US THAT PART OF THE ERROR MESSAGE.

The answer to which WE ALL KNEW and would have given you if you had

INCLUDED THE EXACT TEXT OF THE ERROR MESSAGE IN YOUR FIRST POST.

 

Next time before you post:

 

How to Post:

http://www.elephantboycomputers.com/page2.html#Usenet

http://support.microsoft.com/default.aspx/kb/555375 - How to Ask a Question

http://users.tpg.com.au/bzyhjr/liszt.htm - How Not to Get Technical Help on

Usenet

http://www.catb.org/~esr/faqs/smart-questions.html

 

Malke

--

MS-MVP

Elephant Boy Computers - Don't Panic!

FAQ - http://www.elephantboycomputers.com/#FAQ

Guest T. Duprex
Posted

Re: Network Share Unaccessible

 

Pardon me, MVPs. I didn't realize you guys were that good.

Guest Gary S. Terhune
Posted

Re: Network Share Unaccessible

 

LOL! What *do* you expect from people who spend sometimes hours per day,

nearly every day, for years, researching solutions to Windows problems.

Incompetence?

 

Generalized questions get generalized answers, usually very long ones,

usually loaded with lists of possibilities and their associated suggested

resolutions. Specific errors, when you provide them in their entirety and

verbatim, frequently lead to immediate, precise answers. Guess which one

takes a LOT more work.

 

--

Gary S. Terhune

MS-MVP Shell/User

http://grystmill.com

 

"T. Duprex" <tduprexATlandmark.net> wrote in message

news:Xns9AF2F01DEFEB3pinger@207.46.248.16...

> Pardon me, MVPs. I didn't realize you guys were that good.

>

Guest T. Duprex
Posted

Re: Network Share Unaccessible

 

Gary:

 

Understood. No excuse for my not so detailed request. I guess being called

"Sunshine" annooyed me a litte.

 

Over the years you guys have helped me a lot. Thanks for being there.

>

Guest Gary S. Terhune
Posted

Re: Network Share Unaccessible

 

It was intended to, I'm sure, <g>.

 

--

Gary S. Terhune

MS-MVP Shell/User

http://grystmill.com

 

"T. Duprex" <tduprexATlandmark.net> wrote in message

news:Xns9AF33CAB49EApinger@207.46.248.16...

> Gary:

>

> Understood. No excuse for my not so detailed request. I guess being called

> "Sunshine" annooyed me a litte.

>

> Over the years you guys have helped me a lot. Thanks for being there.

>>

>

Guest T. Duprex
Posted

Re: Network Share Unaccessible

 

"Gary S. Terhune" <none> wrote in news:uG0#RhG#IHA.1228

@TK2MSFTNGP02.phx.gbl:

> It was intended to, I'm sure, <g>.

 

Would you call it a flame message?

>

Guest Gary S. Terhune
Posted

Re: Network Share Unaccessible

 

You mean the "Sunshine" part? Not at all. That was just a little dig brought

on by major frustration. I'm sure that if Malke had intended to flame you,

you'd be off somewhere, crying uncontrollably--still. But I don't recall

Malke being that kind of person.

 

If you want an example of flame posts, just search Google Groups for posts

by me. Just in the last 24 hours, I've posted scads of them in the

Vista.General group. Of course, it's not fair, what I do, since my targets

are all ignorant non-Linux using trolls. (They claim to use Linux, but they

simply aren't smart enough. Their real goal is to sink Linux forever with

bad press.) I suppose it's totally not PC to make fun of the ignorant.

 

--

Gary S. Terhune

MS-MVP Shell/User

http://grystmill.com

 

"T. Duprex" <tduprexATlandmark.net> wrote in message

news:Xns9AF36C081AB29pinger@207.46.248.16...

> "Gary S. Terhune" <none> wrote in news:uG0#RhG#IHA.1228

> @TK2MSFTNGP02.phx.gbl:

>

>> It was intended to, I'm sure, <g>.

>

> Would you call it a flame message?

>>

>

Guest T. Duprex
Posted

Re: Network Share Unaccessible

 

"John John (MVP)" <audetweld@nbnet.nb.ca> wrote in

news:OrGZ8vA#IHA.2348@TK2MSFTNGP06.phx.gbl:

 

Okay: My bad.

 

However John John, I have a question.

 

What might be the cause of IRPStackSize being deleted in the first place?

I know that I read shares from this XP machine last December with no

problem. Nothing major that comes to mind that has happened. The only

event was that a day or so before I loaded SR3 and that went off without

incident. I noticed that Microsoft subsequently loaded several fixes,

presumably for security issues.

 

TIA

 

 

> Now is a fine time to give us all of the error message. If you had

> mentioned the "Not enough server storage is available..." part of the

> message you would have gotten a fix in no time flat from the

> respondents here.

>

> John

>

> T. Duprex wrote:

>> "T. Duprex" <tduprexATlandmark.net> wrote in

>> news:Xns9AF25F72C5429pinger@207.46.248.16:

>>

>> I have resolved the problem.

>>

>> Did a search in Goggle Groups and eventually found that the problem

>> can be caused by IRPSTackSize being non-existent or too small. In my

>> case it didn't exist. I initially tried a decimal value of 15, which

>> didn't work. I then increased it to 30 and had success.

>>

>> HKLM\System\CurrentControlSet\Services\lanmanserver\parameters\IRPStac

>> kSize

>>

>> As a final note it was the second half of the error message that said

>> that the server may not have enough capacity that really was the

>> clue. Search Goggle groups for IRPStackSize and there are a bunch of

>> messages to give you more detailed information.

>>

>>

>>

Guest John John (MVP)
Posted

Re: Network Share Unaccessible

 

I don't know, look in your Event Log to see if anything is recorded

around the time the problem started. I know that Symantec AV software

can cause problems with this but I don't know an exact cause. See if

the information here can shed some light on the problem:

 

Not enough server storage

http://winhlp.com/node/40

 

http://search.yahoo.com/search;_ylt=A0geu9sBRJtIlqIAYeWl87UF?p=IRPStackSize+site%3Aeventid.net&ei=UTF-8&iscqry=&fr=sfp

 

John

 

T. Duprex wrote:

> "John John (MVP)" <audetweld@nbnet.nb.ca> wrote in

> news:OrGZ8vA#IHA.2348@TK2MSFTNGP06.phx.gbl:

>

> Okay: My bad.

>

> However John John, I have a question.

>

> What might be the cause of IRPStackSize being deleted in the first place?

> I know that I read shares from this XP machine last December with no

> problem. Nothing major that comes to mind that has happened. The only

> event was that a day or so before I loaded SR3 and that went off without

> incident. I noticed that Microsoft subsequently loaded several fixes,

> presumably for security issues.

>

> TIA

>

>

>

>

>>Now is a fine time to give us all of the error message. If you had

>>mentioned the "Not enough server storage is available..." part of the

>>message you would have gotten a fix in no time flat from the

>>respondents here.

>>

>>John

>>

>>T. Duprex wrote:

>>

>>>"T. Duprex" <tduprexATlandmark.net> wrote in

>>>news:Xns9AF25F72C5429pinger@207.46.248.16:

>>>

>>>I have resolved the problem.

>>>

>>>Did a search in Goggle Groups and eventually found that the problem

>>>can be caused by IRPSTackSize being non-existent or too small. In my

>>>case it didn't exist. I initially tried a decimal value of 15, which

>>>didn't work. I then increased it to 30 and had success.

>>>

>>>HKLM\System\CurrentControlSet\Services\lanmanserver\parameters\IRPStac

>>>kSize

>>>

>>>As a final note it was the second half of the error message that said

>>>that the server may not have enough capacity that really was the

>>>clue. Search Goggle groups for IRPStackSize and there are a bunch of

>>>messages to give you more detailed information.

>>>

>>>

>>>

>

>


×
×
  • Create New...