Stupid networking tricks
-
DNS Cache?
Henry Minute Do not read medical books! You could die of a misprint. - Mark Twain Girl: (staring) "Why do you need an icy cucumber?" “I want to report a fraud. The government is lying to us all.” I wouldn't let CG touch my Abacus! When you're wrestling a gorilla, you don't stop when you're tired, you stop when the gorilla is.
It's a simply workgroup network - no DNS servers involved...
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997 -
So when I moved, I had to change ISPs, which meant configuring a new router. To begin with, the cable modem povided by Time-Warner doesn't let you change ANYTHING with regards to how the modem works, so that required me to buy a Motorola Surfboard modem at BestBuy (I couldn't afford the time for it to be shipped from anywhere). My router is a DHCP server, and it allows you to reserve IPs based on MAC addresses so that each machine gets the same IP address whenever the power is cycled on the router (which could happen at any time because of the occasional power outage), resulting in a renewed DHCP lease for all attached devices. I had also set this up on my previous router, but since I had to completely re-do it, I figured I'd re-organize the IPs. This meant that ALL of the machines that had dynamic IPs assigned would get new IPs. So far so good - even after doing this, the previously configured shares seemed to work fine, all machines could access the internet, and I could ping all of the newly assigned IPs. Yesterday morning, I tried to terminal service into one of the boxes by using its machine name, and it couldn't connect. I puzzled over this for most of the day, and fxed it last night when I had a thought about what might be the problem. To make this a bit more interesting, I leave it to you to deduce the problem. the first person that gueses what was wrong gets a 5.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997You had a DNS suffix setup on the router, so your DHCP clients had something in the "Connection-specific DNS Suffix" field when you ran ipconfig. Could also be called domain name or something like that in the router config.
-
So when I moved, I had to change ISPs, which meant configuring a new router. To begin with, the cable modem povided by Time-Warner doesn't let you change ANYTHING with regards to how the modem works, so that required me to buy a Motorola Surfboard modem at BestBuy (I couldn't afford the time for it to be shipped from anywhere). My router is a DHCP server, and it allows you to reserve IPs based on MAC addresses so that each machine gets the same IP address whenever the power is cycled on the router (which could happen at any time because of the occasional power outage), resulting in a renewed DHCP lease for all attached devices. I had also set this up on my previous router, but since I had to completely re-do it, I figured I'd re-organize the IPs. This meant that ALL of the machines that had dynamic IPs assigned would get new IPs. So far so good - even after doing this, the previously configured shares seemed to work fine, all machines could access the internet, and I could ping all of the newly assigned IPs. Yesterday morning, I tried to terminal service into one of the boxes by using its machine name, and it couldn't connect. I puzzled over this for most of the day, and fxed it last night when I had a thought about what might be the problem. To make this a bit more interesting, I leave it to you to deduce the problem. the first person that gueses what was wrong gets a 5.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997 -
There was a .45in hole in the front of it with a 3in hole in the back?
Brad Deja Moo - When you feel like you've heard the same bull before.
The tactical situation had not degraded to the point that gun-play was called for. :)
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997 -
You had a DNS suffix setup on the router, so your DHCP clients had something in the "Connection-specific DNS Suffix" field when you ran ipconfig. Could also be called domain name or something like that in the router config.
Nope. But thanks for playing, and feel free to try again.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997 -
So when I moved, I had to change ISPs, which meant configuring a new router. To begin with, the cable modem povided by Time-Warner doesn't let you change ANYTHING with regards to how the modem works, so that required me to buy a Motorola Surfboard modem at BestBuy (I couldn't afford the time for it to be shipped from anywhere). My router is a DHCP server, and it allows you to reserve IPs based on MAC addresses so that each machine gets the same IP address whenever the power is cycled on the router (which could happen at any time because of the occasional power outage), resulting in a renewed DHCP lease for all attached devices. I had also set this up on my previous router, but since I had to completely re-do it, I figured I'd re-organize the IPs. This meant that ALL of the machines that had dynamic IPs assigned would get new IPs. So far so good - even after doing this, the previously configured shares seemed to work fine, all machines could access the internet, and I could ping all of the newly assigned IPs. Yesterday morning, I tried to terminal service into one of the boxes by using its machine name, and it couldn't connect. I puzzled over this for most of the day, and fxed it last night when I had a thought about what might be the problem. To make this a bit more interesting, I leave it to you to deduce the problem. the first person that gueses what was wrong gets a 5.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997John Simmons / outlaw programmer wrote:
I tried to terminal service into one of the boxes by using its machine name, and it couldn't connect. I puzzled over this for most of the day, and fxed it last night when I had a thought about what might be the problem.
The box in question was turned off?
Just along for the ride. "the meat from that butcher is just the dogs danglies, absolutely amazing cuts of beef." - DaveAuld (2011)
"No, that is just the earthly manifestation of the Great God Retardon." - Nagy Vilmos (2011) -
So when I moved, I had to change ISPs, which meant configuring a new router. To begin with, the cable modem povided by Time-Warner doesn't let you change ANYTHING with regards to how the modem works, so that required me to buy a Motorola Surfboard modem at BestBuy (I couldn't afford the time for it to be shipped from anywhere). My router is a DHCP server, and it allows you to reserve IPs based on MAC addresses so that each machine gets the same IP address whenever the power is cycled on the router (which could happen at any time because of the occasional power outage), resulting in a renewed DHCP lease for all attached devices. I had also set this up on my previous router, but since I had to completely re-do it, I figured I'd re-organize the IPs. This meant that ALL of the machines that had dynamic IPs assigned would get new IPs. So far so good - even after doing this, the previously configured shares seemed to work fine, all machines could access the internet, and I could ping all of the newly assigned IPs. Yesterday morning, I tried to terminal service into one of the boxes by using its machine name, and it couldn't connect. I puzzled over this for most of the day, and fxed it last night when I had a thought about what might be the problem. To make this a bit more interesting, I leave it to you to deduce the problem. the first person that gueses what was wrong gets a 5.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997Was it you had manually set the hostname in the HOSTS file, but didn't update file(s) when you did the rejig?
-
John Simmons / outlaw programmer wrote:
I tried to terminal service into one of the boxes by using its machine name, and it couldn't connect. I puzzled over this for most of the day, and fxed it last night when I had a thought about what might be the problem.
The box in question was turned off?
Just along for the ride. "the meat from that butcher is just the dogs danglies, absolutely amazing cuts of beef." - DaveAuld (2011)
"No, that is just the earthly manifestation of the Great God Retardon." - Nagy Vilmos (2011)Nope - all of the machines were turned on at the time.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997 -
Was it you had manually set the hostname in the HOSTS file, but didn't update file(s) when you did the rejig?
This is the correct answer. The IPs no longer matched what was listed in the HOSTS file.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997 -
Was it you had manually set the hostname in the HOSTS file, but didn't update file(s) when you did the rejig?
Ah, you just beat me to it...
- Anders
-
This is the correct answer. The IPs no longer matched what was listed in the HOSTS file.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997The reason I guessed it was this is simple, I have done it before. :doh:
-
Was it you had manually set the hostname in the HOSTS file, but didn't update file(s) when you did the rejig?
-
I use the HOSTS file to prevent the prowser from visitng web sites (ads, etc) that could introdece problems on my systems. When a url in the file is found on a web page, my browser displays a hazardous waste logo where the ad would have shown up.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997 -
I use the HOSTS file to prevent the prowser from visitng web sites (ads, etc) that could introdece problems on my systems. When a url in the file is found on a web page, my browser displays a hazardous waste logo where the ad would have shown up.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997Interesting approach. That is actually quite a good use of it, a kind of client side blacklist. I have also had to put things in the HOSTS file, as you must have done to cause this problem, to get some Windows networking stuff to operate correctly. I'm sure it shouldn't be necessary but Windows networking seems to be quite fragile, to the extent that sometimes I either email files to myself to transfer them, or host them on a local HTTP server and fetch them. TCP and DNS often work even when net view etc don't.
-
I use the HOSTS file to prevent the prowser from visitng web sites (ads, etc) that could introdece problems on my systems. When a url in the file is found on a web page, my browser displays a hazardous waste logo where the ad would have shown up.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997I've got hundreds of entries in my HOSTS file for just this purpose. How, then, did it affect your LAN?
"One man's wage rise is another man's price increase." - Harold Wilson
"Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons
"Show me a community that obeys the Ten Commandments and I'll show you a less crowded prison system." - Anonymous
-
I've got hundreds of entries in my HOSTS file for just this purpose. How, then, did it affect your LAN?
"One man's wage rise is another man's price increase." - Harold Wilson
"Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons
"Show me a community that obeys the Ten Commandments and I'll show you a less crowded prison system." - Anonymous
The IPs didn't match, and it looks like Terminal Services uses what's in the HOSTS file to resolve machine names to IP addresses. If there's nothing in the hosts file, I assume that it just looks for the machine name on the network. Since the IPs were wrong in the file, it couldn't connect to the specified machine name.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997 -
Interesting approach. That is actually quite a good use of it, a kind of client side blacklist. I have also had to put things in the HOSTS file, as you must have done to cause this problem, to get some Windows networking stuff to operate correctly. I'm sure it shouldn't be necessary but Windows networking seems to be quite fragile, to the extent that sometimes I either email files to myself to transfer them, or host them on a local HTTP server and fetch them. TCP and DNS often work even when net view etc don't.
My most annoying issue right now is that no matter what I do, some of the machines on the LAN can't map remote shares when I reboot the machine. If I go into Explorer and click on the share, it searhes for it and finds it, and then everything is good. (All machines are running the same version of windows 7 and are caught up on the latest patches.)
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997 -
This is the correct answer. The IPs no longer matched what was listed in the HOSTS file.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997Why on earth are you manually entering hostnames in HOSTS? Built-in name resolution protocols not fancy enough for you? lol.
-
Why on earth are you manually entering hostnames in HOSTS? Built-in name resolution protocols not fancy enough for you? lol.
I don't remember why I was doing it...
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997