I have a problem like this can any one pls advise.
My network is connected to remote branch office through cisco 3600 router using mico wave link.There is no firewall between these two networks.
The problem is i can able to ping the remote server but when i try to access the data i couldnt able to do .
remote server permissions are fully granted for me to access the remote network.
But the thing is few client systems in my network (randomly)can able to access the remote server with out any problem.
what could be the cause of the problem.
The problem is most likely with the service advertising. Over a router, the browser announcements are not sent and hence stations can ping but are unable to connect to a service. The few stations that do work will probably have either an lmhosts file or WINS activated.
The preferred solution is to use WINS.
Thanks for the info.
Already i have wins server in my network and also remote side is having wins.
U mean to say both the wins server has to talk each other .
Can u pls give more info i can follow the same.
Thanks a lot
It is possible to have more than one WINS server but it is obvious that they should have the same database. As far as I know it is not possible to synchronize WINS servers.
To make a server advertise it's services via WINS you must add the WINS ip adress to the list of WINS servers in the servers ip configuration. After that the server must be rebooted.
This is not a networking problem.
I understand your words.
But what i am suspecting is may be my router is not forwarding the wins broadcast to the remote network ,becuase of that this problem is occuring
Is there anything like this.
WINS traffic is not broadcast, it is unicast. The IP adress of the WINS server has to be known to the client in another way, preferrably though DHCP.
It might be that your WINS server is not able to reach the remote network due to incorrect gateway settings or static routes.
Check that clients can reach the WINS server.
are you able to ping from directly connected ? If yes try to ping from i hop away or do an extended ping sourcing your ping from another segment. If your ping from 1 hop away fails the problem is most likely due to the default gateway is misconfigured on the server .
If you can "touch" your remote server (or have someone remotely do so) enable WINS Replication on both your server and the remote server. Then force an immediate replication between the two servers and schedule future replications to occur during non business hours (or hours of light activity).
This should take care of WINS access to remote servers. In addition, you might have to enable WINS server settings in your DHCP lease information. If you do not know how, just ask.
WINS involves the use of Replication Partners. If in your network scenario you have a WINS server on each side of your microwave link, typically the clients on each side will register themselves with the local WINS server on that side. In order for clients on each side to see the other half of your network world, the WINS servers must provide optics for the other side (browsing the network for example). In order to do this, the WINS servers must be configured as Replication Partners of each other, In other words, just don't configure the WINS server on one side - you must configure it on both. Once this is done they will propagate their database registrations to each other. You will likely had to set them up as PUSH/PULL partners of each other.
In terms of the DHCP, set up all the Scopes so that the clients on side-A are given WINS server side-A as their primary WINS and WINS server side-B as their secondary. Obviously a DHCP Scope for the other side would be the opposite. One final caveat (warning) - if you are using multiple DHCP servers, be absolutely sure that the IP range they give out for a give segment does not overlap the one the other DHCP server is giving out.