Problem in Connecting to a Remote Location

1. I created a new VLAN for our new office location near the head office with the same configuration as the other VLAN's which are running in our office.
2. But the problem now is that I'm unable to ping to a remote location which has an ip series of 196.12.80.0 series from local lan ip 10.50.23.0 series.
3. And my network connection goes like this for remote locations.

C:\Documents and Settings\ADMIN>tracert 196.12.80.225

(remote location)
Tracing route to 196.12.80.225 over a maximum of 30 hops

So whenever I try to ping or tracerorute this particular network I'm unable to reach it but from other local lan ip's apart from 10.50.23.0 series any series before this say for eg 10.50.18.0 im able to reach the location.

Hi,
Thanks for the reply; I added a static route for the following and issue is solved.

But now another problem is there we have nearly 23 vlans and everything is functioning fine but now the vlan series 10.50.18.0/24 255.255.255.0 is unable to communicate with any of other vlans in terms of file sharing or smb apart from its local lan it's unable to communicate with the other vlans.
Any suggestions of what the problems can be because I never added any inter vlan routing but everything worked well and can't understand where the problem is arising. Quick response will be appreciated.

Is smb aprt using special protocol?
If it is, you can use combination of command of IP forward-protocol xxxx (protocol to be transmit) on config mode and an IP helper-address on interface configuration.

@ William
Well I have given a access link from a 2960 catalyst from our head office using a fiber connection to your branch location to a unmanageable linksys switch.
So the total can be a 3750 cisco l3 switch which has vlan database and a 2960 catalyst ,
one unmanaged switch.

Hi Vivek, if you can ping but not reach file shares, you may be blocking file share traffic at some point in the path.
For Microsoft file sharing (SMB) User Datagram Protocol (UDP) ports from 135 through 139 and Transmission Control Protocol (TCP) ports from 135 through 139 cannot be blocked.
Direct-hosted SMB traffic without a network basic input/output system (NetBIOS) uses port 445 (TCP and UPD).

The 10.50.23.0/24 network cannot reach the 192.12.80.0/24 network. This is the stated problem.

The path from 10.50.23.0/24 is via a router at 10.50.0.10 to a WAN gateway at 10.113.137.241 at which point the packets fail to reach their destination.

There is an 'access link from a 2960 catalyst' (switch) to another unmanaged switch in another location.

There is a 3750 switch with your VLAN database, a 2960 switch, and some unmanaged switch that may or may not be involved and may or may not be in the same location.

So far, I have an incomplete and jumbled picture of your network. With the information you have given me, I can't understand how the other 23 VLANS connect much less why you would expect 10.50.23.0/24 to reach the 192.12.80.0/24 network.

Please provide a clear and detailed description of your network so that we can help you.

You got it all messed you buddy the resolution for my network problem not reaching 192.12. series was rectified after i added a static route in my router to the particular wan location from my local LAN.

The other problem im facing is that we have a few branch offices nearby our headoffice which are connected to the HO network using a fiber connection.

So what I did was terminate the fiber line connection to a port on 2960 switch and assigned the vlan 18 to it and kept the port on access mode.

On the other end is the branch office which has the up link from HO and fiber line which got the up link from 2960 switch is connected to a unmanaged switch.

And the problem is we are able to ping and as well make remote sessions but unable to make smb's to file share's or any share specified.So this is the problem I thought a problem might b wid antivirus so i removed any virus and disable the firewall as well bt still no go for it.

Its an existing ip range and it is working fine at one of our branch locations which is connected to a managed cisco switch it is working fine im able to ping smb and remote as well,but its creating problem with unmanaged switch,which is at another location.

So i feel the problem might be there with the unmanaged switch but how can i figure this thing out?

i mean i didn;t get what u meant by same domain it is the working scenario like workgroup and domain systems or the network???
well for the fact im confused is that the same vlan is working fine on a managed switch at another branch office bt its creating problems on unmanaged switch is it something gotta do with it??
and i thought there might be a problem with the antivirus or firewall so i uninstalled the antivrus and disabled the firewall service but still no go!!

Check native valan 1 in the router. Assign IP to native Vlan and made it up.
It might be native vlan mismatch. When other switches other than unmanaged
switches we have to check
native vlans. Unmanaged switches works on native vlan only. Your problem
might be connecting to unmanaged switch.
Try it with connecting managed switch with specific vlan.

