Re: Connecting a Legacy (very!) Lanman box

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



TimeTraveller

Thank you very much!!! That was It! AFter disabling SMB, the Drive is
visible, and the application is working on the SBS files!!!

Much Much appreciation, if you are ever in Vancouver, drop by for a beer!!


--
Mike Wolfe


"TimeTraveller" wrote:

> Have you disabled SMB Signing on the SBS Server?
>
> DOS/WIN95 etc do not support SMB Signing which is turned on by default in
> SBS2003
>
> TT
>
> "Mike Wolfe" <MikeWolfe@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:C5888440-2254-4DB3-987B-ED2104E5837B@xxxxxxxxxxxxxxxx
> > Hi
> > We have SBS2003 premium and 17 stations mix of XP Pro and Win2k Pro.
> > Server
> > and Ws's all at current SP and patch level. I recently upgraded the site
> > from a Netware based LAN to SBS2003.
> >
> > My last problem is with the Voice Mail system - it was inherited when we
> > moved to this office 4 months ago, and runs on a very old (1993 vintage)
> > box
> > running DOS.
> >
> > We managed to find a LANMAN package and (miraculously) a compatible driver
> > for the NIC, and after many attempts starts are dangerously close to
> > getting
> > this box running on the SBS net - it needs to run there since it dumps the
> > VM
> > files on the server, and when staff manage their voice mail boxes it
> > manipulates the server files. We do need it on the net since there is a
> > queue watch / manage process that interacts with the (telephone support)
> > users on their desktop.
> >
> > SO, at this time I have the box called VOICEMAIL boot up, and successfully
> > load the LANMAN client, successfully retrieve an IP address lease from the
> > SBS2003 DHCP server, successfully do a net use (with a password - LANMAN
> > syntax) to map a drive letter to a (less than 8 character name) share on
> > the
> > SBS2003 server, then I can make that drive current, but get an access
> > denied
> > error when we do a dir or basically anything else. The Shares list page
> > shows an active connection when the drive is mapped via the net use.
> >
> > I have made the user VOICEMAIL the owner of the share, with full control
> > of
> > share permissions, added the user to Domain Admins, given the user Full
> > control under the security permissions, and the user shows effective
> > permissions as full control and all else.
> >
> > The security event log shows the sucessful login, and I see no other
> > events
> > related to the failure to do a dir.
> >
> > Any Ideas??????
> >
> > --
> > Mike Wolfe
>
>
>
.



Relevant Pages

  • Re: Baffelling RWW problem
    ... "special permissions" and all is good in RWW land. ... Check the configuration on SBS server and client computer as following: ... your ISP DNS server IP should be ...
    (microsoft.public.windows.server.sbs)
  • Re: login/logoff Report
    ... Share/NTS Permissions ... Make sure you're logged onto the SBS server as a domain admin. ... In the section marked "Permissions for Domain Users", ...
    (microsoft.public.windows.server.sbs)
  • Re: Fax service failing to send faxes out? Receives ok.
    ... The default fax permission for SBS server is listed as following, ... SBS Fax Operators: Allow - Fax, ... Special Permissions - Allow - Submit Low Priority Fax, ... Click Services tab and select Hide All Microsoft Services and Disable ...
    (microsoft.public.windows.server.sbs)
  • Re: login/logoff Report
    ... truncated" error message when you try to modify or to view GPOs in Windows ... Server 2003, Windows XP Professional, or Windows 2000 ... Make sure the "logging folder" share has Share Permissions: ... Put the newly created logon.cmd and logoff.cmd on your SBS desktop ...
    (microsoft.public.windows.server.sbs)
  • RE: Cannot access companyweb
    ... to migrate from SBS 2003 to SBS2003, in this period, you can't achieve this ... 825763 How to configure Internet access in Windows Small Business Server ... By this method, you need to manually restore Exchange data, SharePoint ... Another way is to create a local profile, ...
    (microsoft.public.windows.server.sbs)