# Can't even get going.. network setup error? **URL:** \ **Category:** Docker Toolbox\ **Created:** [June 8, 2016, 1:53am UTC](https://forums.docker.com/t/cant-even-get-going-network-setup-error/14900 "2016-06-08T01:53:10Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![crazifuzzy](https://avatars.discourse-cdn.com/v4/letter/c/d9b06d/32.png) [@crazifuzzy](https://forums.docker.com/u/crazifuzzy)\ **Post date:** [June 8, 2016, 1:53am UTC](https://forums.docker.com/t/cant-even-get-going-network-setup-error/14900/1 "2016-06-08T01:53:10Z")
So I’ve tried this a few times. This is on Windows 10. On running the Docker Quicstart Terminal, I get: Starting “default”… (default) Check network to re-create if needed… Error setting up host only network on machine start: host-only cidr conflicts with the network address of a host interface Looks like something went wrong in step ´Checking status on default´… Press any key to continue… I’ve tried removing Docker Toolbox and Virtualbox, as well as all the virtual network devices, and letting it all reinstall. I have no idea what this error means, or where to go, and search hasn’t shown anything close to this error. ---
**Author:** ![crazifuzzy](https://avatars.discourse-cdn.com/v4/letter/c/d9b06d/32.png) [@crazifuzzy](https://forums.docker.com/u/crazifuzzy)\ **Post date:** [June 8, 2016, 2:03am UTC](https://forums.docker.com/t/cant-even-get-going-network-setup-error/14900/2 "2016-06-08T02:03:18Z")
Crap - so another search found the issue. It looks like Docker Toolbox is defaulted to set the virtual subnet as 192.168.99.0/24, which is what my LAN uses, so it conflicts. Is there a way to change this behavior? Or is my specific IP range of my network preventing me from using docker toolbox? ---
**Author:** ![crazifuzzy](https://avatars.discourse-cdn.com/v4/letter/c/d9b06d/32.png) [@crazifuzzy](https://forums.docker.com/u/crazifuzzy)\ **Post date:** [June 8, 2016, 2:17am UTC](https://forums.docker.com/t/cant-even-get-going-network-setup-error/14900/3 "2016-06-08T02:17:19Z")
Okay, so I found a solution - I think… I had to add the --virtualbox-hostonly-cidr “x.x.x.1/24” command to choose a new default subnet - but took quite a few tries to figure out how to do that. I had to modify [start.sh](http://start.sh), and add it into the docker-machine create command line. Looks like I’m okay for now, but this really should be documented better, or better yet, autochoose a different range if that IP already exists! ---
**Author:** ![andrewdotdobson](https://avatars.discourse-cdn.com/v4/letter/a/7cd45c/32.png) [@andrewdotdobson](https://forums.docker.com/u/andrewdotdobson)\ **Post date:** [June 15, 2016, 2:48pm UTC](https://forums.docker.com/t/cant-even-get-going-network-setup-error/14900/4 "2016-06-15T14:48:00Z")
Hey. I’m having exactly the same issue. Could you please give me some more detail on the update to [start.sh](http://start.sh) which you made? Thanks. ---
**Author:** ![rubicontext](https://avatars.discourse-cdn.com/v4/letter/r/f08c70/32.png) [@rubicontext](https://forums.docker.com/u/rubicontext)\ **Post date:** [March 5, 2018, 3:22am UTC](https://forums.docker.com/t/cant-even-get-going-network-setup-error/14900/5 "2018-03-05T03:22:31Z")
Same issue here. Any help would be much appreciated. Thanks. ---
**Author:** ![rubicontext](https://avatars.discourse-cdn.com/v4/letter/r/f08c70/32.png) [@rubicontext](https://forums.docker.com/u/rubicontext)\ **Post date:** [March 5, 2018, 3:39am UTC](https://forums.docker.com/t/cant-even-get-going-network-setup-error/14900/6 "2018-03-05T03:39:49Z")
For future reference, I fixed this issue by removing the default machine and recreate it with specific IP docker-machine create -d virtualbox --virtualbox-cpu-count=2 --virtualbox-memory=4096 --virtualbox-disk-size=50000 --virtualbox-hostonly-cidr “192.168.33.1/24” default Works fine now. ---
**Author:** ![marquish](https://avatars.discourse-cdn.com/v4/letter/m/ac91a4/32.png) [@marquish](https://forums.docker.com/u/marquish)\ **Post date:** [September 11, 2019, 6:09am UTC](https://forums.docker.com/t/cant-even-get-going-network-setup-error/14900/7 "2019-09-11T06:09:32Z")
Solved … I was working with Docker Toolbox on Windows Host, For me “Npcap Loopback Adapter” was assigned with static ip of 192.168.99.1 I just browsed to Control Panel\Network and Internet\Network Connections Then converted “Npcap” adapter TCP/IPV4 Address to “Obtain an IP address Automatically” and it worked like a charm.