Inter-VLAN Problem on Windows File sharing

[eabonalla]

Hi,

Im using 3750 L3 switch and 2950 L2 Switch. I've configured 12 VLANs and configured inter-VLAN. But there has been a problem with file sharing on windows. I can ping the machine on different VLANs and i can also run some application like remote desktop connections. But file sharing is failing. Pls help. thanks

[Thotsaphon Lueangwattanaphong]

Hi

The problem occurs when you test file shareing of 10.1.2.18 and 10.1.7.4 so please confirm my confusion :D

1. From 10.1.2.18 ping to 10.1.7.4 what is the result?

2. From 10.1.2.18 telnet to 10.1.7.4 with port 3389 what is the result? It would work because you can remote desktop into it as you tell.

3. From 10.1.2.18 telnet to 10.1.7.4 with port 445 what is the result?

[Danilo Dy]

Your policy routing which has PEZA ACL makes host from VLAN101 hop to 10.1.1.6 and back.

permit ip 10.1.2.0 0.0.0.127 any

Router 10.1.1.6 interface is clean of ACL for windows file sharing?

Hmmm, the last line in your reply gives more question than answer :)

[manoj.jain]

Hello

I m facing same kind of problem tooo.. i m using Vlan also ,my domain controller in one of the vlan ,some workstation in another vlan ,but they are not able to join the domain,giving me error of domain controller not joining. but the workstation which is in same vlan of DC are able to join the domain.

Plz guide me how to resolve this.

Thanx in advance

[eabonalla]

i can ping 10.1.7.4.

i cannot telnet 10.1.7.4 on port 3389

i cannot telnet 10.1.7.4 on port 445

im using putty program for telnet to work on different ports aside from default.

[Danilo Dy]

AS mentioned in my previous post, your policy routing which has PEZA ACL makes host from VLAN101 hop to 10.1.1.6 and back to reach 10.1.7.x.

permit ip 10.1.2.0 0.0.0.127 any

Router 10.1.1.6 interface is clean of ACL for windows file sharing?

[Danilo Dy]

When logic doesn't work, its time to perform sniffing. Use wireshark http://www.wireshark.org/

HostA (10.1.2.18)= host connecting to shared file in HostB

HostB (10.1.7.4) = host with file sharing enable

Sniff HostA port in switch and trigger a file sharing connection from HostA to HostB. Save the result and post it here.

Sniff HostB port in switch and trigger a file sharing connection from HostA to HostB. Save the result and post it here.

[eabonalla]

my policy based routing is just for traffic bound to internet. traffic inside our LAN shoud be denied to those two router.

I will try the sniffing.

i will post again the result. maybe next week.

Thank so much for all your help.

[nyr.hakeem-habeeb]

Hi

have you checked bindings of services on the adapter, this could be a strong culprit.

Thanks

[eabonalla]

how can i check this bidings? pls pls pls help. i didnt heard of this.

[nyr.hakeem-habeeb]

Hi

its "Control Panel > Network Connections > Advanced > Advanced Settings ...."

Thanks

[Danilo Dy]

Check bindings http://support.microsoft.com/kb/894564

But you already disable Win XP Firewall and you are able to connect in the same network (VLAN).

I remember during NT4 that you can connect PC to PC file sharing only in the same broadcast domain. In a large enterprise with multiple network you need client server. Anyway, I no windows expert so don't take this comment seriously :)

[eabonalla]

im thinking of bindings on switches. my mistake.

anyway ill try the sniffing first. havent tried it.

thanks guys.

[Sam Smiley]

If you can ping from VLAN to VLAN this isn't a InterVLAN issue. This is clearly a DNS/WINS/DNS Suffix issue, you don't go into a great deal of detail how your Windows machines are set up. If you have a domain controller in the network with Active Directory DNS this should be automatic, however DNS since Windows 2008 is far from automatic. By default on a Windows Domain Controller DNS will set up as a forwarder. If this is configured as a forwarder your clients will be registering to a remote host (most likely the ISP DNS); this doesn't do your local clients any good while trying to resolve names. If this is the case configure your DNS to resolve from root hints. You should also configure WINS lookup since you have gone to the trouble to install WINS.

If you don't have an Active Domain Controller this gets more complicated. Since Windows 2000 clients have relied on DNS to find things on the network. If there is no domain controller the clients have nowhere to register, you will have to open up your DNS server to dynamic registration.

Finally the DNS suffix search order will also cause this if it is not configured properly, again not knowing your Windows infrastructure it is impossible to recommend. All of this should be handed out to the client with DHCP. The DHCP server should also be handing out the netbios-node-type to the clients, however if DNS/WINS/DNS Suffix are not correct it won't matter.

Regards,

Sam