mikesgroovin
HONK if you route packets
- Messages
- 4,718
- Location
- MD
the entry was restrictanonymous not restoreanonymous and not restrictanonymoussam. The restrictanonymous was to be set to 0.
Please read carefully, I'd hate for you to "delete" or do something else unintentionally.
The short of my concern was that sometimes when trying to negotiate a share, the resource user and pass aren't read. They are always "sent" by the client or requesting PC, but sometimes these bits aren't read, this is where the restrictanonymous comes in and if it set to 1, you will get that "You may not have permission to use this network resource" error, when, in fact, you do have permission to use this network resource.
You may want to restate EXACTLY what your problem is now because, after your last 2 posts and restoring from an earlier image, I'm not sure where your problem lies anymore.
Please read carefully, I'd hate for you to "delete" or do something else unintentionally.
The short of my concern was that sometimes when trying to negotiate a share, the resource user and pass aren't read. They are always "sent" by the client or requesting PC, but sometimes these bits aren't read, this is where the restrictanonymous comes in and if it set to 1, you will get that "You may not have permission to use this network resource" error, when, in fact, you do have permission to use this network resource.
You may want to restate EXACTLY what your problem is now because, after your last 2 posts and restoring from an earlier image, I'm not sure where your problem lies anymore.