Windows Server - connect to cluster share with Ip address 2008 cluster
Asked By Resonate
18-Nov-09 07:06 AM
Hi,
I am having a problem with a 2008 file cluster.
The problem is the network scanning we have. They are multi function
devices that have the ability to scan to and then copy the scan to network
shares.
The problem is that although the devices can be configured to use dns all
they essentially do is lookup the ip address and try to connect to it. So
instead of goign \\clustername\share which they should do they go
\\clusterip\share which does not appear to work in server 2008. When I
browse to \\clusterip from my pc I just see teh shares on the active node
not the cluster.
I have confirmed this bahaviour by doing network traces between the
printer/scanner and the active cluster node.
This to my knowledge is different to 2003 and I need to fix it.
Is there any solution I can put in place before I tell Xerox they need to
rewite their firmware!
Bahaviour
(1)
Firmware
(1)
Rewite
(1)
Goign
(1)
Dns
(1)
Vladimir Petter replied to Resonate
Starting from W2K8 File Server shares are scoped to net-name. Accessing it
by IP address will not work.
Vladimir Petter
Clustering and High Availability.
This posting is provided "AS IS" with no warranties, and confers no rights.

Patching and Firmware versions general question Windows Server Hello, Can anyone tell me whether or not patches deployed from Microsoft are tested against a hardware base to ensure compatibility with certain firmware revisions? Is the best rule of thumb to keep all hardware at current releases? The box crash hard and would only accept the most recent patching package after updating the firmware. Any additional information would be highly appreciated. Alan. Windows Server Discussions WolfRe (1) LearnQuick (1 http: / / www.LearnQuick.Com (phone on web site) Most of the time it assumes the firmware up to date. I'd say half the time it does not matter though. In my experience, keeping firmware up to date is tantamount to ensuring all things, patches included, play nice together and ask for a big fat bonus instead for being so good). ;) Sean keywords: Patching, and, Firmware, versions, general, question description: Hello, Can anyone tell me whether or not patches deployed from
O.T. To all REAYNAS NV+ Owners Do not update to 4.00c1-p1 Firmware. <<<Windows Server > > , O.T., To, all, REAYNAS, NV+, Owners, Do, not, update, to, 4.00c1-p1, Firmware., <<<" / > O.T. To all REAYNAS NV+ Owners Do not update 4.00c1-p1 Firmware. It crashed a clients Unit, and after reading the forum I'm not the only com description: O.T. To all REAYNAS NV+ Owners Do not update 4.00c1-p1 Firmware. It crashed a clients Unit, and after reading the forum I'm not the only
Each Proliant has a QLogic QLA2340 HBA card and is connected to an IBM DS4800 (Firmware 07.10.23). Originally both Prolants were running HBA Driver 9.1.7.16 and Firmware 1.45. Under this configuration both machines were rebooting every so often and we are this Machine1 was changed so it is running HBA Driver 9.1.4.15 and Firmware 1.52. Machine2 is still running HBA Driver 9.1.7.16 and Firmware 1.45. According to the IBM Compatibility Matrix the OS / HBA Firmware / HBA Driver / SAN Firmware are a match for Machine1 so we don't know why it is continuing to reboot. Machine1 also has produced a blue screen crash once after the HBA card firmware was upgraded. May I please know what I can do to troubleshoot this? Thank you Discussions SQL Server 2005 (1) Windows Server 2003 (1) X64 (1) QLogic (1) Prolants (1) Firmware (1) Proliant (1) Matrix (1) This is most likely an HBA Driver / Firmware issue. You