Networking Forums  

Go Back   Networking Forums > Networking Newsgroups > Windows Server Networking

Wins.dll is not recognized as a parser in netmon

Reply
 
Thread Tools Display Modes
  #1  
Old 01-25-2007, 09:21 PM
Default Wins.dll is not recognized as a parser in netmon



I am trying to research a wins error 4102, and I can not find anything to
help me resolve the issue.

I do have 2 wins servers that are located at 2 diffrent sites and are
confugured as wins servers push/pull. These 2 servers seem to replicate fine
when I manully request replication. And the data in the 2 servers is
accurate. My concerne is there is a rogue winserver some where that is
generating this error.
Both Servers are 2003 SP1

I have done the following

1. Make sure the all WINS servers are configured correctly such as from
either Pull only or Push only, to Push/Pull. If you configure WINS A to
perform pull replications with WINS B, make sure it is a push partner of WINS
B.

2. If the other WINS server is located across a router, check for network
connectivity to the remote WINS server.

3. If the WINS is running on a multihomed server or RRAS server , you may
want to setup WINS to replicate with any partner. Neither are RRAS servers so
not applicable

4. You may want to run a Network Monitor trace, and then identify the remote
WINS server (Pull partner) that sends the "WINS: Stop Reason = Message Error"
error message.

The problem with number 4 is I downloaded the 2003 tools to obtain the
Wins.dll
I have completed the following.
Open Tcpip.ini in the Netmon\Parsers subdirectory.
Add "42 = WINS" to the [TCP_HandoffSet] section of the file, as in the
following example:
[TCP_HandoffSet]
20 = FTP
21 = FTP
23 = TELNET
25 = SMTP
42 = WINS
53 = DNS

Save and close Tcpip.ini.
Open Parser.ini in the Netmon subdirectory.
Add "WINS.DLL = 0: WINS" to the [PARSERS] section of the file, as in the
following example:
[PARSERS]
FRAME.DLL = 0: FRAME
MAC.DLL = 0: ETHERNET, TOKENRING, FDDI, TMAC, SMT
LLC.DLL = 0: LLC, RPL, SNAP, BPDU
NETBIOS.DLL = 0: NETBIOS
SMB.DLL = 0: SMB
....
WINS.DLL = 0: WINS

Add the following section to the end of Parser.ini.
[WINS]
Comment = "WINS Server Replication"
FollowSet =
HelpFile =

Save and close Parser.ini.

And I have copied the Wins.dll into the parsers folder.

Yet when I run network monitor wins does show up as a parser to filter on.
and I am not seeing wins entries in the capture.



Schuml
Reply With Quote
  #2  
Old 01-26-2007, 04:26 AM
JohnGil (MSFT)
Guest
 
Posts: n/a
Default RE: Wins.dll is not recognized as a parser in netmon

Netmon 3 is released. The WINS parser is built in. You can get it at:

https://connect.microsoft.com/Downlo...spx?SiteID=216

"Schuml" wrote:

