Re: Network Question on Cluster - Windows 2003 Enterprise R2 server
- From: "Chuck [MSFT]" <ctimon@xxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 21 Nov 2007 19:11:35 -0500
When you are copying, are you opening the SMB connection using NetBIOS or DNS name resolution? If yes, try opening the connection using an IP address and see what the behavior is.
--
Chuck Timon, Jr.
Microsoft Corporation
Windows Server 2008 Readiness Team
This posting is provided 'AS IS" with no warranties, and confers no rights.
"Sabo, Eric" <sabo_e@xxxxxxx> wrote in message news:%23zXyNNFLIHA.5580@xxxxxxxxxxxxxxxxxxxxxxx
Still having the problem. It seems to work sometimes and then other times it does not work.
Does anyone have an suggestions?
Any post SP2/preSP3 hotfixes that might apply here?
"Sabo, Eric" <sabo_e@xxxxxxx> wrote in message news:OYQN0oIKIHA.2480@xxxxxxxxxxxxxxxxxxxxxxxYes, our bind order is like what you posted.
This is really strange. Only one node out of three is having these issues. checked all network settings and cables today.
"Joseph T Corey" <jcorey@xxxxxxxxxxxxxx> wrote in message news:164BEEE6-D15D-4654-9E71-646B27D5EFAE@xxxxxxxxxxxxxxxxHave you checked your network binding orders (Network Connections, Advanced, Advanced Settings, Adapters and Bindings tab). For each cluster node, the binding order should be:
1) Public
2) SAN (in you case your SAN/iSCSI connection will be 2 and 3
4) Heartbeat
--
Joseph T. Corey MCSE, Security+
Systems Administrator
jcorey@xxxxxxx
"Sabo, Eric" <sabo_e@xxxxxxx> wrote in message news:OVILV9%23JIHA.3356@xxxxxxxxxxxxxxxxxxxxxxxWe have a 3 node Windows 2003 Enterprise R2 cluster running Exchange 2007. I found something very interesting.
I tried a copying data from one node to another server, which both servers should use the public network connection but this does not happen. (data from being copied from local disk drive to local disk drive - ISCSI storage should have been involved in the copy of this data)
Network configuration for both servers:
Cluster node has the following for network connection:
Public Network NIC - goes on our public VLAN
ISCSI # 1 NIC - goes on our ISCSI # 1 VLAN (172.16.1.X subnet mask used is 255.255.255.0)
ISCSI # 2 NIC - goes on our ISCSI # 2 VLAN (172.16.2.X subnet mask used is 255.255.255.0)
Cluster Heatbeat NIC - goes to CH VLAN (172.16.3.X subnet mask used is 255.255.255.0)
Other Server (copying data from)
Public Network NIC - goes on our public VLAN
ISCSI # 1 NIC - goes on our ISCSI # 1 VLAN (172.16.1.X subnet mask used is 255.255.255.0)
ISCSI # 2 NIC - goes on our ISCSI # 2 VLAN (172.16.2.X subnet mask used is 255.255.255.0)
What I discovered was Cluster server was trying to use ISCSI # 1 VLAN NIC to Other Server Public NIC while copying this data.
Thanks in advance!
Eric Sabo
.
- Follow-Ups:
- Re: Network Question on Cluster - Windows 2003 Enterprise R2 server
- From: Sabo, Eric
- Re: Network Question on Cluster - Windows 2003 Enterprise R2 server
- References:
- Network Question on Cluster - Windows 2003 Enterprise R2 server
- From: Sabo, Eric
- Re: Network Question on Cluster - Windows 2003 Enterprise R2 server
- From: Joseph T Corey
- Re: Network Question on Cluster - Windows 2003 Enterprise R2 server
- From: Sabo, Eric
- Re: Network Question on Cluster - Windows 2003 Enterprise R2 server
- From: Sabo, Eric
- Network Question on Cluster - Windows 2003 Enterprise R2 server
- Prev by Date: Re: Stretched Cluster on Windows 2008 - Heartbeat question
- Next by Date: Remove Site Cluster
- Previous by thread: Re: Network Question on Cluster - Windows 2003 Enterprise R2 server
- Next by thread: Re: Network Question on Cluster - Windows 2003 Enterprise R2 server
- Index(es):
Relevant Pages
|