DNS cache problem

Nerva

Platinum Member
Jul 26, 2005
2,784
0
0
i kind of have run into a problem at work. this computer cannot access the internet, i think the problem is with the dns cache because that's where the repairs hang up. i tried to flush the dns, but it tells me it can't flush it because the command failed at execution or something. when i tried to display the dns, it says it cannot be resolved. does anyone know what i can do to fix this?
 

Nerva

Platinum Member
Jul 26, 2005
2,784
0
0
Originally posted by: blemoine
Running a local dns server or using the isp dns server?


i think it's a local dns server that belongs to my school.
 

DaiShan

Diamond Member
Jul 5, 2001
9,617
1
0
Ok, when you say cannot access the Internet, do you mean you can't get to yahoo.com, or you can't ping ip addresses? Is it set to dhcp or static IP? Which OS is it? What happens when you do ipconfig /release and ipconfig /renew?
 

cleverhandle

Diamond Member
Dec 17, 2001
3,566
3
81
Are you sure you've got basic connectivity? What do you get from "ipconfig /all" (or ifconfig -a on Unix)? Can you ping 216.109.118.76 (Yahoo)? DNS servers can certainly go down, but usually the problem is something simpler.
 

Nerva

Platinum Member
Jul 26, 2005
2,784
0
0
Originally posted by: cleverhandle
Are you sure you've got basic connectivity? What do you get from "ipconfig /all" (or ifconfig -a on Unix)? Can you ping 216.109.118.76 (Yahoo)? DNS servers can certainly go down, but usually the problem is something simpler.

the computer has an assigned ip address, but it won't ping itself. it's running windows xp. all ipconfig commands have failed. the renew function couldn't be executed. the xp repair stops at the dns cache. it's weird, but this computer just can't access any sites.
 

DaiShan

Diamond Member
Jul 5, 2001
9,617
1
0
Originally posted by: 3cho
Originally posted by: cleverhandle
Are you sure you've got basic connectivity? What do you get from "ipconfig /all" (or ifconfig -a on Unix)? Can you ping 216.109.118.76 (Yahoo)? DNS servers can certainly go down, but usually the problem is something simpler.

the computer has an assigned ip address, but it won't ping itself. it's running windows xp. all ipconfig commands have failed. the renew function couldn't be executed. the xp repair stops at the dns cache. it's weird, but this computer just can't access any sites.

Are you on dhcp or static? (did a router assign the ip, or did you?) What is the ip address you get when you type ipconfig /all? Also what is the subnet mask? Make sure that you compare these to the correct settings for your network.

 

cleverhandle

Diamond Member
Dec 17, 2001
3,566
3
81
Originally posted by: 3cho

the computer has an assigned ip address, but it won't ping itself.
Meaning it won't ping 192.168.0.1 (or whatever the address is) or it won't ping 127.0.0.1 (localhost)? If it won't ping localhost, then you've got a problem with the networking stack on the machine. That really shouldn't happen, and I'm not sure how to go about fixing it. If it pings 127.0.0.1, but not the assigned address, then I'd ask how you're finding what that address is, since ipconfig is failing.

edit: In any event, if ipconfig is failing I don't think DNS is the issue here.
 

Nerva

Platinum Member
Jul 26, 2005
2,784
0
0
Originally posted by: cleverhandle
Originally posted by: 3cho

the computer has an assigned ip address, but it won't ping itself.
Meaning it won't ping 192.168.0.1 (or whatever the address is) or it won't ping 127.0.0.1 (localhost)? If it won't ping localhost, then you've got a problem with the networking stack on the machine. That really shouldn't happen, and I'm not sure how to go about fixing it. If it pings 127.0.0.1, but not the assigned address, then I'd ask how you're finding what that address is, since ipconfig is failing.

edit: In any event, if ipconfig is failing I don't think DNS is the issue here.

it's on a static ip and all the subnet mask stuff match that of the other computers. the ip for the computer 192.253.18.156, and i can't even ping that. i get that ip address and all the info by typing ipconfig /all. ipconfig is not exactly failing, just ipconfig /renew and dnsflush
 

cleverhandle

Diamond Member
Dec 17, 2001
3,566
3
81
Originally posted by: 3cho
all ipconfig commands have failed.
ipconfig is not exactly failing, just ipconfig /renew and dnsflush
Try to be careful with your language - it makes a difference in whether people can give you accurate advice.

Can you ping 127.0.0.1?
 

Nerva

Platinum Member
Jul 26, 2005
2,784
0
0
Originally posted by: cleverhandle
Originally posted by: 3cho
all ipconfig commands have failed.
ipconfig is not exactly failing, just ipconfig /renew and dnsflush
Try to be careful with your language - it makes a difference in whether people can give you accurate advice.

