http://www.dslreports.com/forum/befsx41-Names-vs-local-IP-address-13522036 en Wed, 23 Mar 2022 18:16:10 EDT Wed, 23 Mar 2022 18:16:10 EDT http://www.dslreports.com/forum/Re-befsx41-Names-vs-local-IP-address-13573986 said by will792:

So many people in this forum recommend setting up static IP addresses but it is real pain of the neck to make changes whenever ISP switches DNS servers. It is so much easier to maintain locked DHCP entries (if this functionality is available of course).
I use static IP addresses on my internal network and on each workstation, I have assigned the DNS server to be the router (i.e. 192.168.1.1). My BEFSR41 V4 (and previously V2) seems to forward and return DNS requests/responses to each workstation without a problem.

I'm not sure if this is a BEFSR41 specific feature or not.]]> http://www.dslreports.com/forum/Re-befsx41-Names-vs-local-IP-address-13573986 Sat, 04 Jun 2005 07:59:43 EDT http://www.dslreports.com/forum/Re-befsx41-Names-vs-local-IP-address-13565585 said by will792:

So many people in this forum recommend setting up static IP addresses but it is real pain of the neck to make changes whenever ISP switches DNS servers. It is so much easier to maintain locked DHCP entries (if this functionality is available of course).
Hello fellow Connecticut resident!
(Stonington myself)
I'd take the static IP approach. Pain in the neck whenever the ISP changes DNS servers...but in reality that's such a rare case! Once every couple of years (perhaps your on DSL with SNET/SBC, yes they changed around a year ago with juggling stuff around after the Yahoo merger thing...but that's a rare thing).

Does the new 1.53 or so firmware for the sx41 add "reservations" to the DHCP service? I know Linksys has been rolling that out in newer firmwares, where you can set a fixed IP address bound to the MAC of your machines. That would solve your problem, you can leave rigs set to "Obtain Auto" so they pull info from the router (including current DNS)...yet still be static. I know the RV0 series of routers has that feature, I use it for a lot of clients so they can remote desktop from home.]]> http://www.dslreports.com/forum/Re-befsx41-Names-vs-local-IP-address-13565585 Fri, 03 Jun 2005 06:41:52 EDT http://www.dslreports.com/forum/Re-befsx41-Names-vs-local-IP-address-13545271
You can make your LAN IP's static by assigning them on each of your computers: Control Panel, Network Connections, Local Area Connection, Properties, Internet Protocol (TCP/IP): select "use the following ip address" and fill one in (for example: 192.168.1.2). Each computer must have a different address, of course. The subnet mask is always 255.255.255.0 and the gateway address for this example is 192.168.1.1.
--
Dan Tseng (WallWatcher author)]]> http://www.dslreports.com/forum/Re-befsx41-Names-vs-local-IP-address-13545271 Tue, 31 May 2005 23:19:00 EDT http://www.dslreports.com/forum/Re-befsx41-Names-vs-local-IP-address-13544807 http://www.dslreports.com/forum/Re-befsx41-Names-vs-local-IP-address-13544807 Tue, 31 May 2005 22:28:36 EDT http://www.dslreports.com/forum/Re-befsx41-Names-vs-local-IP-address-13542375
The HOSTS file is in C:\WINDOWS\system32\drivers\etc

Make a backup of it before making any changes. There's also an LMHOSTS file, but changing it didn't solve the problem.

You can edit the HOSTS file with Notepad. The last line is the only non-comment entry in the original HOSTS file. It says:

127.0.0.1 localhosts

You can add your own entries below it, one per line. Leave no spaces before the IP address, and at least one space between the address and the name. When done, save it back to disk, then see whether the "convert local" option in WallWatcher starts to work. Please post your results here.
--
Dan Tseng (WallWatcher author)]]> http://www.dslreports.com/forum/Re-befsx41-Names-vs-local-IP-address-13542375 Tue, 31 May 2005 17:42:18 EDT http://www.dslreports.com/forum/Re-befsx41-Names-vs-local-IP-address-13532111 http://www.dslreports.com/forum/Re-befsx41-Names-vs-local-IP-address-13532111 Mon, 30 May 2005 11:58:47 EDT http://www.dslreports.com/forum/Re-befsx41-Names-vs-local-IP-address-13531919
I also should have mentioned that WW's "use NetBios 137" option may not work with XP's Service Pack 2.
--
Dan Tseng (WallWatcher author)]]> http://www.dslreports.com/forum/Re-befsx41-Names-vs-local-IP-address-13531919 Mon, 30 May 2005 11:31:43 EDT http://www.dslreports.com/forum/Re-befsx41-Names-vs-local-IP-address-13531539 "Filters page" is now the "Restrict Access" page, each section in this page is mutually exclusive of the other parts....in some cases.
( long drawn out explanation to follow )
you can set the "Internet Access Policy:" name to anything you want ( as long as you remember what its for).
For the "PCs: [EDIT LIST] you need to include all the LAN subnet.
For the "Deny, Allow Internet access during selected days and hours" Allow ALL!!!
Now for the "Blocked Services"part of the "Restrict Access" page....click on Add/Edit Service button, (POPUP page) under " Service Name" call it "netbios", under "Protocol" select from the dropdown both "TCP/UDP", under "Port Range" enter 137-139 then click "Add" then click "Apply"......
now from the main "Restrict Access" page in the "Blocked Services"part use the pop-down to select the new "netbios" service you just created in the popup page..........

