Ok, not so final update. . .
Worked once. Hadn't worked since. Hitting windows based shares still goes.
. . .
Well, hold on a minute:
I installed Resco Explorer. No help there. Windows shares went away. Uninstalled Resco. Windows shares still gone, but NAS (FreeNAS) now accessible via Total Commander CE.
This is a power users OS right?
Ok, the NAS share is now inaccessible.
[Update]
After fiddling with registries and PPC software and the like I read a message that said: "Stop looking at your phone and look at your SMB server" After looking at my server there was no log activity when trying to connect with my phone. The only thing I could think of was to check the DNS domain of my NAS matched the DNS domain of my router (that from the router is what's written in the phone's DNSDomain reg key)
I changed the DNS domain on the NAS.
As of 11:30 CST, I haven't lost my access to either the Windows share of the FreeBSD share since-- despite my efforts to break it (turning the phone off and on, turning EVDO data on and off, turning wireless off and on). I think that my NAS was acting as a browser master (even though I told it not to). When SMB/CIFS goes down all share access goes down until SMB comes back up (which is a few seconds).
In summary:
- I think there are some issues with the 6.5.5 branch concerning LAN / Wireless subsystem.
- 6.5.3 will work for 99.99999% of all users with no issues whatsoever.
- I recommend avoiding Rescoe-- as a means for "fixing" this and similar issues. It does weird things to your configuration and, as stated before, this isn't a PPC problem.
- Depending on your NAS configuration you could get by setting:
Code:
HKEY_LOCAL_MACHINE\Comm\SecurityProviders\NTLM\LmCompatibilityLevelClient = 1
If not, check the other three registry setting I pointed out earlier. Also, for good measure, put the ntlmssd.dll at the beginning of both Providers values.
- You may have to enable your SMB server to accept null passwords.
- I'm not sure the Browser Master setting is really relevant, but all the SMB confs I've looked at that are trying to resolve NTLM issues have it turned off.
- Lastly, if you use high falutin networking gear like I do (read: stuff I downloaded off the web and slapped on old computer parts), check that it does not have a DNS domain setting (nothing to do with the NetBIOS name or workgroup).
Ok. Next up is SSH / SCP / SFTP. Who's with me? But first, we eat.