> I am trying to research a wins error 4102, and I can not find anything to
> help me resolve the issue.
>
> I do have 2 wins servers that are located at 2 diffrent sites and are
> confugured as wins servers push/pull. These 2 servers seem to replicate fine
> when I manully request replication. And the data in the 2 servers is
> accurate. My concerne is there is a rogue winserver some where that is
> generating this error.
> Both Servers are 2003 SP1
>
> I have done the following
>
> 1. Make sure the all WINS servers are configured correctly such as from
> either Pull only or Push only, to Push/Pull. If you configure WINS A to
> perform pull replications with WINS B, make sure it is a push partner of WINS
> B.
>
> 2. If the other WINS server is located across a router, check for network
> connectivity to the remote WINS server.
>
> 3. If the WINS is running on a multihomed server or RRAS server , you may
> want to setup WINS to replicate with any partner. Neither are RRAS servers so
> not applicable
>
> 4. You may want to run a Network Monitor trace, and then identify the remote
> WINS server (Pull partner) that sends the "WINS: Stop Reason = Message Error"
> error message.
>
> The problem with number 4 is I downloaded the 2003 tools to obtain the
> Wins.dll
> I have completed the following.
> Open Tcpip.ini in the Netmon\Parsers subdirectory.
> Add "42 = WINS" to the [TCP_HandoffSet] section of the file, as in the
> following example:
> [TCP_HandoffSet]
> 20 = FTP
> 21 = FTP
> 23 = TELNET
> 25 = SMTP
> 42 = WINS
> 53 = DNS
>
> Save and close Tcpip.ini.
> Open Parser.ini in the Netmon subdirectory.
> Add "WINS.DLL = 0: WINS" to the [PARSERS] section of the file, as in the
> following example:
> [PARSERS]
> FRAME.DLL = 0: FRAME
> MAC.DLL = 0: ETHERNET, TOKENRING, FDDI, TMAC, SMT
> LLC.DLL = 0: LLC, RPL, SNAP, BPDU
> NETBIOS.DLL = 0: NETBIOS
> SMB.DLL = 0: SMB
> ...
> WINS.DLL = 0: WINS
>
> Add the following section to the end of Parser.ini.
> [WINS]
> Comment = "WINS Server Replication"
> FollowSet =
> HelpFile =
>
> Save and close Parser.ini.
>
> And I have copied the Wins.dll into the parsers folder.
>
> Yet when I run network monitor wins does show up as a parser to filter on.
> and I am not seeing wins entries in the capture.
>

Reply With Quote
  #3  
Old 01-26-2007, 07:12 PM
Schuml
Guest
 
Posts: n/a
Default RE: Wins.dll is not recognized as a parser in netmon

Thanks John;

The Site mentioned did not work however you can download netmon 3.0

Go to http://connect.microsoft.com

Sign in with your passport account.

Choose "Available Connections" on the left.

Choose "Apply" for Network Monitor 3.0 (once you've finished with the
application, the selection appears in your "My Participation" page).

Go to the Downloads page (On the left side), and select the appropriate
build 32 or 64 bit build.

But I still dont see a wins parser included


"JohnGil (MSFT)" wrote:

> Netmon 3 is released. The WINS parser is built in. You can get it at:
>
> https://connect.microsoft.com/Downlo...spx?SiteID=216
>
> "Schuml" wrote:
>
> > I am trying to research a wins error 4102, and I can not find anything to
> > help me resolve the issue.
> >
> > I do have 2 wins servers that are located at 2 diffrent sites and are
> > confugured as wins servers push/pull. These 2 servers seem to replicate fine
> > when I manully request replication. And the data in the 2 servers is
> > accurate. My concerne is there is a rogue winserver some where that is
> > generating this error.
> > Both Servers are 2003 SP1
> >
> > I have done the following
> >
> > 1. Make sure the all WINS servers are configured correctly such as from
> > either Pull only or Push only, to Push/Pull. If you configure WINS A to
> > perform pull replications with WINS B, make sure it is a push partner of WINS
> > B.
> >
> > 2. If the other WINS server is located across a router, check for network
> > connectivity to the remote WINS server.
> >
> > 3. If the WINS is running on a multihomed server or RRAS server , you may
> > want to setup WINS to replicate with any partner. Neither are RRAS servers so
> > not applicable
> >
> > 4. You may want to run a Network Monitor trace, and then identify the remote
> > WINS server (Pull partner) that sends the "WINS: Stop Reason = Message Error"
> > error message.
> >
> > The problem with number 4 is I downloaded the 2003 tools to obtain the
> > Wins.dll
> > I have completed the following.
> > Open Tcpip.ini in the Netmon\Parsers subdirectory.
> > Add "42 = WINS" to the [TCP_HandoffSet] section of the file, as in the
> > following example:
> > [TCP_HandoffSet]
> > 20 = FTP
> > 21 = FTP
> > 23 = TELNET
> > 25 = SMTP
> > 42 = WINS
> > 53 = DNS
> >
> > Save and close Tcpip.ini.
> > Open Parser.ini in the Netmon subdirectory.
> > Add "WINS.DLL = 0: WINS" to the [PARSERS] section of the file, as in the
> > following example:
> > [PARSERS]
> > FRAME.DLL = 0: FRAME
> > MAC.DLL = 0: ETHERNET, TOKENRING, FDDI, TMAC, SMT
> > LLC.DLL = 0: LLC, RPL, SNAP, BPDU
> > NETBIOS.DLL = 0: NETBIOS
> > SMB.DLL = 0: SMB
> > ...
> > WINS.DLL = 0: WINS
> >
> > Add the following section to the end of Parser.ini.
> > [WINS]
> > Comment = "WINS Server Replication"
> > FollowSet =
> > HelpFile =
> >
> > Save and close Parser.ini.
> >
> > And I have copied the Wins.dll into the parsers folder.
> >
> > Yet when I run network monitor wins does show up as a parser to filter on.
> > and I am not seeing wins entries in the capture.
> >

