In reply to a post by amilod:

Dhcp was designed for home users, so no need to understand how a network works, it's all plug and play that's all a home user needs, no it dept I have ever worked in uses dhcp on there network.

I agree.

In reply to a post by amilod:

Anyone worth there salt would turn off dhcp, using fixed ip addresses is the only way a network should be controlled.

That is the most stupid thing I've read all week.

In reply to a post by Pipexer:

In reply to a post by amilod:

Anyone worth there salt would turn off dhcp, using fixed ip addresses is the only way a network should be controlled.

That is the most stupid thing I've read all week.

That's rude. What you have to remember is that there *is* no one person who is always right or always wrong. We're ALL human, and we all have differing experience and opinions.

Reacting in a gracious, humble way is the key to avoiding conflict. I detect a constant air of underlying resentment and arrogance on TBB, like a gun waiting to go off... on a hair trigger, should someone "dare" to challenge another's viewpoint.

I seem get the feeling that many die hard TBB members are late 30s, possibly even 40-60 years old, and really should know better than to act like squabbling children. I am 36, and I was pretty arrogant yesterday and said sorry for that, as it progresses NOTHING, except resentment and tension. Did I get anywhere by being rude? Of course I didn't, and annoyed many of you.

No one person is "Mr Right", and everyone else "Mr Wrong". Swallow your pride and be good folk. We're ALL sinners in God's eyes, and not one of us perfect.

Thank you for this forum, I love it.

Edited by glossywhite (Tue 21-Feb-12 02:08:10)

In reply to a post by amilod:

Anyone worth there salt would turn off dhcp, using fixed ip addresses is the only way a network should be controlled.

Is it? What could be simpler for a home user with a typical compliment of computers then to let DHCP assign its IPs automatically. No need to bother about ascertaining the various MACs and reserving them, and having to dream up new ones every time someone with smart phone, eReader or other handheld device walks into the house. Why make work for yourself unless you have exceptional requirements for your network?

It's so obvious that the DHCP inventors had to invent it.

So how much salt are you worth, if we are not?

In reply to a post by Pipexer:

In reply to a post by amilod:

Anyone worth there salt would turn off dhcp, using fixed ip addresses is the only way a network should be controlled.

That is the most stupid thing I've read all week.

That�s just what I would have expected to hear from a home user. Ah well it takes all sorts. Bless your cotton socks.

In reply to a post by XRaySpeX:

In reply to a post by amilod:

Anyone worth there salt would turn off dhcp, using fixed ip addresses is the only way a network should be controlled.

Is it? What could be simpler for a home user with a typical compliment of computers then to let DHCP assign its IPs automatically. No need to bother about ascertaining the various MACs and reserving them, and having to dream up new ones every time someone with smart phone, eReader or other handheld device walks into the house. Why make work for yourself unless you have exceptional requirements for your network?

It's so obvious that the DHCP inventors had to invent it.

So how much salt are you worth, if we are not?

If I remember correctly you guys were moaning about the dhcp on the box, you appeared to be intelligent folk who knew what they were doing, so it would be obvious to me that you would not use dhcp, and structure your network in such a way that you would know which equipment is on what address.

In reply to a post by XRaySpeX:

In reply to a post by amilod:

Anyone worth there salt would turn off dhcp, using fixed ip addresses is the only way a network should be controlled.

Is it? What could be simpler for a home user with a typical compliment of computers then to let DHCP assign its IPs automatically. No need to bother about ascertaining the various MACs and reserving them, and having to dream up new ones every time someone with smart phone, eReader or other handheld device walks into the house. Why make work for yourself unless you have exceptional requirements for your network?

It's so obvious that the DHCP inventors had to invent it.

So how much salt are you worth, if we are not?

I like to take a comprimise approach :-
Reserved IP addresses for PCs and Wireless Printers router assigned IP Addresses for the other devices like "guest PCs", games consoles, smart phone tablets etc.

Reserving IP addresses and setting them up in your hosts file prevents the PC searching the internet for your other devices.

For example one of my (old) XP PCs has the machine name "Athalon" and I share our laser jet printer from this. Before I set up reserved ip address I have seen my wife's vista PC struggling to connect to the shared printer, doing a tracert shown that it is trying to reach a machine with an ip address outside our network (i.e. on the internet).

You might argue that it's my non-unique name which is making the problem worse, but how many PCs are there out there which have been set up by the Windoww 7 networking wizard where the first user is "John" and the machine name is "John-PC". If John want to share his printer there is a strong chance that other family members PCs are going to reach out to the internet when printing, especially if John's PC happens to be off at the time of printing.

In reply to a post by Mike_Williams:

In reply to a post by XRaySpeX:

In reply to a post by amilod:

Anyone worth there salt would turn off dhcp, using fixed ip addresses is the only way a network should be controlled.

Is it? What could be simpler for a home user with a typical compliment of computers then to let DHCP assign its IPs automatically. No need to bother about ascertaining the various MACs and reserving them, and having to dream up new ones every time someone with smart phone, eReader or other handheld device walks into the house. Why make work for yourself unless you have exceptional requirements for your network?

It's so obvious that the DHCP inventors had to invent it.

So how much salt are you worth, if we are not?

I like to take a comprimise approach :-
Reserved IP addresses for PCs and Wireless Printers router assigned IP Addresses for the other devices like "guest PCs", games consoles, smart phone tablets etc.

Reserving IP addresses and setting them up in your hosts file prevents the PC searching the internet for your other devices.

For example one of my (old) XP PCs has the machine name "Athalon" and I share our laser jet printer from this. Before I set up reserved ip address I have seen my wife's vista PC struggling to connect to the shared printer, doing a tracert shown that it is trying to reach a machine with an ip address outside our network (i.e. on the internet).

You might argue that it's my non-unique name which is making the problem worse, but how many PCs are there out there which have been set up by the Windoww 7 networking wizard where the first user is "John" and the machine name is "John-PC". If John want to share his printer there is a strong chance that other family members PCs are going to reach out to the internet when printing, especially if John's PC happens to be off at the time of printing.

I always find that manually configuring the pc to print to the shared printer located on another pc to be the best option.
I always tell my business customers not to scrimp on a printer if it is to be used by more than one PC, always buy a network printer, this will stop any problems from occurring. Especially if you are trying to print from a 64bit win 7 pc to a 32 bit XP machine/printer.

In reply to a post by XRaySpeX:

So how much salt are you worth, if we are not?

He/she is just trolling, anyone with any grain of common sense, let alone experience administering networks of more than 10 computers, let alone 1000, knows that you don't go round configuring all those clients with static IP addresses and assocuated settings, nor expect guests with non-managed devices to crack open TCP/IP settings, check with the network administrator for a free IP, and enter that in. Completely putting aside the fact DHCP is required for other important network services to be able to function properly.

Edited by Pipexer (Tue 21-Feb-12 18:17:59)

I don't see how this could be, because if you are in a workgroup and are connecting to "John-PC" then this is single label name and windows will use NetBIOS (broadcast) or LLMNR to resolve the hostname. This would not go out through the default gateway. Also, the Windows Firewall would not be configured to allow file and print sharing out of the local subnet.

Edited by Pipexer (Tue 21-Feb-12 18:27:11)