How can I get Netbios working Acrros frame relay subnets ?

[DKMOORE]

I have recently inherited a 2 site network.
Main site is running NT4 PDC with DNS and WINS attached to a Cisco 1605. This site has W9x, NT, and 2K workstations.
The remote site has no server. It is connected via frame relay using a Cisco 1601. It also has all varieties of Windows platforms.
Both sides can see each other "NetBios Names" via Explorer, however when trying to access the the error "\\xxx is not accessible" "the network path was not found" appears.
However, when using the ip address the shares are accessible!
I have read about opening "udp ports 137 & 138" as well as enabling helper ip address.
This has been done, but to no availe.
I have even tried adding staic mappings in the WINS databse, still the result is the same.
What am I doing incorrectly?
I admit to having very little knowledge about routers.
At which interface should the ip helper address reside?
At which interface should the udp ports be opened?
Does each router use the same ip helper address?
Should the ip helper address be the WINS server address?
Thanks in adavance for any help.

Dkmoore

 

[jeter]

Insert an ip helper address on the router at the remote with the ip address of the server at the host. Jeter@LasVegas.com
Fisher CCNA

 

[Saeed42]

Check out this post

thread557-189575
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Don't be content with being average. Average is as close to the bottom as it is to the top
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

 

[jgercken]

The above solutions basically flood the NetBios packets throughout and are only desireable in small networks. For a scalable solution you should look into using bridging or maybe DLSw+.
-Jeff ----------------------------------------
Wassabi Pop Tarts! Write Kellogs today!

 

[wybnormal]

DLSW+ is not a solution for someone who is weak on Cisco configs. It's also touchy as all getout to latency/line flapping. It maintains a constant TCP connection and occasionally it will go *stupid* and not work..even though the link is up by all accounts.

I dont why you say that IP helper is for small networks? We used in a network of 800 routers up and down the state of CA just fine. You do want to filter out stuff you are not using and instead of just dumping the packets to the segment, give a specific IP address to talk to.

MikeS
Find me at

http://www.packetattack.com

"The trouble with giving up civil rights is that you never get them back"