joako
Premium
join:2000-09-07
/dev/null
 ·AT&T U-Verse
| reply to atomicrabbit
Re: CIFS not connecting
said by atomicrabbit  :what should I allow in the firewall? Disable it, not needed behind a router.
--
PRescott7-2097 |
|
atomicrabbit
join:2009-06-04 | jaoko, i disabled the firewall, made no difference. Still can't connect.
I've verified that I have file sharing working properly. I've tried connecting to my computer from another
@pandora, I'll look into that. Thanks for the link. |
|
B
Premium,MVM
join:2000-10-28
| I assume you read their FAQ?
I just pulled it up Googling.... good luck.
Why isn't CIFS working for me?
* Use an IP address. ex: \\192.168.1.5\share
* Use a regular account that requires username/password instead of a guest account.
* Make sure the account has read/write permission.
* Make sure NAT Loopback is enabled in Advanced/Firewall.
You also might want to make sure the share name is simple and short.
-- B
--
In a realm outside causality and function |
|
atomicrabbit
join:2009-06-04
| * Use an IP address. ex: \\192.168.1.5\share YES
* Use a regular account that requires username/password instead of a guest account. YES
* Make sure the account has read/write permission. YES
* Make sure NAT Loopback is enabled in Advanced/Firewall. YES, it's set to Forward Only, but I tried setting it to All, and it still didn't work |
|
atomicrabbit
join:2009-06-04 | reply to B
suggestions please :| |
|
wierdo
join:2001-02-16
Tulsa, OK
 ·Future Nine Corpor..
·Teliax VOIP
| said by atomicrabbit :suggestions please :| Check your computer's logs and see if it's even attempting to connect.
--
It's wierdo, not weirdo. Yes, I know that's not the 'proper' spelling of the similar english language word.  |
|
atomicrabbit
join:2009-06-04 | sorry for the late reply... nothing in the logs on my computer. |
|
wierdo
join:2001-02-16
Tulsa, OK
·Future Nine Corpor..
·Teliax VOIP
| 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. |
|
atomicrabbit
join:2009-06-04
| 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:
|
|
atomicrabbit
join:2009-06-04
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? |
|
pandora
Premium
join:2001-06-01
Outland
·ooma
·Future Nine Corpor..
 ·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." |
|
atomicrabbit
join:2009-06-04
| @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! |
|
