Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
januszjasinski
Starting Member
1 Post |
 Posted - 2008-10-08 : 08:56:50
|
Hi,I'm somewhere in the middle between newbie and guru when it comes to SQL Server. However, this one has got me stumped.We had a SQL box sitting somewhere "out there" in the network. I could connect to it fine from whatever server, via code or EM (Enterprise Manager). The IP address changed of the box. It is now on the NHS N3 network. This is when the issue has started.I am on a 200.xxx address and the SQL box is on a 200.xxx address also. From my machine, I can connect via ASP and via EM just fine.However when I'm on a 50.xxx or 100.xxx machine, I can't connect either by ASP or EM. Strange thing is, a colleague who sits next to me is on a 100.xxx address and managed to log in fine this morning via EM. (N.B. address' have been changed for security)The SQL is in a cluster. I cna ping it via IP and via server name just fine from any machine. When I ping it, I get an IP address of: 200.1.1.1Running SQLPING on the problematic machines, I get the following (N.B. the different ServerIP!!!): <?xml version="1.0" encoding="ISO-8859-1"?><SQLReconResults> <SQLReconResult> <ServerIP>200.1.1.2</ServerIP> <TCPPort>1433</TCPPort> <ServerName>NameOfServer</ServerName> <InstanceName>MSSQLSERVER</InstanceName> <BaseVersion>8.00.194</BaseVersion> <SSNetlibVersion /> <TrueVersion /> <ServiceAccount /> <IsClustered>Yes</IsClustered> <Details>(UDP)ServerName;NameOfServer;InstanceName;MSSQLSERVER;IsClustered;Yes;Version;8.00.194;np;\\NameOfServer\pipe\sql\query;tcp;1433;;</Details> <DetectionMethod>UDP</DetectionMethod> </SQLReconResult></SQLReconResults> Has anyone any idea what could be happening? |
|
|
|
|
|
Problems connecting to a SQL Server on a cluster