atomicrabbit
join:2009-06-04
| reply to pandora
Re: CIFS not connecting
@pandora: I figured out why WIreShark wasn't working on my OS, if you read my last post, and I got it working now.
ok back to my problem. I figured out to filter "smb" requests and I think I found what the problem, is, I just don't know how to fix it.
It's giving me ERROR: STATUS_BAD_NETWORK_NAME |
|
atomicrabbit
join:2009-06-04
| ok i figured it out. Apparently if I share the entire drive, the sub-directories are not shared to the router ??? I say "to the router" because if I try to access the shared drive from another computer, I am able to access the entire drive and all it's contents.
But for some reason I had to set the shared settings of the "tomato_bandwidth" directory separately from the i: drives sharing properties.
So now instead of giving the path \\192.168.1.XXX\i\tomato_bandwidth ... I set teh shared propeties of the tomato_bandwidth directory separately and set the shared path to \\192.168.1.XXX\tomato_bandwidth
Kinda stupid.
It works now. The shared directory gets mounted. |
|
B
Premium,MVM
join:2000-10-28
| Great detective work. I agree; since they prompt for "UNC" path they really should have accepted your original version. Did you try it both with and without the terminating slash?
-- B
--
In a realm outside causality and function |
|
atomicrabbit
join:2009-06-04
1 edit | well if the second path worked without the terminating slash, then the first path should have as well.
And actually, if I add the terminating slash, after saving the settings, tomato automatically removes it |
|
wierdo
join:2001-02-16
Tulsa, OK
 ·Future Nine Corpor..
·Teliax VOIP
| reply to atomicrabbit
said by atomicrabbit  :Kinda stupid. It works now. The shared directory gets mounted. Hah, that'll do it. Since tomato passes the input directly to the CIFS/SMB kernel module it can't handle subdirectories. To handle them it would have to pass only the initial //192.168.1.xxx/i to the module, then tell the logger to use /cifs1/tomato_bandwidth as the directory.
AFAIK, it's hardcoded to always use /cifs1, so you're stuck with only using the root of a share.
--
It's wierdo, not weirdo. Yes, I know that's not the 'proper' spelling of the similar english language word.  |
|
B
Premium,MVM
join:2000-10-28 | They should really clarify that screen prompt, then. Maybe "UNC path to share root".
-- B
--
In a realm outside causality and function |
|
atomicrabbit
join:2009-06-04
| said by wierdo :To handle them it would have to pass only the initial //192.168.1.xxx/i to the module, then tell the logger to use /cifs1/tomato_bandwidth as the directory. this unfortunately makes sense. Thanks for clarifying
said by B :They should really clarify that screen prompt, then. Maybe "UNC path to share root". Definitely agree! |
|
