Raspberry Pi ...

[campbell]

I just junked a 10 yr old Dell in perfectly serviceable condition which you could've had gratis, Nizz

[BiggestNizzy]

The original plan was to run a win xp machine with wamp for the web server and a copy of exel running in the background to generate the html. I thought the raspberry pi would have been easy, and It meant I could power it from the usb ports on the monitor. It also meant I could use it as an excuse to brush up on my php.

[campbell]

The old Dell was XP

[robin]

I should point out that my original post on this thread asking for R.Pi was meant to be tongue in cheek. Thanks to all those offering me their spare kit!

Cheers,
Robin

[BiggestNizzy]

pi@raspberrypi ~ $ ping 192.168.##.#
PING 192.168.16.3 (192.168.##.#) 56(84) bytes of data.
64 bytes from 192.168.##.#: icmp_req=1 ttl=128 time=13.9 ms
64 bytes from 192.168.##.#: icmp_req=2 ttl=128 time=71.5 ms
64 bytes from 192.168.##.#: icmp_req=3 ttl=128 time=26.2 ms
^C
--- 192.168.##.# ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 13.974/37.235/71.521/24.753 ms
pi@raspberrypi ~ $ telnet 192.168.##.# 1433
Trying 192.168.##.#...
telnet: Unable to connect to remote host: Connection timed out

[graeme]

Is your raspberry pi in the same subnet as your SQL server? Can you post the output of "ifconfig" from the pi?



Other possible issues:
1) Your SQL server is on a non-standard port (something other than 1433). Ask IT to confirm.
2) Your SQL server is restricted to only accept connections from certain IPs. Ask IT to confirm.
3) There's an over-zealous firewall in the way (more likely if they're not in the same subnet, hence the question above). Ask IT to confirm.

[BiggestNizzy]

Is your raspberry pi in the same subnet as your SQL server? Can you post the output of "ifconfig" from the pi?

Other possible issues:
1) Your SQL server is on a non-standard port (something other than 1433). Ask IT to confirm.
Unknown - have asked Emax as they set it up.
2) Your SQL server is restricted to only accept connections from certain IPs. Ask IT to confirm.
Nope
3) There's an over-zealous firewall in the way (more likely if they're not in the same subnet, hence the question above). Ask IT to confirm.
no firewall.

