WINs/DNS on Edge Router
-
@fuznutz04 said in WINs/DNS on Edge Router:
@scottalanmiller said in WINs/DNS on Edge Router:
@fuznutz04 said in WINs/DNS on Edge Router:
@Dashrender said in WINs/DNS on Edge Router:
WINS eh? I seriously doubt it.
You have apps that are still relying on NetBIOS for something? Can't solve this with DNS?
It's a copier that is trying to access by computer name. I guess a simple solutions would just be to change the copier to use IPs instead.
The copier is trying to use NetBIOS instead of DNS? Are you positive? That's so incredibly unlikely, I've never heard of that scenario before.
The copier was set to use \computername\scan as a location to send files for the "scan to PC" function. It wasn't resolving properly after I installed the ERL.
What was doing DNS resolution before the ERL? I'm guessing it was using broadcasting, though I don't know why the ERL would stop that part from working.
-
@Dashrender said in WINs/DNS on Edge Router:
@fuznutz04 said in WINs/DNS on Edge Router:
@scottalanmiller said in WINs/DNS on Edge Router:
@fuznutz04 said in WINs/DNS on Edge Router:
@Dashrender said in WINs/DNS on Edge Router:
WINS eh? I seriously doubt it.
You have apps that are still relying on NetBIOS for something? Can't solve this with DNS?
It's a copier that is trying to access by computer name. I guess a simple solutions would just be to change the copier to use IPs instead.
The copier is trying to use NetBIOS instead of DNS? Are you positive? That's so incredibly unlikely, I've never heard of that scenario before.
The copier was set to use \computername\scan as a location to send files for the "scan to PC" function. It wasn't resolving properly after I installed the ERL.
What was doing DNS resolution before the ERL? I'm guessing it was using broadcasting, though I don't know why the ERL would stop that part from working.
The only thing in place prior to the ERL was the Comcast gateway device which was also handing out DHCP to the internal LAN.
-
@Dashrender said in WINs/DNS on Edge Router:
@fuznutz04 said in WINs/DNS on Edge Router:
@scottalanmiller said in WINs/DNS on Edge Router:
@fuznutz04 said in WINs/DNS on Edge Router:
@Dashrender said in WINs/DNS on Edge Router:
WINS eh? I seriously doubt it.
You have apps that are still relying on NetBIOS for something? Can't solve this with DNS?
It's a copier that is trying to access by computer name. I guess a simple solutions would just be to change the copier to use IPs instead.
The copier is trying to use NetBIOS instead of DNS? Are you positive? That's so incredibly unlikely, I've never heard of that scenario before.
The copier was set to use \computername\scan as a location to send files for the "scan to PC" function. It wasn't resolving properly after I installed the ERL.
What was doing DNS resolution before the ERL? I'm guessing it was using broadcasting, though I don't know why the ERL would stop that part from working.
The ERL would stop that part from working quickly because prior to 1.9.0 and the use of dnsmasq, the ERL would often not know about DNS names for the things it assigned. Mostly it was a problem with static reservations I believe.
-
WINS? Most likely you just need to setup the DNS Search Names/Space but in a workgroup any computer can become the master browser
-
@fuznutz04 said in WINs/DNS on Edge Router:
@scottalanmiller said in WINs/DNS on Edge Router:
@fuznutz04 said in WINs/DNS on Edge Router:
@Dashrender said in WINs/DNS on Edge Router:
WINS eh? I seriously doubt it.
You have apps that are still relying on NetBIOS for something? Can't solve this with DNS?
It's a copier that is trying to access by computer name. I guess a simple solutions would just be to change the copier to use IPs instead.
The copier is trying to use NetBIOS instead of DNS? Are you positive? That's so incredibly unlikely, I've never heard of that scenario before.
The copier was set to use \\computername\scan as a location to send files for the "scan to PC" function. It wasn't resolving properly after I installed the ERL.
While that is NetBIOS notation, it's also what Windows uses when going to DNS. So that doesn't itself give you any reason to suspect NetBIOS. Check DNS first.
-
@scottalanmiller said in WINs/DNS on Edge Router:
@fuznutz04 said in WINs/DNS on Edge Router:
@scottalanmiller said in WINs/DNS on Edge Router:
@fuznutz04 said in WINs/DNS on Edge Router:
@Dashrender said in WINs/DNS on Edge Router:
WINS eh? I seriously doubt it.
You have apps that are still relying on NetBIOS for something? Can't solve this with DNS?
It's a copier that is trying to access by computer name. I guess a simple solutions would just be to change the copier to use IPs instead.
The copier is trying to use NetBIOS instead of DNS? Are you positive? That's so incredibly unlikely, I've never heard of that scenario before.
The copier was set to use \\computername\scan as a location to send files for the "scan to PC" function. It wasn't resolving properly after I installed the ERL.
While that is NetBIOS notation, it's also what Windows uses when going to DNS. So that doesn't itself give you any reason to suspect NetBIOS. Check DNS first.
or you can try \\computername.domain.tld\ but, when using just the hosts you need either DNS search setup to append the domain name (likely if you add a domain name to the TCP/IP settings in the copier it will do this) or you need a computer acting as the WINs master browser but that's depreciated.
-
I will still need to put in static entries, even though I enable this ?
set service dhcp-server use-dnsmasq enable -
@fuznutz04 said in WINs/DNS on Edge Router:
I will still need to put in static entries, even though I enable this ?
set service dhcp-server use-dnsmasq enableIf they are in the DHCP of the router, you should not.
Everything may need rebooted though
-
Excellent. So then the only entries needed would be any device that has a static IP address.
EdgeOS is getting better all the time.
-
@fuznutz04 said in WINs/DNS on Edge Router:
Excellent. So then the only entries needed would be any device that has a static IP address.
Yes.
EdgeOS is getting better all the time.
Yes.
