My First thread with TcpListener 
static void Main(string[] args)
TcpListener listener = new TcpListener(IPAddress.Any , 8000);
TcpClient client;

while (true) // Add your exit flag here
client = listener.AcceptTcpClient();
ThreadPool.QueueUserWorkItem(ThreadProc, client);
private static void ThreadProc(object obj)
var client = (TcpClient)obj;
// Do your work here

[ 發表回應 ]   |  常註連結  |   ( 3.1 / 16 )
fixing VPN problem in Ubuntu Windows 
Source : ... buntu.html

fixing VPN problem in Ubuntu

I set up VPN in Ubuntu 14.04, but when I tried to turn it on in NetworkManager, I kept getting errors like "No suitable device found", "Could not find source connection" in /var/log/syslog.

The problem turned out to be that my ethernet connection was not managed by NetworkManager. "nmcli c" didn't show my wired connection.

The solution:
Edit /etc/NetworkManager/NetworkManager.conf, in section [ifupdown], change "managed=false" to "managed=true", then do a:
"sudo service network-manager restart"
Now both vpn and ethernet connections are managed by NetworkManager, turning on VPN just works.

About Having DNS Issues when connected to a VPN

source :

I am connecting to a Cisco VPN Server using vpnc. Once connected, my machine was unable to automatically update DNS setting from the new VPN. I tested by temporarily changing /etc/resolv.conf with the proper nameserver and search domain, and everything worked. This is obviously not a long term solution, so I added an additional DNS server and search domain to the VPN settings in Network manager. With those settings in place, resolvconf does add the search domain, but not the DNS IP, and I still cannot do any lookups.

What is my next step in configuring or troubleshooting from here?


First make sure that there are no lines beginning with nameserver in any files in /etc/resolvconf/resolv.conf.d. If /etc/resolvconf/resolv.conf.d/tail is a symbolic link to target original, make it point to /dev/null.

Second, disconnect from the VPN. Edit /etc/NetworkManager/NetworkManager.conf

$ sudo gedit /etc/NetworkManager/NetworkManager.conf

and comment out

(i.e., add a # so that it looks like the following)

and then

sudo service network-manager restart

[ 發表回應 ]   |  常註連結  |   ( 3.3 / 13 )
PPTP Client Auto Reconnect Note 
# Create vpn Connection
pptpsetup --create vpnhk --server x.x.x.x --username vpn-user-name --password vpn-password --encrypt --start
pptpsetup --create vpnlw --server y.y.y.y --username vpn-user-name --password vpn-password --encrypt --start
pptpsetup --create vpnfw --server z.z.z.z --username vpn-user-name --password vpn-password --encrypt --start

# Manual Connect VPN
pon vpnhk updetach
pon vpnlw updetach
pon vpnfw updetach

# Manual Disconnect All VPN
poff -a

# Manual Route Add
route add -net netmask dev ppp0
route del -net netmask

# Setup Boot up ppp Auto Connection
auto vpnhk
iface vpnhk inet ppp
provider vpnhk

auto vpnlw
iface vpnlw inet ppp
provider vpnlw

auto vpnhk
iface vpnhk inet ppp
provider vpnlw

# added by pptpsetup
joehome vpnhk "EV2340~9"
joehome vpnfw "EV2340~9"
joehome vpnlw "EV2340~9"

# Auto pptp Re-connection modify Sample
# written by pptpsetup
pty "pptp --nolaunchpppd"
name joehome
remotename vpnfw
ipparam vpnfw
maxfail 0

# Install quagga Dynamic Route tools
apt-get install quagga

# Dynamic Route Configuration, Need install quagga

# Dynamic Route Table setting, Need install quagga
hostname AnyName
password YourPassword
enable password YourPassword
ip route
ip route
ip route
ip route
ip route

# Dynamic Route Restart
/etc/init.d/quagga restart

[ 發表回應 ] ( 30預覽 )   |  常註連結  |   ( 2.9 / 140 )
<window root>system32 missing or corrupt [Solved/Closed] 
Source : ... or-corrupt

If you have a black screen with a messages like those :

>Windows could not start because the following file is missing or corrupt:

>Windows NT could not start because the below file is missing or corrupt:

>Windows NT could not start because the below file is missing or corrupt:

>NTLDR is Missing
Press any key to restart

>Invalid boot.ini
Press any key to restart

Repair with XP CD :
1. Boot with CDROM
2. Enter the installer XP CD
3. Press R if like this :

4. Press 1(or the other that show the installation drive) and enter the admin ]

5. Type Like This :
> C: CD ..
> C: ATTRIB –H C:boot.ini
> C: ATTRIB –S C:boot.ini
> C: ATTRIB –R C:boot.ini
> C: del boot.ini
> C: BOOTCFG /Rebuild

6. After Rebuild finish type this:
C: CHKDSK /R /F kemudian
“Sure you want to write a new bootsector to the partition C: ?” press “Y”

Hope this can be help you ..
forza la beneamata

[ 發表回應 ] ( 2預覽 )   |  常註連結  |   ( 3 / 297 )
MS Access: upsizing to SQL Server 2008 
Source : (Cypris).Cypris' lookout. ... rver-2008/

I’m currently researching ways to move my main MS Access application from a simple local network client/backend setup to a global, multiple remote sites configuration using SQL Server.

One of the challenges is to upsize the current MS Access 2007 backend database to SQL Server 2008. If you try it from Access itself using the Upsizing Wizard, you may end up getting this error message:

The Upsizing Wizard only works with Microsoft SQL Server (Versions 6.50 SP5 or higher). Please log in to a SQL Server data source.

After spending some time fiddling around with SQL Server settings I couldn’t understand why I was still getting this error.
Turns out that the upsizing wizard is apparently sensitive to the version of SQL Server you’re using and it doesn’t consider SQL Server v10 (2008) as being later than v6.50…

This issue is in fact a blessing.
Microsoft provides a migration tool for upsizing MS Access database to SQL Server 2008 that’s orders of magnitude better than anything the basic wizard can do: the SQL Migration Assistant for Access, or SSMA.

SSMA lets you take a bunch of Access databases and move the tables and queries you choose to SQL Server, automatically linking them in your original database if you want.
It’s not just a one-off thing either: SSMA keeps track of the objects that where transferred and allows you to synchronise both schema and data as often as you need.

So here you are: do not use the basic MS Access Upsizing Wizard, download and use SSMA instead.

Strange COM Error
While SSMA works perfectly fine on my Windows 2008 x64 laptop, on my main Windows XP desktop it throws an exception when trying to load an Access database:

Unable to cast COM object of type ‘Microsoft.Office.Interop.Access.Dao.DBEngineClass’ to interface type ‘Microsoft.Office.Interop.Access.Dao._DBEngine’
… {00000021-0000-0010-8000-00AA006D2EA4}…

It was a COM error saying that the library for DAO couldn’t be loaded.
I couldn’t find any relevant information on the web.
After a while, I had a look at the DAO driver in
C:\Program Files\Common Files\Microsoft Shared\DAO\dao360.dll
and I noticed that the filename was in blue: that reminded me that I had set compression on the filesystem.

I disabled compression for the file and, magically, SSMA worked again…

Moral of the story: be careful about compressing your filesystem, some registered libraries and system files may work in unpredictable ways…

[ 發表回應 ] ( 72預覽 )   |  常註連結  |   ( 2.9 / 757 )

| 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 下一頁> >>