|Last week I hosted an ad-hoc network with WPA2-Personal encryption and static IP's. We were all able to see each other and ping each other. The host, me, is logged into a domain account, on the college's domain (my dorm has access to campus wireless). All the clients are not part of this domain, but part of a workgroup and log into the wireless with their account info.|
- Host(me): OS: Windows 7 Professional 64-bits ; IP: 192.168.0.105
- Client 1: OS: Windows 7 Home Premium 64-bits ; IP: 192.168.0.106
- Client 2: OS: Windows 8 ; IP: 192.168.0.107
- Client 3: OS: Windows 7 Home Premium 64-bits ; IP: 192.168.0.108
This week I tried to host it again but it failed, I can no longer see anyone else and can't ping anyone else. Same for anyone else in the ad-hoc network.
If Client 1 or 2 hosts however they can see each other and ping. If I log out of the domain, switch to a workgroup and log in locally I can join the ad-hoc network and everything runs smoothly.
But switching between the college domain and a workgroup is a pain in the ass of course.
Using the software 'Connectivity' does allow me to create an ad-hoc network in which we can see each other and ping, but it comes with lag and eventual timeouts.
- Can I resolve this so I can log into the ad-hoc network with my domain account ?
- Why has it suddenly stopped working since it ran smoothly last week ?