Remember to "Save Settings" at the bottom of the "Restrict Access" page

WOW I didnt think I'd get that out!!!.........I need a nap now.]]> http://www.dslreports.com/forum/Re-befsx41-Names-vs-local-IP-address-13531539 Mon, 30 May 2005 10:32:58 EDT http://www.dslreports.com/forum/Re-befsx41-Names-vs-local-IP-address-13530537
WallWatcher converts IP address to URL's (or names) by asking Windows to do it. When you select WW's "Convert local IP Addresses to Names" option, WW handles those conversions exactly the same way it handles remote IP conversions (by asking Windows to do it).

When using certain Firmware versions for the BEFSX41 (or BEFSR41), the router's DHCP table listed the names of all of my LAN stations. When using other Firmware versions, it never listed any of them.

When the router's DHCP table did list the names, WW's "Convert local" option displayed all the LAN names; when the router's DHCP table did NOT list the names, neither did WW, unless another WW option was used: "use NetBios 137" (on the LOGGING menu).

For security reasons, I normally don't use that option myself, and recommend that other people not use it, either: it can tell a remote hacker he's found a "live" computer. Of course, doing a DNS lookup of a computer within your own LAN does not expose you to that risk, so if you can restrict the lookup range to the LAN, you can use the feature safely.

One way to impose that LAN-only restriction is by using the "Filters" page in the Router: define a new service (let's call it "NetBios"), and have it cover the port range 136-139. Then, select it as a "deny / outbound" filter and give it a name ("NetBios" again). Once "Apply" has been clicked, and if you've done it properly, the router won't let NetBios requests get out to the 'net. LAN-LAN requests are not blocked, so it will be safe to let WW do NetBios lookups: the ones for remote addresses will be blocked.

Implementing the previous paragraph is even trickier than it may seem: you have to do things just right, and in the right sequence. Otherwise, you could wind up configuring the router to block ALL internet access from ALL your computers; or you could wind up without the NetBios filter you've tried to set, which will let those NetBios requests get out to the 'net.

Another drawback to using NetBios lookups is that they can take up to 65 seconds to fail (and they will fail, since you've told the router to block them). That can slow WW down under some circumstances.
--
Dan Tseng (WallWatcher author)]]> http://www.dslreports.com/forum/Re-befsx41-Names-vs-local-IP-address-13530537 Mon, 30 May 2005 04:27:49 EDT http://www.dslreports.com/forum/Re-WTR54G-after-mkt-firware-features-13524646 said by rkruz:

I dont plan on making them static.
Why not? If its your LAN at home...

Seems to be the simplest solution, requires no additional software or hardware, uses existing stuff...etc.
--
The funny thing about firemen...night and day they're always firemen]]> http://www.dslreports.com/forum/Re-WTR54G-after-mkt-firware-features-13524646 Sun, 29 May 2005 11:09:59 EDT http://www.dslreports.com/forum/Re-WTR54G-after-mkt-firware-features-13524212 http://www.dslreports.com/forum/Re-WTR54G-after-mkt-firware-features-13524212 Sun, 29 May 2005 09:36:52 EDT http://www.dslreports.com/forum/Re-WTR54G-after-mkt-firware-features-13523154 http://www.dslreports.com/forum/Re-WTR54G-after-mkt-firware-features-13523154 Sun, 29 May 2005 01:57:30 EDT http://www.dslreports.com/forum/Re-befsx41-Names-vs-local-IP-address-13522921 --
The funny thing about firemen...night and day they're always firemen]]> http://www.dslreports.com/forum/Re-befsx41-Names-vs-local-IP-address-13522921 Sun, 29 May 2005 01:05:54 EDT http://www.dslreports.com/forum/befsx41-Names-vs-local-IP-address-13522036
I am using a realvnc to monitor and control desktops on 3 other PCs and i have to find and enter the IP address each time. If there was a name, apparently it will display a choice. the VNC help suggested something about DNC but I didnt see that feature in the router setup.

I also use Wallwatcher, and its supposed to show names of local machines vs IP but I cant get it to do that either.
So im wondering if there is some routher setup thing I can do.

I have the latest firmware installed that is listed on the Linksys site.

thanks for any tips!]]> http://www.dslreports.com/forum/befsx41-Names-vs-local-IP-address-13522036 Sat, 28 May 2005 22:47:37 EDT