imaginetsecurity |
Why do you have static routing on your internal routers? Have you considered EIGRP?
Do you have ACLs on your routers? Are you sure the virtual IP is correctly enabled?
What are the major networks involved here? (eg. branch1 192.168.x.x and branch2 192.168.y.y) When you PING what network are you on that can reach the individual IPs but not the virtual? Are you local to that segment or remote and coming across the routers?
MrWizard |
More than likely the problem is…
The default gateway on the virtual IP is not set to the router.
mysore |
First of all Thanks for your relay “Mr.imaginetsecurity”.
We don’t have any ALCs on our router. and Virtual Ip is correctly enabled because it is working in local segment. Sorry for mentioning wrong segments. My local &Network Segment are like eg: 192.170.2.0 and 192.170.1.0, When i try to ping 192.170.2.32&33 from 1.0 net work it pings, but not Virtual IP 192.170.2.34,& i am pinging form remote Segment accross router.
imaginetsecurity |
The other post suggesting the virt IP gateway has merit. How are you creating the loadbalance? Via TS or the routers?
Can you PING the virt IP from either of the TS (i.e. local to that network segment)?
Is your gateway correct for the virt IP? The subnet masks are correct, too (across each device)?
mysore |
We are creating load Balance Via TS, Option is there in windows 2003, and i can able to ping to virt Ip from Both TS.
Can we set Gateway for Virtual IP? further details will be help ful,
and Subnet mask are correct for TS.
———————————————————–
The other post suggesting the virt IP gateway has merit. How are you creating the loadbalance? Via TS or the routers?
Can you PING the virt IP from either of the TS (i.e. local to that network segment)?
Is your gateway correct for the virt IP? The subnet masks are correct, too (across each device)?
imaginetsecurity |
Have you gone through the Win2003 “Load Balancing Terminal Servers” deployment procedures? Find them here <a href="http://www.microsoft.com/resources/documentation/WindowsServ/2003/all/deployguide/en-us/Default.asp?url=/resources/documentation/WindowsServ/2003/all/deployguide/en-us/sdcce_term_nfow.asp" rel="nofollow">http://www.microsoft.com/resources/documentation/WindowsServ/2003/all/deployguide/en-us/Default.asp?url=/resources/documentation/WindowsServ/2003/all/deployguide/en-us/sdcce_term_nfow.asp</a>
You might also check the white paper “Session Directory and Load Balancing Using Terminal Server” found here:
<a href="http://www.microsoft.com/windowsserver2003/techinfo/overview/sessiondirectory.mspx" rel="nofollow">http://www.microsoft.com/windowsserver2003/techinfo/overview/sessiondirectory.mspx</a>
jrgreenberg |
When you set up the virtual IP, did you get a virtual MAC associatred with it? Can you see that MAC in the HQ’s router’s ARP table? Cisco routers/MSFCs don’t always handle virtual MACs well. You might want to add a static arp on the HQ router to bind the virtual IP to the virtual MAC.
The command for this: router(config)# arp
Virtual IP Address, Windows Server 2003, Windows Terminal Server, Routers, Cisco routers
We have 2 Windows 2003 Terminal Servers and both are part of load balance with a Single Virtual IP Address. For Eg
0
