|
windows
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Can't Access Network Devicesupports both USB and Firewire connections. The drive is always assigned letter N. When the drive is connected to the PC using Firewire I can access it using either its local name (N:\) or it's network name (\\PM\N). {PM is the computer name.} Other PCs on my network are also able to access it. When the drive is connected to the PC using USB I can access it using its local name (N:\) but the network name (\\PM\N) does not work from this PC or the other PCs on my network. I get a message saying the drive is not accessable. Why does Firewire vs. USB have any effect on network connectivity? I'm running WinXP Pro SP2. Again, this drive is always N (Firewire or USB). Again, N:\ always works but \\PM\N works only with a Firewire connection. Why? Peter -- **Remove Xs to reply by e-mail** Hi
I do not know why you have to switch from USB to Firewire and vice versa. In any case try to assign a different drive letter to each one of the forms of connection. Jack (MS, MVP-Networking) Show quoteHide quote "Peter" <XXpmpmp***@comcast.net> wrote in message news:7uipl4d4evtngq0ags573sen38s86prfc6@4ax.com... >I have an external hard drive connected to one of my PCs. The drive > supports both USB and Firewire connections. The drive is always assigned > letter N. > > When the drive is connected to the PC using Firewire I can access it using > either its local name (N:\) or it's network name (\\PM\N). {PM is the > computer name.} Other PCs on my network are also able to access it. > > When the drive is connected to the PC using USB I can access it using its > local name (N:\) but the network name (\\PM\N) does not work from this PC > or the other PCs on my network. I get a message saying the drive is not > accessable. > > Why does Firewire vs. USB have any effect on network connectivity? > > I'm running WinXP Pro SP2. Again, this drive is always N (Firewire or > USB). Again, N:\ always works but \\PM\N works only with a Firewire > connection. Why? > > Peter > -- > > **Remove Xs to reply by e-mail** I don't HAVE to switch from USB to Firewire. I would prefer to use USB
all the time but that makes the drive non-networkable. For now I'm using Firewire all the time until I figure this out. I don't know how to give the drive a different drive letter for USB vs. Firewire. I connect the drive, the PC recognizes it and gives it N. How do I tell the PC to give it N if connected USB but give it another letter for Firewire? And even if I could figure out how to do that, that still doesn't answer the question of why is the drive non-networkable with a USB connection? Peter On Thu, 1 Jan 2009 13:21:02 -0500, "Jack \(MVP-Networking\)." <j***@discussiongroup.com> wrote: Show quoteHide quote >Hi **Remove Xs to reply by e-mail**>I do not know why you have to switch from USB to Firewire and vice versa. >In any case try to assign a different drive letter to each one of the forms >of connection. >Jack (MS, MVP-Networking) > >"Peter" <XXpmpmp***@comcast.net> wrote in message >news:7uipl4d4evtngq0ags573sen38s86prfc6@4ax.com... >>I have an external hard drive connected to one of my PCs. The drive >> supports both USB and Firewire connections. The drive is always assigned >> letter N. >> >> When the drive is connected to the PC using Firewire I can access it using >> either its local name (N:\) or it's network name (\\PM\N). {PM is the >> computer name.} Other PCs on my network are also able to access it. >> >> When the drive is connected to the PC using USB I can access it using its >> local name (N:\) but the network name (\\PM\N) does not work from this PC >> or the other PCs on my network. I get a message saying the drive is not >> accessable. >> >> Why does Firewire vs. USB have any effect on network connectivity? >> >> I'm running WinXP Pro SP2. Again, this drive is always N (Firewire or >> USB). Again, N:\ always works but \\PM\N works only with a Firewire >> connection. Why? >> >> Peter >> -- >> >> **Remove Xs to reply by e-mail** -- Hi
When you are connected with the USB look at the Control Panel/Computer management/Disk management it has the capacity to assign drive letter of your choice. http://www.ezlan.net/example/dsk_mang.jpg Jack (MS, MVP-Networking) Show quoteHide quote "Peter" <XXpmpmp***@comcast.net> wrote in message news:207ql4dcbmrp8i1rdrqej4031tub5nfngq@4ax.com... >I don't HAVE to switch from USB to Firewire. I would prefer to use USB > all the time but that makes the drive non-networkable. For now I'm using > Firewire all the time until I figure this out. > > I don't know how to give the drive a different drive letter for USB vs. > Firewire. I connect the drive, the PC recognizes it and gives it N. How > do I tell the PC to give it N if connected USB but give it another letter > for Firewire? > > And even if I could figure out how to do that, that still doesn't answer > the question of why is the drive non-networkable with a USB connection? > > Peter > > > On Thu, 1 Jan 2009 13:21:02 -0500, "Jack \(MVP-Networking\)." > <j***@discussiongroup.com> wrote: > >>Hi >>I do not know why you have to switch from USB to Firewire and vice versa. >>In any case try to assign a different drive letter to each one of the >>forms >>of connection. >>Jack (MS, MVP-Networking) >> >>"Peter" <XXpmpmp***@comcast.net> wrote in message >>news:7uipl4d4evtngq0ags573sen38s86prfc6@4ax.com... >>>I have an external hard drive connected to one of my PCs. The drive >>> supports both USB and Firewire connections. The drive is always >>> assigned >>> letter N. >>> >>> When the drive is connected to the PC using Firewire I can access it >>> using >>> either its local name (N:\) or it's network name (\\PM\N). {PM is the >>> computer name.} Other PCs on my network are also able to access it. >>> >>> When the drive is connected to the PC using USB I can access it using >>> its >>> local name (N:\) but the network name (\\PM\N) does not work from this >>> PC >>> or the other PCs on my network. I get a message saying the drive is not >>> accessable. >>> >>> Why does Firewire vs. USB have any effect on network connectivity? >>> >>> I'm running WinXP Pro SP2. Again, this drive is always N (Firewire or >>> USB). Again, N:\ always works but \\PM\N works only with a Firewire >>> connection. Why? >>> >>> Peter >>> -- >>> >>> **Remove Xs to reply by e-mail** > -- > > **Remove Xs to reply by e-mail** I've been to the Disk Management screen many times. I've assigned the
letter N to this drive when connected via USB. When I switch to the Firewire connection the drive still gets N. There does not seem to be a way to assign it one letter when connected USB and a different letter when connected Firewire. (If there is a way to do that please tell me how.) I have tried changing the assigned letter from N to something else but that accomplished nothing. Just to make sure we're focused on the actual problem ... the PC *does* recognize this drive with either type of connection. I can get to N:\ with USB or Firewire. What I can't do is get to \\PM\N when it's connected USB. {Thanks to all who have been trying to help with this. I really appreciate it because I am out of clues.} Peter On Thu, 1 Jan 2009 15:48:39 -0500, "Jack \(MVP-Networking\)." <j***@discussiongroup.com> wrote: Show quoteHide quote >Hi **Remove Xs to reply by e-mail**>When you are connected with the USB look at the Control Panel/Computer >management/Disk management it has the capacity to assign drive letter of >your choice. >http://www.ezlan.net/example/dsk_mang.jpg >Jack (MS, MVP-Networking) >"Peter" <XXpmpmp***@comcast.net> wrote in message >news:207ql4dcbmrp8i1rdrqej4031tub5nfngq@4ax.com... >>I don't HAVE to switch from USB to Firewire. I would prefer to use USB >> all the time but that makes the drive non-networkable. For now I'm using >> Firewire all the time until I figure this out. >> >> I don't know how to give the drive a different drive letter for USB vs. >> Firewire. I connect the drive, the PC recognizes it and gives it N. How >> do I tell the PC to give it N if connected USB but give it another letter >> for Firewire? >> >> And even if I could figure out how to do that, that still doesn't answer >> the question of why is the drive non-networkable with a USB connection? >> >> Peter >> >> >> On Thu, 1 Jan 2009 13:21:02 -0500, "Jack \(MVP-Networking\)." >> <j***@discussiongroup.com> wrote: >> >>>Hi >>>I do not know why you have to switch from USB to Firewire and vice versa. >>>In any case try to assign a different drive letter to each one of the >>>forms >>>of connection. >>>Jack (MS, MVP-Networking) >>> >>>"Peter" <XXpmpmp***@comcast.net> wrote in message >>>news:7uipl4d4evtngq0ags573sen38s86prfc6@4ax.com... >>>>I have an external hard drive connected to one of my PCs. The drive >>>> supports both USB and Firewire connections. The drive is always >>>> assigned >>>> letter N. >>>> >>>> When the drive is connected to the PC using Firewire I can access it >>>> using >>>> either its local name (N:\) or it's network name (\\PM\N). {PM is the >>>> computer name.} Other PCs on my network are also able to access it. >>>> >>>> When the drive is connected to the PC using USB I can access it using >>>> its >>>> local name (N:\) but the network name (\\PM\N) does not work from this >>>> PC >>>> or the other PCs on my network. I get a message saying the drive is not >>>> accessable. >>>> >>>> Why does Firewire vs. USB have any effect on network connectivity? >>>> >>>> I'm running WinXP Pro SP2. Again, this drive is always N (Firewire or >>>> USB). Again, N:\ always works but \\PM\N works only with a Firewire >>>> connection. Why? >>>> >>>> Peter >>>> -- >>>> >>>> **Remove Xs to reply by e-mail** >> -- >> >> **Remove Xs to reply by e-mail** --
Show quote
Hide quote
"Peter" <XXpmpmp***@comcast.net> wrote in message Isn't that a feature? Windows doesn't like to let you make what it news:207ql4dcbmrp8i1rdrqej4031tub5nfngq@4ax.com... > I don't HAVE to switch from USB to Firewire. I would prefer to use > USB > all the time but that makes the drive non-networkable. For now I'm > using > Firewire all the time until I figure this out. > > I don't know how to give the drive a different drive letter for USB > vs. > Firewire. I connect the drive, the PC recognizes it and gives it N. > How > do I tell the PC to give it N if connected USB but give it another > letter > for Firewire? > > And even if I could figure out how to do that, that still doesn't > answer > the question of why is the drive non-networkable with a USB > connection? > > Peter > > > On Thu, 1 Jan 2009 13:21:02 -0500, "Jack \(MVP-Networking\)." > <j***@discussiongroup.com> wrote: > >>Hi >>I do not know why you have to switch from USB to Firewire and vice >>versa. >>In any case try to assign a different drive letter to each one of the >>forms >>of connection. >>Jack (MS, MVP-Networking) >> >>"Peter" <XXpmpmp***@comcast.net> wrote in message >>news:7uipl4d4evtngq0ags573sen38s86prfc6@4ax.com... >>>I have an external hard drive connected to one of my PCs. The drive >>> supports both USB and Firewire connections. The drive is always >>> assigned >>> letter N. >>> >>> When the drive is connected to the PC using Firewire I can access it >>> using >>> either its local name (N:\) or it's network name (\\PM\N). {PM is >>> the >>> computer name.} Other PCs on my network are also able to access it. >>> >>> When the drive is connected to the PC using USB I can access it >>> using its >>> local name (N:\) but the network name (\\PM\N) does not work from >>> this PC >>> or the other PCs on my network. I get a message saying the drive is >>> not >>> accessable. >>> >>> Why does Firewire vs. USB have any effect on network connectivity? >>> >>> I'm running WinXP Pro SP2. Again, this drive is always N (Firewire >>> or >>> USB). Again, N:\ always works but \\PM\N works only with a Firewire >>> connection. Why? >>> >>> Peter >>> -- >>> >>> **Remove Xs to reply by e-mail** > -- > > **Remove Xs to reply by e-mail** identifies as removable media networkable? Why escapes me. But then why should a fire wire drive not be identified as removable? -- Wisdom and experience come with age, they say, but I wish I could remember the darn question
Show quote
Hide quote
On Thu, 1 Jan 2009 22:30:30 -0000, "GbH" <Geoff_Hannington@IEE.ORGasm> No, that's not at all a feature of Windows. Removable devices arewrote: > >"Peter" <XXpmpmp***@comcast.net> wrote in message >news:207ql4dcbmrp8i1rdrqej4031tub5nfngq@4ax.com... >> I don't HAVE to switch from USB to Firewire. I would prefer to use >> USB >> all the time but that makes the drive non-networkable. For now I'm >> using >> Firewire all the time until I figure this out. >> >> I don't know how to give the drive a different drive letter for USB >> vs. >> Firewire. I connect the drive, the PC recognizes it and gives it N. >> How >> do I tell the PC to give it N if connected USB but give it another >> letter >> for Firewire? >> >> And even if I could figure out how to do that, that still doesn't >> answer >> the question of why is the drive non-networkable with a USB >> connection? >> >> Peter >> >> >> On Thu, 1 Jan 2009 13:21:02 -0500, "Jack \(MVP-Networking\)." >> <j***@discussiongroup.com> wrote: >> >>>Hi >>>I do not know why you have to switch from USB to Firewire and vice >>>versa. >>>In any case try to assign a different drive letter to each one of the >>>forms >>>of connection. >>>Jack (MS, MVP-Networking) >>> >>>"Peter" <XXpmpmp***@comcast.net> wrote in message >>>news:7uipl4d4evtngq0ags573sen38s86prfc6@4ax.com... >>>>I have an external hard drive connected to one of my PCs. The drive >>>> supports both USB and Firewire connections. The drive is always >>>> assigned >>>> letter N. >>>> >>>> When the drive is connected to the PC using Firewire I can access it >>>> using >>>> either its local name (N:\) or it's network name (\\PM\N). {PM is >>>> the >>>> computer name.} Other PCs on my network are also able to access it. >>>> >>>> When the drive is connected to the PC using USB I can access it >>>> using its >>>> local name (N:\) but the network name (\\PM\N) does not work from >>>> this PC >>>> or the other PCs on my network. I get a message saying the drive is >>>> not >>>> accessable. >>>> >>>> Why does Firewire vs. USB have any effect on network connectivity? >>>> >>>> I'm running WinXP Pro SP2. Again, this drive is always N (Firewire >>>> or >>>> USB). Again, N:\ always works but \\PM\N works only with a Firewire >>>> connection. Why? >>>> >>>> Peter >>>> -- >>>> >>>> **Remove Xs to reply by e-mail** >> -- >> >> **Remove Xs to reply by e-mail** > > >Isn't that a feature? Windows doesn't like to let you make what it >identifies as removable media networkable? Why escapes me. >But then why should a fire wire drive not be identified as removable? networkable. -- **Remove Xs to reply by e-mail**
Show quote
Hide quote
"Peter" <XXpmpmp***@comcast.net> wrote in message OK, maybe that's Publisher, I think it barfs if one tries to use a news:vsoql45edkkvsn04n091glpc2sao3l0hns@4ax.com... > On Thu, 1 Jan 2009 22:30:30 -0000, "GbH" <Geoff_Hannington@IEE.ORGasm> > wrote: > >> >>"Peter" <XXpmpmp***@comcast.net> wrote in message >>news:207ql4dcbmrp8i1rdrqej4031tub5nfngq@4ax.com... >>> I don't HAVE to switch from USB to Firewire. I would prefer to use >>> USB >>> all the time but that makes the drive non-networkable. For now I'm >>> using >>> Firewire all the time until I figure this out. >>> >>> I don't know how to give the drive a different drive letter for USB >>> vs. >>> Firewire. I connect the drive, the PC recognizes it and gives it N. >>> How >>> do I tell the PC to give it N if connected USB but give it another >>> letter >>> for Firewire? >>> >>> And even if I could figure out how to do that, that still doesn't >>> answer >>> the question of why is the drive non-networkable with a USB >>> connection? >>> >>> Peter >>> >>> >>> On Thu, 1 Jan 2009 13:21:02 -0500, "Jack \(MVP-Networking\)." >>> <j***@discussiongroup.com> wrote: >>> >>>>Hi >>>>I do not know why you have to switch from USB to Firewire and vice >>>>versa. >>>>In any case try to assign a different drive letter to each one of >>>>the >>>>forms >>>>of connection. >>>>Jack (MS, MVP-Networking) >>>> >>>>"Peter" <XXpmpmp***@comcast.net> wrote in message >>>>news:7uipl4d4evtngq0ags573sen38s86prfc6@4ax.com... >>>>>I have an external hard drive connected to one of my PCs. The >>>>>drive >>>>> supports both USB and Firewire connections. The drive is always >>>>> assigned >>>>> letter N. >>>>> >>>>> When the drive is connected to the PC using Firewire I can access >>>>> it >>>>> using >>>>> either its local name (N:\) or it's network name (\\PM\N). {PM is >>>>> the >>>>> computer name.} Other PCs on my network are also able to access >>>>> it. >>>>> >>>>> When the drive is connected to the PC using USB I can access it >>>>> using its >>>>> local name (N:\) but the network name (\\PM\N) does not work from >>>>> this PC >>>>> or the other PCs on my network. I get a message saying the drive >>>>> is >>>>> not >>>>> accessable. >>>>> >>>>> Why does Firewire vs. USB have any effect on network connectivity? >>>>> >>>>> I'm running WinXP Pro SP2. Again, this drive is always N >>>>> (Firewire >>>>> or >>>>> USB). Again, N:\ always works but \\PM\N works only with a >>>>> Firewire >>>>> connection. Why? >>>>> >>>>> Peter >>>>> -- >>>>> >>>>> **Remove Xs to reply by e-mail** >>> -- >>> >>> **Remove Xs to reply by e-mail** >> >> >>Isn't that a feature? Windows doesn't like to let you make what it >>identifies as removable media networkable? Why escapes me. >>But then why should a fire wire drive not be identified as removable? > > No, that's not at all a feature of Windows. Removable devices are > networkable. > -- > > **Remove Xs to reply by e-mail** removable drive as its file location. Sorry about that too many newsgroups. -- Wisdom and experience come with age, they say, but I wish I could remember the darn question What if you plug it into the PC using USB, then right-click the drive in
Windows Explorer and select "Sharing" to create a share for it. Give it a share name "like "USB-N" and see if you can connect to \\PM\USB-N from your other machines. -- Show quoteHide quote-Ben- Ben M. Schorr, MVP Roland Schorr & Tower http://www.rolandschorr.com http://www.officeforlawyers.com Author - The Lawyer's Guide to Microsoft Outlook 2007: http://tinyurl.com/5m3f5q "Peter" <XXpmpmp***@comcast.net> wrote in message news:7uipl4d4evtngq0ags573sen38s86prfc6@4ax.com: > I have an external hard drive connected to one of my PCs. The drive > supports both USB and Firewire connections. The drive is always assigned > letter N. > > When the drive is connected to the PC using Firewire I can access it using > either its local name (N:\) or it's network name (\\PM\N). {PM is the > computer name.} Other PCs on my network are also able to access it. > > When the drive is connected to the PC using USB I can access it using its > local name (N:\) but the network name (\\PM\N) does not work from this PC > or the other PCs on my network. I get a message saying the drive is not > accessable. > > Why does Firewire vs. USB have any effect on network connectivity? > > I'm running WinXP Pro SP2. Again, this drive is always N (Firewire or > USB). Again, N:\ always works but \\PM\N works only with a Firewire > connection. Why? > > Peter > -- > > **Remove Xs to reply by e-mail** Good idea but it didn't work.
\\PM\N doesn't work \\PM\N-USB doesn't work Neither one is accessable from my other PCs and neither one is accessable from THIS PC. N:\ works but obviously only from this PC. On Thu, 1 Jan 2009 23:00:30 +0000, "Ben M. Schorr - MVP (OneNote)" <b***@bogusaddress.mvp> wrote: >What if you plug it into the PC using USB, then right-click the drive in **Remove Xs to reply by e-mail**>Windows Explorer and select "Sharing" to create a share for it. Give it >a share name "like "USB-N" and see if you can connect to \\PM\USB-N from >your other machines. -- Solution found:
I can't say that I understand what this solution is all about but it did fix the problem. Looks like it had nothing to do with permissions. You can read the details at: http://www.ghacks.net/2008/01/13/not-enough-server-storage-is-available-to-process-this-command/ I did not have that IRPStackSize Dword in the registry of any of my PCs. I added it with a value of 21 to the registry on the PC the external drive is connected to and the problem is gone. I can now access \\PM\N from any of my PCs. Thanks to everyone here who helped along the way! Peter On Thu, 01 Jan 2009 09:08:20 -0500, Peter <XXpmpmp***@comcast.net> wrote: Show quoteHide quote >I have an external hard drive connected to one of my PCs. The drive **Remove Xs to reply by e-mail**>supports both USB and Firewire connections. The drive is always assigned >letter N. > >When the drive is connected to the PC using Firewire I can access it using >either its local name (N:\) or it's network name (\\PM\N). {PM is the >computer name.} Other PCs on my network are also able to access it. > >When the drive is connected to the PC using USB I can access it using its >local name (N:\) but the network name (\\PM\N) does not work from this PC >or the other PCs on my network. I get a message saying the drive is not >accessable. > >Why does Firewire vs. USB have any effect on network connectivity? > >I'm running WinXP Pro SP2. Again, this drive is always N (Firewire or >USB). Again, N:\ always works but \\PM\N works only with a Firewire >connection. Why? > >Peter -- On Thu, 01 Jan 2009 23:55:37 -0500, Peter wrote:
>Solution found: Peter,> >I can't say that I understand what this solution is all about but it did >fix the problem. Looks like it had nothing to do with permissions. You >can read the details at: > >http://www.ghacks.net/2008/01/13/not-enough-server-storage-is-available-to-process-this-command/ > >I did not have that IRPStackSize Dword in the registry of any of my PCs. I >added it with a value of 21 to the registry on the PC the external drive >is connected to and the problem is gone. I can now access \\PM\N from any >of my PCs. thanks for reporting back! One question: did you actually get that error message (Not enough server storage ...)? Hans-Georg -- No mail, please. On Fri, 02 Jan 2009 12:54:03 +0100, Hans-Georg Michna
<hans-georgNoEmailPle***@michna.com> wrote: >Peter, Hans - I did get that message but only once which made me think it was an> >thanks for reporting back! > >One question: did you actually get that error message (Not >enough server storage ...)? > >Hans-Georg isolated fluke. I'm not sure why I got it only once. Peter -- **Remove Xs to reply by e-mail** On Fri, 02 Jan 2009 16:53:06 -0500, Peter wrote:
>On Fri, 02 Jan 2009 12:54:03 +0100, Hans-Georg Michna Peter,><hans-georgNoEmailPle***@michna.com> wrote: >>thanks for reporting back! >> >>One question: did you actually get that error message (Not >>enough server storage ...)? >Hans - I did get that message but only once which made me think it was an >isolated fluke. I'm not sure why I got it only once. thanks for reporting back! I guess without that message the cause might have been difficult to identify. Not to mention that the content of the error message is meaningless. Hans-Georg -- No mail, please. 
Other interesting topics
Netgear Connectivity Problem
IP conflict due to old fix IP Help for the clueless, please. how to configure an alfa wireless-g ethernet router/bridge? unable to connect using WPA ID 2011 locked up internet connection Unauthorized to access computers I.E. 7.0 will not open a certain web site I.E. welcome page |
|||||||||||||||||||||||
