netbios and sql replication

If i have netbios enabled on the distributor is there any way to make it
not request netbios information to the subscriber? I have the
subscriber in the host file and in the client network utility. That
should halt nebios request, but it doesn't. The subscriber keeps seeing
netbios request coming from our distributor?
Would adding the subscriber to the lmhost help more then adding it to
the host?
thanks,
comb
probably not. Hostname resolution goes through a hierarchy trying to resolve
the hostname, sometimes Netbios cache, WINS server first, broadcast,
lmhosts, hosts, DNS, sometimes DNS (if the host name has a . in it) first.
It depends on a variety of settings.
Why is this important to you. Once the server knows about a name it caches
it and doesn't do the lookup again.
"combfilter" <asdf@.adsf.com> wrote in message
news:MPG.1cc9e0a2c18ba491989680@.news.newsreader.co m...
> If i have netbios enabled on the distributor is there any way to make it
> not request netbios information to the subscriber? I have the
> subscriber in the host file and in the client network utility. That
> should halt nebios request, but it doesn't. The subscriber keeps seeing
> netbios request coming from our distributor?
> Would adding the subscriber to the lmhost help more then adding it to
> the host?
> thanks,
> comb
|||Our subscriber is complaining about netbios request from our distributor
in their firewall logs.
The subscriber is in the host file so our machine shouldn't even need to
do a netbios request. However, for some reason it is. Also, the host
file does work. I can make changes to it and they take place
immediatly.
Mostly I just want to stop it to make the subscriber happy.
In article <#nf51xfQFHA.3704@.TK2MSFTNGP12.phx.gbl>,
hilary.cotter@.gmail.com says...
> probably not. Hostname resolution goes through a hierarchy trying to resolve
> the hostname, sometimes Netbios cache, WINS server first, broadcast,
> lmhosts, hosts, DNS, sometimes DNS (if the host name has a . in it) first.
> It depends on a variety of settings.
> Why is this important to you. Once the server knows about a name it caches
> it and doesn't do the lookup again.
> "combfilter" <asdf@.adsf.com> wrote in message
> news:MPG.1cc9e0a2c18ba491989680@.news.newsreader.co m...
>
>
sql

Net Protocols - what if none are enabled?

Hopefully there's some SQL architect gurus reading...
I have a couple servers where none of the Net Protocols are enabled. I'm
not sure how they ended up that way. Usually we have at (default?) for
TCP/IP then Named Pipes, we have no need for other net protocols. However,
our apps and services are still able make SQL connections.
I'm verifying this via the SQL Network Client Utility. What else can
determine or configure Network Libraries? And what impacts might this have
on connectivity with no protocols enabled?
Thanks,
ThuanAre you saying that you use Client Network Utility on the server machine and
in the Client Network
Utility on the server machine not netlibs are enabled? You should be using S
erver Network Utility on
the server machine.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Thuan" <Thuan@.discussions.microsoft.com> wrote in message
news:1B4C234A-B5C8-474C-92A5-DB071BB530D3@.microsoft.com...
> Hopefully there's some SQL architect gurus reading...
> I have a couple servers where none of the Net Protocols are enabled. I'm
> not sure how they ended up that way. Usually we have at (default?) for
> TCP/IP then Named Pipes, we have no need for other net protocols. However
,
> our apps and services are still able make SQL connections.
> I'm verifying this via the SQL Network Client Utility. What else can
> determine or configure Network Libraries? And what impacts might this hav
e
> on connectivity with no protocols enabled?
> Thanks,
> Thuan|||Hi
If this is an MSDE instance then network access is not enabled by default on
the server. You should check out the Server Network Utility to see if
clients can connect and on each client check the Client Network Utility.
Enabling the protocols in the Client Network Utility will only affect the
client applications on the server.
John
"Thuan" <Thuan@.discussions.microsoft.com> wrote in message
news:1B4C234A-B5C8-474C-92A5-DB071BB530D3@.microsoft.com...
> Hopefully there's some SQL architect gurus reading...
> I have a couple servers where none of the Net Protocols are enabled. I'm
> not sure how they ended up that way. Usually we have at (default?) for
> TCP/IP then Named Pipes, we have no need for other net protocols.
> However,
> our apps and services are still able make SQL connections.
> I'm verifying this via the SQL Network Client Utility. What else can
> determine or configure Network Libraries? And what impacts might this
> have
> on connectivity with no protocols enabled?
> Thanks,
> Thuan

Net Protocols - what if none are enabled?

Hopefully there's some SQL architect gurus reading...
I have a couple servers where none of the Net Protocols are enabled. I'm
not sure how they ended up that way. Usually we have at (default?) for
TCP/IP then Named Pipes, we have no need for other net protocols. However,
our apps and services are still able make SQL connections.
I'm verifying this via the SQL Network Client Utility. What else can
determine or configure Network Libraries? And what impacts might this have
on connectivity with no protocols enabled?
Thanks,
ThuanAre you saying that you use Client Network Utility on the server machine and in the Client Network
Utility on the server machine not netlibs are enabled? You should be using Server Network Utility on
the server machine.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Thuan" <Thuan@.discussions.microsoft.com> wrote in message
news:1B4C234A-B5C8-474C-92A5-DB071BB530D3@.microsoft.com...
> Hopefully there's some SQL architect gurus reading...
> I have a couple servers where none of the Net Protocols are enabled. I'm
> not sure how they ended up that way. Usually we have at (default?) for
> TCP/IP then Named Pipes, we have no need for other net protocols. However,
> our apps and services are still able make SQL connections.
> I'm verifying this via the SQL Network Client Utility. What else can
> determine or configure Network Libraries? And what impacts might this have
> on connectivity with no protocols enabled?
> Thanks,
> Thuan|||Hi
If this is an MSDE instance then network access is not enabled by default on
the server. You should check out the Server Network Utility to see if
clients can connect and on each client check the Client Network Utility.
Enabling the protocols in the Client Network Utility will only affect the
client applications on the server.
John
"Thuan" <Thuan@.discussions.microsoft.com> wrote in message
news:1B4C234A-B5C8-474C-92A5-DB071BB530D3@.microsoft.com...
> Hopefully there's some SQL architect gurus reading...
> I have a couple servers where none of the Net Protocols are enabled. I'm
> not sure how they ended up that way. Usually we have at (default?) for
> TCP/IP then Named Pipes, we have no need for other net protocols.
> However,
> our apps and services are still able make SQL connections.
> I'm verifying this via the SQL Network Client Utility. What else can
> determine or configure Network Libraries? And what impacts might this
> have
> on connectivity with no protocols enabled?
> Thanks,
> Thuansql