I have had these issues myself and never found a solution for them.
I used Cisco AP 1200s and Intel 3945ABGs configured for WPA2 and had about 95% success for new user logins. And I had 0% success if I tried to force a password change.
What I noticed is that the Intel Software would "lose"...
I have a sonicwall at the edge. ISA is internal with NAT addresses on both sides. I pass DNS forwards through both the ISA and Sonicwall.
My directory is behind the ISA Firewall. All internal DNS never gets out. Only outside addresses are forwarded.
Jeffrey Botsford
MCSE/CCNA/Cyber Forensics L1
I allow DNS outbound through my ISA server. My 2 DNS servers hit the ISPs DNS servers for all external queries.
I would also recommend the following:
http://www.opendns.com/
Putting OPENDNS ahead of my ISPs DNS servers (forwarder) did improve my networks DNS resolution for external sites...
Since your using dyndns this is no problem. Here is how you do it:
In dyndns you should have a record pointing to your domain.
example: mydomain.com
mydomain.com should have a current IP address the same as the IP address (external) on your router. If so, you are good to go. Now you can use...
This requires 2 subnets. I assume the switch is layer 3 capable? If so ip-helper (once set) per vlan will direct clients to the appropriate DHCP server.
If you are attempting to have 2 different subnets on the same VLAN your in trouble.
Jeffrey Botsford
MCSE/CCNA/Cyber Forensics L1
169.254.29.140 is a self assigned address. Windows does this when it cannot receive an address through DHCP. Reset your modem and see what happens. If your using ICS your client machines will receive an address from the 192.168 range
The router would be one line of defense. By plugging your modem into the second nic you have removed the router from the equation all together.
At home I use a linksys router with my cable modem and it is fairly robust for what I need.
Why two NICs? If you have a router there is no reason for a second NIC in the server. All machines would be connected through the switch in the router.
Assuming your running DHCP on your network, your ISPs DNS server should not be listed as a DNS server for your network. That server would have...
maybe i am off here. Your primary DNS server is 139.130.4.5 Your secondary is 192.168.0.1. Shouldn't your primary be 192.168.0.1? In addition, forwarding should be setup on the internal DNS server pointing to 139.130.4.5 for all lookups not resolved by the internal DNS server.
Ensure two NICs are installed. Once that has been accomplished you can share the internet connection by going to the advanced properties tab and selecting internet connection settings.
First, I would get a router (Linksys is what I prefer). These normally come with DHCP functionality. If your playing around you may wish to disable that and run DHCP from the server. (Note: These types of routers are normally set with 192.168.1.1 as their internal address, thus your DHCP scope...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.