Terminal Server NLB
. the address is working locally on my LAN. Workstations on the 192.168.1.0/24 network can access the 192.168.1.2 without a problem. Any networks past my router are not able to get to the IP address. The router is not routing the requests to that IP address. and experts have determined that I should add a static ARP entry into the router in order to get the NLB address routed.
NLB is set for unicast and our routers use RIP. A static ARP has been added to the router but ip is still not accessible from another subnet. is there something else we are missing in the NLB setup. We are using mpls to remote sites. The ip is accessible from the inside.
NLB is set for unicast and our routers use RIP. A static ARP has been added to the router but ip is still not accessible from another subnet. is there something else we are missing in the NLB setup. We are using mpls to remote sites. The ip is accessible from the inside.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
they are all accessible except for the nlb ip address.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
ie: 10.129.6.254 /24 to 172.18.1.192/18 this works.
10.129.6.254/24 to 172.18.1.205/18 does not work, this is the ip address of the nlb cluster