pi@raspberrypi ~ $ ifconfig
eth0 Link encap:Ethernet HWaddr b8:27:eb:f0:7a:2b
inet addr:192.168.###.5 Bcast:192.168.###.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1490712 errors:0 dropped:5381 overruns:0 frame:0
TX packets:179494 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:90376623 (86.1 MiB) TX bytes:15217014 (14.5 MiB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:708 errors:0 dropped:0 overruns:0 frame:0
TX packets:708 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:36924 (36.0 KiB) TX bytes:36924 (36.0 KiB)

C:\Users\gnisbet>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : PC-280612-W7
Primary Dns Suffix . . . . . . . : ####.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : ####.local

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : ####.local
Description . . . . . . . . . . . : Intel(R) 82579LM Gigabit Network Connecti
on
Physical Address. . . . . . . . . : 5C-F9-DD-74-FF-67
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::e42f:b0cb:1974:d62%11(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.###.154(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : 09 March 2015 07:54:38
Lease Expires . . . . . . . . . . : 10 March 2015 07:54:39
Default Gateway . . . . . . . . . : 192.168.###.1
DHCP Server . . . . . . . . . . . : 192.168.###.4
DNS Servers . . . . . . . . . . . : 192.168.###.4
192.168.###.16
8.8.8.8
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.####.local:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : ####.local
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 11:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

[graeme]

Stop hashing stuff out! Makes it harder. It's all non-routable so there's no security risk to telling us how your internal network looks. If anyone gets that far they can figure it out for themselves in seconds anyway. My home web server is 10.5.0.202. See, not scared.

So, the SQL server is 192.168.16.3
The Pi is 192.168.SOMETHING.5
What's this WinPC? That's not the SQL server, so how does that fit in?

What's the full Pi address WITHOUT HASHES!

[BiggestNizzy]

Stop hashing stuff out! Makes it harder. It's all non-routable so there's no security risk to telling us how your internal network looks. If anyone gets that far they can figure it out for themselves in seconds anyway. My home web server is 10.5.0.202. See, not scared.

So, the SQL server is 192.168.16.3
The Pi is 192.168.SOMETHING.5
What's this WinPC? That's not the SQL server, so how does that fit in?

What's the full Pi address WITHOUT HASHES!

I'm paranoid

the pi is 192.168.16.5

[graeme]

OK, so they're both on the same subnet (192.128.16.0/24). It could still be firewall restriction, but that makes it a bit less likely.

I think you still need to check with IT which port the SQL Server listens on to see if it has been changed, and whether any old PC can connect to it or if it has been restricted by IP address. Both those things are SQL Server configuration, so you'll need the help of the IT bods that maintain the server.

If they can't help, there are ways, but best to just ask first.

[robin]

You can verify the 1433 part by looking at the ODBC connection configuration on the windows PC that is able to access the SQL server. If you dig about here:

https://msdn.microsoft.com/en-us/library/ms188691.aspx

You should find one on your PC (assuming your PC is using ODBC to connect Access/Excel to the SQLServer).

Cheers,
Robin

[BiggestNizzy]

Running std ports
Microsoft SQL Native Client Version 09.00.5000

Data Source Name: myEMAX
Data Source Description:
Server: HYSPEC-APPS\SQL2008
Use Integrated Security: No
Database: Emax-Live
Language: (Default)
Data Encryption: No
Trust Server Certificate: No
Multiple Active Result Sets(MARS): No
Mirror Server:
Translate Character Data: Yes
Log Long Running Queries: No
Log Driver Statistics: No
Use Regional Settings: No
Use ANSI Quoted Identifiers: Yes
Use ANSI Null, Paddings and Warnings: Yes

All the ports-1433, 1434 and 2382 are open (from IT)

[graeme]

Not convinced, but ok, we'll move on.

Next step, what happens if you telnet to the other ports, 1434 and 2382.? Also, try 21, 80, 443 and 3389. A connection would be a good sign, but no connection isn't necessarily bad. Just a bit of shooting in the dark to see what happens.

Then on the pi, run (without the '#' that represents the pi user's bash prompt)

# sudo apt-get -y install tcpdump

Then run the following commands one at a time

# cd ~

(change to the pi user's home directory, so we have permissions to write a logfile to the current directory)

# sudo tcpdump -v host 192.168.16.3 > tcpdump.log &

(run tcpdump, logging all traffic to the sql server ip and redirect the output to a file called tcpdump.log, instead of just spewing it onto the screen. The '&' runs this in the background so we can do other things while it's logging).

# telnet 192.168.16.3 1433

(try the telnet again, so tcpdump can capture the traffic. Wait for it to connect or time out or whatever. Quit the telnet connection and get back to bash prompt)

# fg

(to bring the tcpdump process back to the foreground)

Ctrl-C

(to kill the tcpdump process and stop logging)

Then edit tcpdump.log (using nano or vi or your choice of editor) and send me the contents (or paste them up if it's not too long).

[graeme]

Next test:

# sudo apt-get -y install nmap

# nmap -p0-10000 192.168.16.3

(this port-scans the sql server to see what ports are open)

Copy and paste the output here, or PM me with it.

[BiggestNizzy]

tcpdump Log comes back with nothing

nmap comes
PORT STATE SERVICE
135/tcp open msrpc
139/tcp open netbios-ssn
445/tcp open microsoft-ds
3389/tcp open ms-wbt-server
5357/tcp open wsdapi
10000/tcp open snet-sensor-mgmt