Year: 2017

Message to self: No password in Access when there is an ODBC connection to an SQL server needed

Message to self: Important

When you create a userspace alike ODBC connection in Windows 2008 Server (whatever) it is likely that Access does not allow you to use linked tables as it is requiring a password.
Although you have the ability to store passwords in Access when linking tables through ODBC it is not always working when the ODBC connection is set in the field ‘user’ rather than Machine DataSource/System

The trick is to execute as admin the file c:\windows\SysWOW64\odbc32.exe
Then create the System ODBC connection towards the SQL database, return to your Access file and link the tables (and keep in mind to save the password as well when linking)

I tried above multiple times when the ODBC was in userspace or was (probably) not correctly created (32 versus 64 bits??)
Possible it can also be related that the application pool is 32bits rather then 64bits and the ODBC connection needs 32bits as well .. Hell: if this occurs again, you have some tips ;_)

Edgemax Lite with local domain issues through VPN

I was using a dnsmasq DHCP/DNS server but that version broke due to an software update where it was running. So I changed towards the DHCP and DNS of Ubiquity Edgemax Lite

The issue I had was that local domainnames (FQDN) could not be looked up by its name but only through IP. In the old situation where not the router was the DNS server it was working but in the new environment not. I changed the DNS server to the correct local IP for the local hostnames, but no success.

Than I found a hint in a forum

open a SSH session towards the Edgemax

configure
show service dns

forwarding {
cache-size 400
listen-on eth1
listen-on eth2
name-server 10.1.1.1
name-server 8.8.8.8
name-server 8.8.4.4
system
}

Above is the non working environment for VPN (for all other situations it was ok)

the local name-server was defined but it was probably not available through L2TP VPN

The solution was to add

options listen-address=10.1.1.1 with this command:
configure
set service dns forwarding options "listen-address=x.x.x.x"
commit
save

where x.x.x.x is the IP of the router. It should be the IP address that PPTP/L2TP is returning to the clients for DNS server