Reply With Quote
  #4  
Old 01-26-2007, 10:43 PM
JohnGil (MSFT)
Guest
 
Posts: n/a
Default RE: Wins.dll is not recognized as a parser in netmon

It's called NBTNS for NetBIOS over TCP Name Server or something like that.

"Schuml" wrote:

> Thanks John;
>
> The Site mentioned did not work however you can download netmon 3.0
>
> Go to http://connect.microsoft.com
>
> Sign in with your passport account.
>
> Choose "Available Connections" on the left.
>
> Choose "Apply" for Network Monitor 3.0 (once you've finished with the
> application, the selection appears in your "My Participation" page).
>
> Go to the Downloads page (On the left side), and select the appropriate
> build 32 or 64 bit build.
>
> But I still dont see a wins parser included
>
>
> "JohnGil (MSFT)" wrote:
>
> > Netmon 3 is released. The WINS parser is built in. You can get it at:
> >
> > https://connect.microsoft.com/Downlo...spx?SiteID=216
> >
> > "Schuml" wrote:
> >
> > > I am trying to research a wins error 4102, and I can not find anything to
> > > help me resolve the issue.
> > >
> > > I do have 2 wins servers that are located at 2 diffrent sites and are
> > > confugured as wins servers push/pull. These 2 servers seem to replicate fine
> > > when I manully request replication. And the data in the 2 servers is
> > > accurate. My concerne is there is a rogue winserver some where that is
> > > generating this error.
> > > Both Servers are 2003 SP1
> > >
> > > I have done the following
> > >
> > > 1. Make sure the all WINS servers are configured correctly such as from
> > > either Pull only or Push only, to Push/Pull. If you configure WINS A to
> > > perform pull replications with WINS B, make sure it is a push partner of WINS
> > > B.
> > >
> > > 2. If the other WINS server is located across a router, check for network
> > > connectivity to the remote WINS server.
> > >
> > > 3. If the WINS is running on a multihomed server or RRAS server , you may
> > > want to setup WINS to replicate with any partner. Neither are RRAS servers so
> > > not applicable
> > >
> > > 4. You may want to run a Network Monitor trace, and then identify the remote
> > > WINS server (Pull partner) that sends the "WINS: Stop Reason = Message Error"
> > > error message.
> > >
> > > The problem with number 4 is I downloaded the 2003 tools to obtain the
> > > Wins.dll
> > > I have completed the following.
> > > Open Tcpip.ini in the Netmon\Parsers subdirectory.
> > > Add "42 = WINS" to the [TCP_HandoffSet] section of the file, as in the
> > > following example:
> > > [TCP_HandoffSet]
> > > 20 = FTP
> > > 21 = FTP
> > > 23 = TELNET
> > > 25 = SMTP
> > > 42 = WINS
> > > 53 = DNS
> > >
> > > Save and close Tcpip.ini.
> > > Open Parser.ini in the Netmon subdirectory.
> > > Add "WINS.DLL = 0: WINS" to the [PARSERS] section of the file, as in the
> > > following example:
> > > [PARSERS]
> > > FRAME.DLL = 0: FRAME
> > > MAC.DLL = 0: ETHERNET, TOKENRING, FDDI, TMAC, SMT
> > > LLC.DLL = 0: LLC, RPL, SNAP, BPDU
> > > NETBIOS.DLL = 0: NETBIOS
> > > SMB.DLL = 0: SMB
> > > ...
> > > WINS.DLL = 0: WINS
> > >
> > > Add the following section to the end of Parser.ini.
> > > [WINS]
> > > Comment = "WINS Server Replication"
> > > FollowSet =
> > > HelpFile =
> > >
> > > Save and close Parser.ini.
> > >
> > > And I have copied the Wins.dll into the parsers folder.
> > >
> > > Yet when I run network monitor wins does show up as a parser to filter on.
> > > and I am not seeing wins entries in the capture.
> > >

