<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> Craig White wrote: <blockquote cite="mid1149982265.23592.2.camel@lin-workstation.azapple.com" type="cite"> <pre wrap="">On Sat, 2006-06-10 at 18:17 -0500, Bill Polhemus wrote: </pre> <blockquote type="cite"> <pre wrap="">Les Mikesell wrote: </pre> <blockquote type="cite"> <pre wrap="">Can you connect with smbclient? </pre> </blockquote> <pre wrap="">Lee: Here's what I tried, and what I got: # smbclient --ip-address xx.xx.xxx.xx --user myuser //myserver/myshare timeout connecting to xx.x.xxx.xx:445 timeout connecting to xx.x.xxx.xx:139 Error connecting to xx.x.xxx.xx (Operation already in progress) Connection to myserver failed I tried this first with, and then without, the VPN (pptp) connection running, and got the same result. </pre> </blockquote> <pre wrap="">---- Unless your remote doesn't have a firewall and the entire path from your connection to the remote doesn't block ports 137-139 & 445, you aren't likely to connect to the remote without a VPN. Blocking ports 137-139 & 445 with firewalls is what a firewall is supposed to accomplish. Thus, you have to use a VPN. Once you are connected to the vpn, can you ping the remote server? If you can't ping it, it's highly unlikely you are going to be able to connect to it via smb/cifs client Craig </pre> </blockquote> Yes, I can connect to it using the PPTP client, and yes, I can ping the server. When I connect via the PPTP client, this is what I get: Using interface ppp0 pptpconfig: monitoring interface ppp0 Connect: ppp0 <--> /dev/pts/3 MPPE 128-bit stateless compression enabled local IP address 10.1.8.23 remote IP address xx.x.xxx.xx primary DNS address 10.1.2.1 secondary DNS address 10.1.2.3 pptpconfig: pppd process exit status 0 (started) ip route replace xx.x.xxx.xx via 192.168.1.5 dev eth0 src 192.168.1.105 pptpconfig: routes added to remote networks pptpconfig: DNS changes made to /etc/resolv.conf pptpconfig: connected ping -c 5 xx.x.xxx.xx PING xx.x.xxx.xx (xx.x.xxx.xx) 56(84) bytes of data. 64 bytes from xx.x.xxx.xx: icmp_seq=1 ttl=114 time=61.7 ms 64 bytes from xx.x.xxx.xx: icmp_seq=2 ttl=114 time=63.5 ms 64 bytes from xx.x.xxx.xx: icmp_seq=3 ttl=114 time=67.8 ms 64 bytes from xx.x.xxx.xx: icmp_seq=4 ttl=114 time=63.5 ms 64 bytes from xx.x.xxx.xx: icmp_seq=5 ttl=114 time=65.0 ms --- xx.x.xxx.xx ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4006ms rtt min/avg/max/mdev = 61.723/64.349/67.835/2.051 ms ________________________ Also, /etc/resolv.conf looks like this: nameserver 10.1.2.1 nameserver 10.1.2.3 ________________________ Then, when I disconnect, this is what I get: pptpconfig: restoring routing and DNS configuration ip route del xx.x.xxx.xx via 192.168.1.5 dev eth0 src 192.168.1.105 mv /etc/resolv.conf.orig.MYSERV /etc/resolv.conf pptpconfig: routing and DNS configuration restored </body> </html>