Can you ping 127.0.0.1?

yeah sorry about that. i think i might have tried to ping home with it, but that didnt work either.
 

cleverhandle

Diamond Member
Dec 17, 2001
3,566
3
81
Originally posted by: 3cho
Originally posted by: cleverhandle
Can you ping 127.0.0.1?

yeah sorry about that. i think i might have tried to ping home with it, but that didnt work either.
I don't know what "home" means.

If you tried to ping 127.0.0.1 (it's not yet clear to me that you've done this) and that doesn't work, you should try following these instructions to reset TCP/IP.

Also, do you have any firewall programs running on this machine? I don't think that any of them would be dumb enough to filter traffic that isn't crossing an interface, but you never know. Disabling them while you're testing is probably a good idea.

 

Nerva

Platinum Member
Jul 26, 2005
2,784
0
0
Originally posted by: cleverhandle
Originally posted by: 3cho
Originally posted by: cleverhandle
Can you ping 127.0.0.1?

yeah sorry about that. i think i might have tried to ping home with it, but that didnt work either.
I don't know what "home" means.

If you tried to ping 127.0.0.1 (it's not yet clear to me that you've done this) and that doesn't work, you should try following these instructions to reset TCP/IP.

Also, do you have any firewall programs running on this machine? I don't think that any of them would be dumb enough to filter traffic that isn't crossing an interface, but you never know. Disabling them while you're testing is probably a good idea.

i thought 127.0.0.1 was home? i think i pinged that and that didnt work. the computer has zone alarm, but it's shut off. however, the connection itself has a firewall, though i do not think that matters. anyway, thanks for your help, i will forward these ideas to the work people as i wont see through it.

if you have any other ideas, please let me know. danke
 

blemoine

Senior member
Jul 20, 2005
312
0
0
127.0.0.1 is localhost. pinging this address is basically a self test. if you can't ping localhost then you may have a firewall or network card problem.
 

Nerva

Platinum Member
Jul 26, 2005
2,784
0
0
Originally posted by: blemoine
127.0.0.1 is localhost. pinging this address is basically a self test. if you can't ping localhost then you may have a firewall or network card problem.

ok i just pinged 127.0.0.1 and that works. but if i were to do ipconfig /renew or /release. it says that "no adapter is in a state that is permissible for this operation."
 

DaiShan

Diamond Member
Jul 5, 2001
9,617
1
0
Originally posted by: 3cho
Originally posted by: blemoine
127.0.0.1 is localhost. pinging this address is basically a self test. if you can't ping localhost then you may have a firewall or network card problem.

ok i just pinged 127.0.0.1 and that works. but if i were to do ipconfig /renew or /release. it says that "no adapter is in a state that is permissible for this operation."

You have to do /release before you do renew. These flags tell your NIC to release the ip address associated with it, then to pull a new ip address from the dhcp server, so the order matters.

cleverhandle and Spidey07 may be right about the tcp stack, but an alternative hypothesis could be that the settings are not correct for this machine, a screen shot of ipconfig /all and of the tcp/ip properties screen might be helpful, as well as an overview of the ip's and subnets you are using.
 

nweaver

Diamond Member
Jan 21, 2001
6,813
1
0
if you are set to a static IP, a release/renew does NOTHING FOR YOU and that message (no adapter is in a state that is permissible for this operation) is normal.
 

cleverhandle

Diamond Member
Dec 17, 2001
3,566
3
81
Originally posted by: nweaver
if you are set to a static IP, a release/renew does NOTHING FOR YOU and that message (no adapter is in a state that is permissible for this operation) is normal.
Right. There's no IP to lease if you've got a static IP. Since you can ping 127.0.0.1, I'd guess that your static IP is just misconfigured before I'd guess that the stack is hosed. What are your settings in the TCP/IP properties for that connection? I'm wondering if maybe you've got the IP set to a broadcast or network address for the subnet mask you entered. Also, has this network adapter worked before? Could be some kind of device problem with the card.
 

Nerva

Platinum Member
Jul 26, 2005
2,784
0
0
Originally posted by: cleverhandle
Originally posted by: nweaver
if you are set to a static IP, a release/renew does NOTHING FOR YOU and that message (no adapter is in a state that is permissible for this operation) is normal.
Right. There's no IP to lease if you've got a static IP. Since you can ping 127.0.0.1, I'd guess that your static IP is just misconfigured before I'd guess that the stack is hosed. What are your settings in the TCP/IP properties for that connection? I'm wondering if maybe you've got the IP set to a broadcast or network address for the subnet mask you entered. Also, has this network adapter worked before? Could be some kind of device problem with the card.

you guys are awesome, though i wont be going into work until next monday again. if they still havent gotten it fixed, i will post screen shots and such