Reply With Quote
  #5  
Old 01-26-2007, 11:22 PM
Schuml
Guest
 
Posts: n/a
Default RE: Wins.dll is not recognized as a parser in netmon

thanks John I will take a look at it


"JohnGil (MSFT)" wrote:

> It's called NBTNS for NetBIOS over TCP Name Server or something like that.
>
> "Schuml" wrote:
>
> > Thanks John;
> >
> > The Site mentioned did not work however you can download netmon 3.0
> >
> > Go to http://connect.microsoft.com
> >
> > Sign in with your passport account.
> >
> > Choose "Available Connections" on the left.
> >
> > Choose "Apply" for Network Monitor 3.0 (once you've finished with the
> > application, the selection appears in your "My Participation" page).
> >
> > Go to the Downloads page (On the left side), and select the appropriate
> > build 32 or 64 bit build.
> >
> > But I still dont see a wins parser included
> >
> >
> > "JohnGil (MSFT)" wrote:
> >
> > > Netmon 3 is released. The WINS parser is built in. You can get it at:
> > >
> > > https://connect.microsoft.com/Downlo...spx?SiteID=216
> > >
> > > "Schuml" wrote:
> > >
> > > > I am trying to research a wins error 4102, and I can not find anything to
> > > > help me resolve the issue.
> > > >
> > > > I do have 2 wins servers that are located at 2 diffrent sites and are
> > > > confugured as wins servers push/pull. These 2 servers seem to replicate fine
> > > > when I manully request replication. And the data in the 2 servers is
> > > > accurate. My concerne is there is a rogue winserver some where that is
> > > > generating this error.
> > > > Both Servers are 2003 SP1
> > > >
> > > > I have done the following
> > > >
> > > > 1. Make sure the all WINS servers are configured correctly such as from
> > > > either Pull only or Push only, to Push/Pull. If you configure WINS A to
> > > > perform pull replications with WINS B, make sure it is a push partner of WINS
> > > > B.
> > > >
> > > > 2. If the other WINS server is located across a router, check for network
> > > > connectivity to the remote WINS server.
> > > >
> > > > 3. If the WINS is running on a multihomed server or RRAS server , you may
> > > > want to setup WINS to replicate with any partner. Neither are RRAS servers so
> > > > not applicable
> > > >
> > > > 4. You may want to run a Network Monitor trace, and then identify the remote
> > > > WINS server (Pull partner) that sends the "WINS: Stop Reason = Message Error"
> > > > error message.
> > > >
> > > > The problem with number 4 is I downloaded the 2003 tools to obtain the
> > > > Wins.dll
> > > > I have completed the following.
> > > > Open Tcpip.ini in the Netmon\Parsers subdirectory.
> > > > Add "42 = WINS" to the [TCP_HandoffSet] section of the file, as in the
> > > > following example:
> > > > [TCP_HandoffSet]
> > > > 20 = FTP
> > > > 21 = FTP
> > > > 23 = TELNET
> > > > 25 = SMTP
> > > > 42 = WINS
> > > > 53 = DNS
> > > >
> > > > Save and close Tcpip.ini.
> > > > Open Parser.ini in the Netmon subdirectory.
> > > > Add "WINS.DLL = 0: WINS" to the [PARSERS] section of the file, as in the
> > > > following example:
> > > > [PARSERS]
> > > > FRAME.DLL = 0: FRAME
> > > > MAC.DLL = 0: ETHERNET, TOKENRING, FDDI, TMAC, SMT
> > > > LLC.DLL = 0: LLC, RPL, SNAP, BPDU
> > > > NETBIOS.DLL = 0: NETBIOS
> > > > SMB.DLL = 0: SMB
> > > > ...
> > > > WINS.DLL = 0: WINS
> > > >
> > > > Add the following section to the end of Parser.ini.
> > > > [WINS]
> > > > Comment = "WINS Server Replication"
> > > > FollowSet =
> > > > HelpFile =
> > > >
> > > > Save and close Parser.ini.
> > > >
> > > > And I have copied the Wins.dll into the parsers folder.
> > > >
> > > > Yet when I run network monitor wins does show up as a parser to filter on.
> > > > and I am not seeing wins entries in the capture.
> > > >