Router
|| l3switch 3750 (all vlans are configured in this switch and connected to other managed switches using trunk links)
|| managed 2960 switch(connected to 3750 using trunk)from this switch i have configured a port with vlan 18 and kept in access mode
||
and the above link is connected via a fiber line and connecting to a unmanaged switch.
||
the same vlan i have configured and kept it at another branch using trunk ports on both the ends its workin fine.
||
(connected to pc's)

And now ill give everyone a clear image of the issue.

@ pankaj lakhani unmanaged switches can't handle or be manually configured vlan's but they should be able give a connection in access mode at least and there is no problem with connectivity but only the file sharing and same connected another location with managed switch it is working fine.

@tobby you find the description in here. And I have assigned vlan on my end of managed switch and that means the link which it will be getting is a access mode method.(uplink)

@sankaran well if native vlan configuration might have been wrong then how to check it in the unmanaged switch bu default native vlan will be the ip of the switch so ??but itwas workin fine until suddenly it stopped functioning.

@nza well in this present scenario trunking doesn't even come in place as i have assigned a vlan to a particular port and then made it switch port mode access. So that initially comes to as that it is just another port in access mode so the receiving end won't be receiving any vlan info but the ip series which is on that vlan right?

and coming to the pinging issue to a remote location that has been sorted out.

Thanks guys for replies but issue is still pending because im unable to do an file share .just can't figure out where the problem is arising is it on the network end the system end? Any help guys appreciate it.

As i understand that u have the HO 10.50.23.0 and the remote location has
196.12.80.x is the newly added location.

As you said u were not able to communicate only from the range 10.50.23.0,
which means Routing issue. check the routing table in both the side.
do tracert from both sides for the network which is not working and do
tracert for the working network.

Make sure the duplex on the managed switch port assigned to vlan 18 is full and speed 100. Otherwise, the unmanaged switch may force it to half duplex and auto speed which could be a problem. Try that, test and advise.

@tobby yes,file sharing is the only problem im facing and i checked the duplex settings is absolutely fine and it is in 100mbps full .
@ jaishankar that problem is solved i added a static route between these two networks.

any more suggestions or if anyone has faced these issue can help me out.

Are you sure that there is no problem with the routing or is there anything that I am missing here? And if yes, how to enable these ports as you mentioned in the post and can you please specify how to enable these port settings.

Without investigating your setup myself, I cannot say with certainty that you do not have a routing problem. However, your can pass ICMP and TCP traffic as evidenced by ping replies and successful RDP connection. If you had a routing issue, I don't see how these would pass but SMB fail.
When you you have SMB issues and try to connect, you will either be prompted for a password if the share can be accessed (no port blocking) or you will get a timeout if the share path is unreachable (block port or unable to resolve name).

It sounds as if you are trying to connect by IP and not name. That's helpful since we wont have to troubleshoot a DNS or NetBIOS issue.

So, what you may want to do is to check your routers, servers, and client machines involved in the file share (SMB). From reading your posts, it looks like we are discussing a Windows file share (if this is not correct let me know).

Look at the machine hosting the share and any router, proxy, or firewall on the server and between the server and the client machine.

On windows machines the process is as follows (dont forget to add exceptions for ports 135 through 139 as well)
Click Start, and then click My Network Places.
Under Network Tasks, click View Network Connections. (Or, right-click My Network Places on the desktop, and then click Properties.)
Right-click the connection that you use for the Internet, and then click Properties.
Click the Advanced tab, and then click Settings.

Note If the Settings button is unavailable, ICF is not enabled on this connection, and you do not have to open any ports (because they are all already open).
Click Add to open a new port.
In the Description box, type a friendly name. For example, type File Sharing : Port 445.
In the Name or IP address of the computer hosting this service on your network box, type 127.0.0.1.

Note You can specify the IP address of an internal computer. But you typically will use 127.0.0.1.
In the External port and Internal port boxes, type the port number. Generally, this number is the same.
Click either TCP or UDP, and then click OK.
Repeat steps for each port that you want to open.

Your routers and firewalls between your networks must also not block these ports.

Copyright 1998-2015 Ziff Davis, LLC (Toolbox.com). All rights reserved. All product names are trademarks of their respective companies. Toolbox.com is not
affiliated with or endorsed by any company listed at this site.