9 replies
by cdcents
You may have already tried this but it is always good to check if you haven't.
Try to ping/tracert a workstation on the 10.x.y.z network from the multi homed server. By default all traffic would be routed to the 206.x.y.z network since that is theprimary. If you find that the traffic is being routed to the 206.x.y.z network then you may have to add static routes for the other network. syntax would be
ROUTE ADD 10.x.y.0 10.x.y.z
(I am presuming a full Class C subnet hence the 0 in the last octet. Please change as necessary). If this helps and you need more info I will check this posting.
CD
by jyimcse
by cdcents
by jyimcse
by cdcents
by jyimcse
by shmaltz
please read the following MS KB articles:
Q221210
at
http://support.microsoft.com/support/kb/articles/Q221/2/10.ASP?LN=EN-US&SD=gn&FR=0&qry=multihomed%20PDC&rnk=5&src=DHCS_MSPSS_gn_SRCH&SPR=MSALL
Q181774
at
http://support.microsoft.com/support/kb/articles/Q181/7/74.ASP?LN=EN-US&SD=gn&FR=0&qry=multihomed%20PDC&rnk=9&src=DHCS_MSPSS_gn_SRCH&SPR=MSALL
Hope this helps.
by jyimcse
The articles are interesting. The Servers are not considered multi-homed because there aren't two NIC's. One nic with primary and secondary ip addresses. I guess the only solution is to switch the addresses or get ride of one. Since the lateris the ultimate goal anyway, I will resolve this, but I wanted to know why it wasn't working.
Thanks for you help
by jyimcse
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending