 wierdo join:2001-02-16 Tulsa, OK Reviews:
·Cox HSI
·T-Mobile US
| reply to atomicrabbit
Re: CIFS not connecting Use wireshark or tcpdump to verify you're not seeing any CIFS traffic from the router. If still no, the only thing I can think of is a routing issue, like if your local network is 192.168.1.* and the WAN port has gotten an address in the same block.
I know at one point I had tomato working with CIFS. -- It's wierdo, not weirdo. Yes, I know that's not the 'proper' spelling of the similar english language word.  |
|
|
|
 | I cannot seem to get WireShark to work on windows 7. I downloaded Wireshark portable and I keep getting this error:
Dumpcap has stopped working
and then when WireShark starts, it says: The NPF driver isn't running. You may have trouble capturing or listing interfaces.
The Event Viewer details say this:
Faulting application name: dumpcap.exe, version: 1.2.0.28753, time stamp: 0x4a3726f3
Faulting module name: libglib-2.0-0.dll, version: 2.20.3.0, time stamp: 0x4a23951f
Exception code: 0x40000015
Fault offset: 0x00048416
Faulting process id: 0x1750
Faulting application start time: 0x01c9fb80fa56918c
Faulting application path: C:\PortableApps\WiresharkPortable\App\Wireshark\dumpcap.exe
Faulting module path: C:\PortableApps\WiresharkPortable\App\Wireshark\libglib-2.0-0.dll
Report Id: 3957c161-6774-11de-8f9b-0013d3cc64bd
|
|
 1 edit | Nevermind, I figured it out, it has something to do with the beta version of WinPcap (v4.1 beta5); it doesn't seem to work with Windows 7. Although the previous stable version (v4.0.2) seems to work fine with Windows 7... go figure.
@wierdo, what would I be looking for in WireShark? would it specifically say "CIFS" somewhere? |
|
 pandoraPremium join:2001-06-01 Outland kudos:1 Reviews:
·ooma
·Google Voice
·Future Nine Corp..
·Comcast
| You've gone from a Linksys alternative firmware question to a Microsoft beta operating system question. It is helpful to run a production OS when trying to get help for features. -- "People demand freedom of speech as a compensation for the freedom of thought which they seldom use." |
|
 | @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 |
|
 | 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. |
|
 BPremium,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 |
|
 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 Reviews:
·Cox HSI
·T-Mobile US
| 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.  |
|
 BPremium,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 |
|
 | 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! |
|