DNS issues.

[TheFridgeMaster]

Hi All,

I seem to be having name resolution problems on BT4.

I can connect via Ethernet and get internet, i can connect to other access points and have internet but i just cant seem to connect to my access point anymore.

Its odd as i have tried everything. Manually connecting to the access point using wpa_supplicant, stopped and started networking multiple times, rebooted, manually set dns server and IP address but no success.

I am fairly familiar with linux, I just cant seem to get this damn thing to work.

It associates but It cant resolve host names.

Help would be much appreciated

Cheers,
Kyle.

[lupin]

I think you're going to need to provide more detail.

After confirming that your network setup is appropriate by successfully connecting with some other system, explain how your network is setup and the exact steps you used to configure networking on BackTrack plus the output of the relevant configuration commands and files, as well as outputs from the appropriate diagnostic tools. Since you mentioned that you were familiar with Linux I'll assume you know which commands, files and tools Im referring to.

[TheFridgeMaster]

I think you're going to need to provide more detail.

After confirming that your network setup is appropriate by successfully connecting with some other system, explain how your network is setup and the exact steps you used to configure networking on BackTrack plus the output of the relevant configuration commands and files, as well as outputs from the appropriate diagnostic tools. Since you mentioned that you were familiar with Linux I'll assume you know which commands, files and tools Im referring to.

OK when i say 'familiar' I mean in my own ranking system if you will.. ha ha.

My network settings are fine as i have 3 PC's already connected on the network and 2 of them use wireless. The annoying part is backtrack used to connect to the wifi and now it doesn't.

If you could tell me what to check for and what to run it will both teach more how to as well as give you more info on the problem.

Cheers.

[TheFridgeMaster]

I think you're going to need to provide more detail.

After confirming that your network setup is appropriate by successfully connecting with some other system, explain how your network is setup and the exact steps you used to configure networking on BackTrack plus the output of the relevant configuration commands and files, as well as outputs from the appropriate diagnostic tools. Since you mentioned that you were familiar with Linux I'll assume you know which commands, files and tools Im referring to.

I pulled this from the wicd log.

2010/08/27 19:45:05 :: trying to load backend external
2010/08/27 19:45:05 :: trying to load backend ioctl
2010/08/27 19:45:05 :: WARNING: python-iwscan not found, falling back to using iwlist scan.
2010/08/27 19:45:05 :: WARNING: python-wpactrl not found, falling back to using wpa_cli.
2010/08/27 19:45:06 :: Listening on LPF/wlan0/00:21:63:30:08:49
2010/08/27 19:45:06 :: Sending on LPF/wlan0/00:21:63:30:08:49
2010/08/27 19:45:06 :: Sending on Socket/fallback
2010/08/27 19:45:10 :: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
2010/08/27 19:45:11 :: DHCPOFFER of 192.168.1.3 from 192.168.1.1
2010/08/27 19:45:11 :: DHCPREQUEST of 192.168.1.3 on wlan0 to 255.255.255.255 port 67
2010/08/27 19:45:11 :: DHCPACK of 192.168.1.3 from 192.168.1.1
2010/08/27 19:45:11 :: bound to 192.168.1.3 -- renewal in 119147 seconds.
2010/08/27 19:45:11 :: DHCP connection successful
2010/08/27 19:45:11 :: not verifying
2010/08/27 19:45:11 :: Connecting thread exiting.
2010/08/27 19:45:11 :: Sending connection attempt result Success
2010/08/27 19:45:49 :: attempting to set hostname with dhclient
2010/08/27 19:45:49 :: using dhcpcd or another supported client may work better
2010/08/27 19:45:50 :: Connecting to wireless network leet wireless
2010/08/27 19:45:50 :: attempting to set hostname with dhclient
2010/08/27 19:45:50 :: using dhcpcd or another supported client may work better
2010/08/27 19:45:50 :: attempting to set hostname with dhclient
2010/08/27 19:45:50 :: using dhcpcd or another supported client may work better
2010/08/27 19:45:51 :: Putting interface down
2010/08/27 19:45:51 :: Releasing DHCP leases...
2010/08/27 19:45:51 :: attempting to set hostname with dhclient
2010/08/27 19:45:51 :: using dhcpcd or another supported client may work better
2010/08/27 19:45:51 :: Setting false IP...
2010/08/27 19:45:51 :: Stopping wpa_supplicant
2010/08/27 19:45:51 :: Flushing the routing table...
2010/08/27 19:45:51 :: Putting interface up...
2010/08/27 19:45:53 :: Generating psk...
2010/08/27 19:45:53 :: Attempting to authenticate...
2010/08/27 19:46:01 :: Running DHCP with hostname bt
2010/08/27 19:46:01 :: attempting to set hostname with dhclient
2010/08/27 19:46:01 :: using dhcpcd or another supported client may work better
2010/08/27 19:46:01 :: Internet Systems Consortium DHCP Client V3.1.1
2010/08/27 19:46:01 :: Copyright 2004-2008 Internet Systems Consortium.
2010/08/27 19:46:01 :: All rights reserved.
2010/08/27 19:46:01 :: For info, please visit DHCP | Internet Systems Consortium
2010/08/27 19:46:01 ::
2010/08/27 19:46:02 :: Listening on LPF/wlan0/00:21:63:30:08:49
2010/08/27 19:46:02 :: Sending on LPF/wlan0/00:21:63:30:08:49
2010/08/27 19:46:02 :: Sending on Socket/fallback
2010/08/27 19:46:02 :: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
2010/08/27 19:46:03 :: DHCPOFFER of 192.168.1.3 from 192.168.1.1
2010/08/27 19:46:03 :: DHCPREQUEST of 192.168.1.3 on wlan0 to 255.255.255.255 port 67
2010/08/27 19:46:03 :: DHCPACK of 192.168.1.3 from 192.168.1.1
2010/08/27 19:46:03 :: bound to 192.168.1.3 -- renewal in 111643 seconds.
2010/08/27 19:46:03 :: DHCP connection successful
2010/08/27 19:46:03 :: not verifying
2010/08/27 19:46:03 :: Connecting thread exiting.
2010/08/27 19:46:03 :: Sending connection attempt result Success
2010/08/27 19:46:18 :: attempting to set hostname with dhclient
2010/08/27 19:46:18 :: using dhcpcd or another supported client may work better
2010/08/27 19:51:13 :: Daemon going down, killing wicd-monitor...
2010/08/27 19:51:13 :: Removing PID file...
2010/08/27 19:51:13 :: Shutting down...