Server 2008 SQLEXPRESS not listening of one workstation

I have 5 workstations and 4 are working properly (two are Vista Ultimate and 2 are Windows 7 Pro) to run an ACCDE program on my “TED” server 2008 R2.

 Workstation #5 is “TIM” Vista Ultimate and is only one not working.   On TIM and using SYSWOW\Odbcte32.exe to test the connection I enter TED\SQLESPRESS and it fails (as if Server not listening) because if I change to add port as follows: TED\SQLEXPRESS, 1433 it will connect.  As ACCDE (is DSNLess) and uses only TED\SQLEXPRESS I would like all 5 to work the same.  

Following suggestions in article re: listening problems ….  In Windows Firewall on TIM  I added a custom inbound rule to add the IP address of my server “TED” to allow this connection.  That did not help.  I also blindly added MSACCESS.EXE outbound rule, but that did not help either.

Anybody have any ideas???   Thanks….
FrankBabzAsked:
Who is Participating?
 
MikeNetwork & Systems ManagerCommented:
Do you have a native sql driver installed on the other PCs that you don't on the one that isn't working? You can check this when you add a new data source in odbcad32.
0
 
MikeNetwork & Systems ManagerCommented:
Have you tried disabling the firewall on TIM completely and testing again to see if that helps, if nothing else it would confirm the firewall to be the problem. You could also do the same on TED to rule out the firewall on that blocking connections from TIM. I am not suggesting you leave the firewall disabled, just do it as a quick test.
0
 
FrankBabzAuthor Commented:
Per your suggestion Mike...  I was very surprised to find that turning off both firewalls had no effect.  I was convinced it was a firewall issue...   Why, is because I have this same ACCDE working on four other PCs of which 2 are an identical Vista OS...  AND because all 3 matching PCs include the same User Account "JOE" that works on 2 and that should eliminate possible account issues on TED.

I did a quick check on "Joe" permissions on other PCs and they all appear to be the same.  Although.. understanding necessary permissions is not my strong suit.   I can (I think) also focus less on MSACCESS.EXE on TIM because Odbcte32.exe on TIM does not connect w/o me adding the listening port, and BTW adding listening port on other PCs is not needed.  I've been thinking ODBC should not matter because all SQLEXPRESS I/O in the ACCDE is DSNless.  Maybe TIM's ODBC does play some role in this?

Thanks your thoughts....  Frank
0
 
MikeNetwork & Systems ManagerCommented:
SQL driver versions
0
 
FrankBabzAuthor Commented:
Getting right driver was the fix...
Thanks...  Frank
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.