Problem connecting to SQLServer after network reorg

[wyldsider]

long and short of it is that we went from a network where we had a proxy server as our gateway (no PDC) to using a LinkSys router as our gateway. Before, everyone was able to log on to one of the computers running SQLServer 2K (MSDE) and now no one can unless they are on that computer itself.

Any ideas if this is a networking issue or a SQL Server issue? Any one else have this problem?

cheers,
Jack

Jack De Winter
Software Developer
MedTel Software

http://www.medtel.on.ca

 

[TitleistDBA]

Did the PC have a static IP address? Can you ping the PC from outside the linksys? It definetly sounds like a Network problem. You could also check what network traffic is getting through the Linksys.

http://www.acushnetcompany.com

 

[wyldsider]

IP traffic to the machine is fine. Pings work, and network traffic seems to be fine. It only seems to be this one machine that is having a problem. We have 5 2K machines in the office, and this seems to be the only one with this problem.

Jack De Winter
Software Developer
MedTel Software

http://www.medtel.on.ca

 

[SQLBill]

Is the port being blocked by the router?

The LinkSys router can be configured as a firewall also. Maybe that has happened and the port for SQL Server (usually TCP 1433) is blocked.

-SQLBill

 

[wyldsider]

Would blocking the port happen if you were trying to access it from the other side of the router, or the inside.

Basically, there is my machine (as an example) and the server machine. They both use the LinkSys to shove packets around, but I would have assumed that port 1433 would only be blocked if someone from the other side of the router tried to access it.

cheers,
Jack

Jack De Winter
Software Developer
MedTel Software

http://www.medtel.on.ca

 

[SQLBill]

From your computer do this (you may need admin privileges):

Start>Run type in cmd and click on OK
that will open a command prompt window.

At the prompt, type tracert <sqlserver ip>
replace the <sqlserver ip> with the actual IP address for the SQL Server: tracert 123.123.123.123

Run that. It will show you the path a 'packet' takes to go from your machine to the SQL Server machine. Does it go through the router?

-SQLBill

 

[wyldsider]

Nope, goes straight to the machine in question. We are also having problems from some machines access a data drive on the same computer? Perhaps a SOCKS or PDC problem?

cheers,
Jack

Jack De Winter
Software Developer
MedTel Software

http://www.medtel.on.ca

 

[SQLBill]

What type of authentication are you using? Windows or SQL Server?

Two places to check in Enterprise Manager.
First right click on the Server, select Properties, go to Security tab - what is the authentication setting?
Then drill down to Security, expand that, click on Logins, right click on a login that's having problems, on General tab what is the authentication setting?

-SQLBill

 

[wyldsider]

This is going against MSDE. I develop using a developer's edition of SQL Server, so I have the tools here, but not on that machine. My copy of EM cannot seem to connect up to that machine, it gets the same error as if I am trying to do a normal connection.

When I install, I do:

setup.exe /qb+ INSTANCENAME=fred SAPWD=nobusiness SECURITYMODE=SQL

ideas?
thanks,
Jack

Jack De Winter
Software Developer
MedTel Software

http://www.medtel.on.ca