Kitl on a two network setup, wince 6.0 RRS feed

  • Question

  • Hello,

    I'm having a hard time setting something up. I have this issue at my work where, if I connect to a kitl debug session over ethernet but I'm promptly kicked from the network, my ports deactived, and the IT department given a lot of headaches and paperwork to tell our corporate network nazi's that we can't do our jobs. Apparently productivity isn't a good enough reason to allow us to connect normally with the devices.

    Active Sync is not available. So the solution we came up with is set up a network that isn't connected to the rest of the network. This seems to work and all until I try to connect to the device with visual studio 2005.

    Is there a way to tell visual studio to use the private network I set up instead of the waiting for devices on the corporate network?

    Tuesday, June 26, 2012 2:39 PM

All replies

  • I don't understand, you say "This seems to work and all.."  but follow that with telling us that it doesn't work.   That leads me to beleive that in fact it doesn't work.

    Did you set up the device and your second NIC with IP addresses?   Are they a different subnet from your corporate network?

    Bruce Eitman (eMVP)
    Senior Engineer
    Bruce.Eitman AT Eurotech DOT com
    My BLOG http://geekswithblogs.net/bruceeitman

    Eurotech Inc.

    Tuesday, June 26, 2012 9:25 PM
  • Set the routing table so that the private network is listed first. Loads of articled on the web on how to do this, one example: http://www.windowsnetworking.com/articles_tutorials/making-sense-windows-routing-tables.html

    Good luck,

    Michel Verhagen, eMVP
    Check out my blog: http://guruce.com/blog

    Microsoft Embedded Partner
    Consultancy, training and development services.

    Tuesday, June 26, 2012 9:41 PM
  • Well, i dont' know what is hard to understand, I was able to set up everything except for the one silly issue i have with not being able to control which network programs get onto.

    I have two seperate DHCP servers, one a regular 198.162.1.x and another corpertate blah.blah.blah.blah

    Tuesday, June 26, 2012 9:47 PM