Reply With Quote
  #6  
Old 01-27-2007, 07:12 AM
JohnGil (MSFT)
Guest
 
Posts: n/a
Default RE: Wins.dll is not recognized as a parser in netmon

I read your post agin. NM3 doesn't have a WINS Repl parser, yet. I tried
NM2 and has the same problem. I was able to get it working with the info in
299346.

"Schuml" wrote:

> I am trying to research a wins error 4102, and I can not find anything to
> help me resolve the issue.
>
> I do have 2 wins servers that are located at 2 diffrent sites and are
> confugured as wins servers push/pull. These 2 servers seem to replicate fine
> when I manully request replication. And the data in the 2 servers is
> accurate. My concerne is there is a rogue winserver some where that is
> generating this error.
> Both Servers are 2003 SP1
>
> I have done the following
>
> 1. Make sure the all WINS servers are configured correctly such as from
> either Pull only or Push only, to Push/Pull. If you configure WINS A to
> perform pull replications with WINS B, make sure it is a push partner of WINS
> B.
>
> 2. If the other WINS server is located across a router, check for network
> connectivity to the remote WINS server.
>
> 3. If the WINS is running on a multihomed server or RRAS server , you may
> want to setup WINS to replicate with any partner. Neither are RRAS servers so
> not applicable
>
> 4. You may want to run a Network Monitor trace, and then identify the remote
> WINS server (Pull partner) that sends the "WINS: Stop Reason = Message Error"
> error message.
>
> The problem with number 4 is I downloaded the 2003 tools to obtain the
> Wins.dll
> I have completed the following.
> Open Tcpip.ini in the Netmon\Parsers subdirectory.
> Add "42 = WINS" to the [TCP_HandoffSet] section of the file, as in the
> following example:
> [TCP_HandoffSet]
> 20 = FTP
> 21 = FTP
> 23 = TELNET
> 25 = SMTP
> 42 = WINS
> 53 = DNS
>
> Save and close Tcpip.ini.
> Open Parser.ini in the Netmon subdirectory.
> Add "WINS.DLL = 0: WINS" to the [PARSERS] section of the file, as in the
> following example:
> [PARSERS]
> FRAME.DLL = 0: FRAME
> MAC.DLL = 0: ETHERNET, TOKENRING, FDDI, TMAC, SMT
> LLC.DLL = 0: LLC, RPL, SNAP, BPDU
> NETBIOS.DLL = 0: NETBIOS
> SMB.DLL = 0: SMB
> ...
> WINS.DLL = 0: WINS
>
> Add the following section to the end of Parser.ini.
> [WINS]
> Comment = "WINS Server Replication"
> FollowSet =
> HelpFile =
>
> Save and close Parser.ini.
>
> And I have copied the Wins.dll into the parsers folder.
>
> Yet when I run network monitor wins does show up as a parser to filter on.
> and I am not seeing wins entries in the capture.
>

Reply With Quote
Reply

Tags
netmon, parser, recognized, winsdll

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


All times are GMT. The time now is 04:53 PM.


Powered by vBulletin® Version 3.7.3
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.