[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[cobalt-users] NASRaQ SMB/Samba Problems?
- Subject: [cobalt-users] NASRaQ SMB/Samba Problems?
- From: "Jeremiah Sypult" <jers@xxxxxxxxxxxxxxx>
- Date: Mon Feb 7 08:06:57 2000
- Organization: StudioNorth
I've talked to someone at Cobalt about a problem with Samba on the NASRaQ's.
They say a patch is in QA/QC--which they don't know when it will be
available.
The problem we are experiencing seems mostly related to SMB
username/password authentication.
Under cetrain circumstances, when some of our developers log in to their
WinNT Workstations, they will have a mapped drive letter to a share on the
NASRaQ. All of their login names / passwords are the same Login with no
password, which is authenticated on a WinNT Server Primary Domain
Controller.
When logging in, they will be prompted with a username/password dialog box
for the share--which /should/ authenticate--but it doesnt... Any set of
credentials specified, be it their normal username/password, or even a few
Administrator accounts on the network, none of them will authenticate...
It seems after rebooting the workstation, it is able to log in.
Another circumstance is our very unique web-development environment.
We have the same PDC serving up webpages via IIS with Cold Fusion and ASP
programming. The web server's 'home directory' is pointing to a share on
the NASRaQ where we store all of our development programming. Randomly,
when you access the webserver, it will stop serving up webpages. I've tried
stopping IIS, stopping services, etc etc... It will error out with some
type of error saying that 'the service failed to respond to the stop
request' or something along those lines...
Then we try and shutdown the sever... What happens there, is that it will
freeze and wait on a dialog box before shutting down completely. That
dialog box says 'Please wait will all network connections are closed'.
We then have to hard-boot the server by pressing the reset button.
This is somewhat frustrating--and knowing that there isn't an immediate
patch available, I was wondering if anyone has experienced similar problems,
and knows if there is any type of workaround while I wait for this patch to
be released? It kinda hinders some development work having to restart any
time between fourty minutes or a couple of hours.
Any help would be greatly appreciated.
-Jer
========================
Jeremiah Sypult
Systems Administration
StudioNorth
jers@xxxxxxxxxxxxxxx
847.473.4545
========================