Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

IP / wireless issue on sql

Status
Not open for further replies.

tbalazs

IS-IT--Management
Dec 18, 2000
158
GB
sql 2003 on server 2003. When users are assigned new IP addresses over wireless they can no longer log in although they can otherwise access the network normally. Is this likely to be a wireless (latency?) issue or an IP issue?
Thanks.
Tony.
 
sql 2003 on server 2003.

There isn't any SQL Server 2003. There are 2000 and 2005. Which do you have?

Are you getting any errors in the SQL Server Error log or the Windows Event Viewer logs?

-SQLBill

Posting advice: FAQ481-4875
 
Thanks SQLBill.
It's SQL 2000
The logs we're getting look like this. Only happens when wireless:

@@ 20-Mar-2006 02:56 pm : FabienneE : FileDate 09-Nov-2005
Forms : , Applicants
Access violation at address 00494DFF in module 'ITRISR.EXE'. Read of address 00000057
FORMS: ,

@@ 11-Apr-2006 05:33 pm : FabienneE : FileDate 09-Nov-2005
Forms : [ApplicantsForm], Applicants

FORMS: ,

@@ 11-Apr-2006 05:33 pm : FabienneE : FileDate 09-Nov-2005
Forms : [ApplicantsForm], Applicants
Connection to database lost.
FORMS: ,
 
You say they can access the network without problems. How about other files on the W2K3 server? Do you have a shared file on the W2K3 server that you can test their access with? If not, create one. See if they can connect to that file. That will narrow it down to if it's just SQL Server or if the problem is with W2K3.

What OS are your clients using?

Also, those look like Windows Event Viewer log errors. Were there any SQL Server Error Log messages? (Use Enterprise Manager, drill down to Management, expand that, expand Error Logs and look at the most recent one).

If you aren't seeing login failures in SQL Server (and you have login failure auditing set), then the problem is strictly with W2K3.


-SQLBill

Posting advice: FAQ481-4875
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top