|
|
Back to UserFriendly Strip Comments Index
|
Networking help needed | by bordertech | 2003-11-03 12:50:32 |
| It's a legacy problem related ... |
by Slamlander |
2003-11-03 14:55:26 |
to the drive mapping. The best place for explainations are the Samba dox. Mapping Network drives uses an older dedprecated version of the SMB protocols. That older protocol would time out the connection and drop the virtual circuit to the mapped drive. When this happens and you then try to access the drive you have to go through an entire login sequence all over again. Worse, your system doesn't know the vc has been dropped (either side) and goes through a horrendous series of waits before renegotiating the connection.
Solution: avoid drive mapping like the plague. Reference all network shares directly, by their UNC name. I know, there are still many brain-dead applications out there that require drive mapping.
Once a drive has been mapped and you then drop the map, your minimum wait, before the server knows the map has been dropped, is the next WINS browser election. Even then, that soemtimes doesn't do it. rebooting both the client and the server is sometimes required (or wait 24 hours).
Like I said, it's a legacy issue from old Lan Manager 1.0 daze and they have to keep it like that for backwards compatibility. Samba partially gets around this problem with keep-alive packets. However, that's only a partial solution. I know a fool-proof solution that I encoded for a Linux box however, pretty it ain't. In fact, had I a dog that ugly, I'd make it walk backwards. |
|
[ Reply ] |
|
|
[Todays Cartoon Discussion]
[News Index]
|
|
