| Author |
Message |
Brian Hamilton
Guest
|
 Posted:
Thu Oct 27, 2005 12:52 am Post subject:
Public IM Connectivity Problem |
|
|
I'm currently trying to get Public IM Connectivity to function on our LCS
2005 SP1 environment. Currently, I am unable to see the status or
communicate with any external (MSN, Yahoo, AOL) user.
After running LCSDiag on my access proxy, I believe I came upon the source
of my problem. I did a Connectivity test against wmi configured servers, and
when it reached the "checking provider servers" section, it reported failure
to connect on each service. The steps it asked me to verfiy was to make sure
the server is listening on 5061 port, make sure my firewall is allowing
5061, and make sure the server is running. I verified that the firewall is
allowing connection from my external nic to any destination on port 5061. I
then tried to telnet to one of the providers (federation.messenger.msn.com)
on port 5061 and the connection timed out. On a hunch, I disabled my private
NIC and tried the telnet again, and it connected properly. I'm down to the
point where I think I'm dealing with a routing table issue, but I'm not
familiar with routing tables or how to configure them. Have any of you
experienced traffic not being routed through the correct NIC on your access
proxy? Also, can someone provide information on what to look for in a
routing table that may be causing problems? I have yet to find any
documentation on routing tables and access proxies.
It makes sense to me that this kind or problem might be more common, since
the recommended configuration of the access proxy basically makes it a
router. Any help is appreciated!
LCS 2005 SP1 Environment:
2 EE Front End Servers, hardware loadbalanced
Backend Server - Active/Passive SQL Cluster
2 SE Directors, hardware loadbalanced
1 Access Proxy |
|
| Back to top |
|
 |
Brian Hamilton
Guest
|
| Posted:
Thu Oct 27, 2005 4:51 pm Post subject:
Re: Public IM Connectivity Problem |
|
|
Hi Bob,
Yes, I've recieved the email from Microsoft that my provisioning request was
completed.
An update on my troubleshooting...I found that our server team that did the
initial OS and network set up assigned the default gateway for each NIC,
both on different subnets...this may be part of the problem. I removed the
gateway configuration on the private interface, and left the public one. Of
course, I could then telnet to the provisioning servers. However, I am now
unable to connect to the VIP of my director array...I assume I need to add a
route to the routing tables, but am unsure of the specifics. I'm confused as
to why I would even need to do this...I would have thought the LCS Access
Proxy application would do the routing.
Also, the documentation on this "recommended" access proxy/network
configuration is lacking at best...
"Bob Christian" <BobChristian@removethis.gmail.com> wrote in message
news:OigOQgw2FHA.1140@tk2msftngp13.phx.gbl...
| Quote: | Brian -
Have you recieved the notice, from Microsoft, regarding PIC being
provisioned for your domain?
The access proxy should pick up the next hop and send it out the correct
NIC...it is odd that it is not.
Bob
--
Bob Christian II
MVP - LCS
http://bobchristian.blogspot.com - Blog
"Brian Hamilton" <brian@hamilton.com> wrote in message
news:u1noF8m2FHA.472@TK2MSFTNGP15.phx.gbl...
I'm currently trying to get Public IM Connectivity to function on our LCS
2005 SP1 environment. Currently, I am unable to see the status or
communicate with any external (MSN, Yahoo, AOL) user.
After running LCSDiag on my access proxy, I believe I came upon the
source of my problem. I did a Connectivity test against wmi configured
servers, and when it reached the "checking provider servers" section, it
reported failure to connect on each service. The steps it asked me to
verfiy was to make sure the server is listening on 5061 port, make sure
my firewall is allowing 5061, and make sure the server is running. I
verified that the firewall is allowing connection from my external nic to
any destination on port 5061. I then tried to telnet to one of the
providers (federation.messenger.msn.com) on port 5061 and the connection
timed out. On a hunch, I disabled my private NIC and tried the telnet
again, and it connected properly. I'm down to the point where I think I'm
dealing with a routing table issue, but I'm not familiar with routing
tables or how to configure them. Have any of you experienced traffic not
being routed through the correct NIC on your access proxy? Also, can
someone provide information on what to look for in a routing table that
may be causing problems? I have yet to find any documentation on routing
tables and access proxies.
It makes sense to me that this kind or problem might be more common,
since the recommended configuration of the access proxy basically makes
it a router. Any help is appreciated!
LCS 2005 SP1 Environment:
2 EE Front End Servers, hardware loadbalanced
Backend Server - Active/Passive SQL Cluster
2 SE Directors, hardware loadbalanced
1 Access Proxy
|
|
|
| Back to top |
|
|
Bob Christian
Guest
|
| Posted:
Thu Oct 27, 2005 4:51 pm Post subject:
Re: Public IM Connectivity Problem |
|
|
Brian -
Have you recieved the notice, from Microsoft, regarding PIC being
provisioned for your domain?
The access proxy should pick up the next hop and send it out the correct
NIC...it is odd that it is not.
Bob
--
Bob Christian II
MVP - LCS
http://bobchristian.blogspot.com - Blog
"Brian Hamilton" <brian@hamilton.com> wrote in message
news:u1noF8m2FHA.472@TK2MSFTNGP15.phx.gbl...
| Quote: | I'm currently trying to get Public IM Connectivity to function on our LCS
2005 SP1 environment. Currently, I am unable to see the status or
communicate with any external (MSN, Yahoo, AOL) user.
After running LCSDiag on my access proxy, I believe I came upon the source
of my problem. I did a Connectivity test against wmi configured servers,
and when it reached the "checking provider servers" section, it reported
failure to connect on each service. The steps it asked me to verfiy was to
make sure the server is listening on 5061 port, make sure my firewall is
allowing 5061, and make sure the server is running. I verified that the
firewall is allowing connection from my external nic to any destination on
port 5061. I then tried to telnet to one of the providers
(federation.messenger.msn.com) on port 5061 and the connection timed out.
On a hunch, I disabled my private NIC and tried the telnet again, and it
connected properly. I'm down to the point where I think I'm dealing with a
routing table issue, but I'm not familiar with routing tables or how to
configure them. Have any of you experienced traffic not being routed
through the correct NIC on your access proxy? Also, can someone provide
information on what to look for in a routing table that may be causing
problems? I have yet to find any documentation on routing tables and
access proxies.
It makes sense to me that this kind or problem might be more common, since
the recommended configuration of the access proxy basically makes it a
router. Any help is appreciated!
LCS 2005 SP1 Environment:
2 EE Front End Servers, hardware loadbalanced
Backend Server - Active/Passive SQL Cluster
2 SE Directors, hardware loadbalanced
1 Access Proxy
|
|
|
| Back to top |
|
|
Benba
Guest
|
| Posted:
Fri Oct 28, 2005 12:51 am Post subject:
Re: Public IM Connectivity Problem |
|
|
Yep, you're right. You'll need a static route on your access proxy(s) to the
director(s). Multi-homed access proxy with DG on the public side assuming
the director is on a different subnet than the director will require a static
route.
"Brian Hamilton" wrote:
| Quote: | Hi Bob,
Yes, I've recieved the email from Microsoft that my provisioning request was
completed.
An update on my troubleshooting...I found that our server team that did the
initial OS and network set up assigned the default gateway for each NIC,
both on different subnets...this may be part of the problem. I removed the
gateway configuration on the private interface, and left the public one. Of
course, I could then telnet to the provisioning servers. However, I am now
unable to connect to the VIP of my director array...I assume I need to add a
route to the routing tables, but am unsure of the specifics. I'm confused as
to why I would even need to do this...I would have thought the LCS Access
Proxy application would do the routing.
Also, the documentation on this "recommended" access proxy/network
configuration is lacking at best...
"Bob Christian" <BobChristian@removethis.gmail.com> wrote in message
news:OigOQgw2FHA.1140@tk2msftngp13.phx.gbl...
Brian -
Have you recieved the notice, from Microsoft, regarding PIC being
provisioned for your domain?
The access proxy should pick up the next hop and send it out the correct
NIC...it is odd that it is not.
Bob
--
Bob Christian II
MVP - LCS
http://bobchristian.blogspot.com - Blog
"Brian Hamilton" <brian@hamilton.com> wrote in message
news:u1noF8m2FHA.472@TK2MSFTNGP15.phx.gbl...
I'm currently trying to get Public IM Connectivity to function on our LCS
2005 SP1 environment. Currently, I am unable to see the status or
communicate with any external (MSN, Yahoo, AOL) user.
After running LCSDiag on my access proxy, I believe I came upon the
source of my problem. I did a Connectivity test against wmi configured
servers, and when it reached the "checking provider servers" section, it
reported failure to connect on each service. The steps it asked me to
verfiy was to make sure the server is listening on 5061 port, make sure
my firewall is allowing 5061, and make sure the server is running. I
verified that the firewall is allowing connection from my external nic to
any destination on port 5061. I then tried to telnet to one of the
providers (federation.messenger.msn.com) on port 5061 and the connection
timed out. On a hunch, I disabled my private NIC and tried the telnet
again, and it connected properly. I'm down to the point where I think I'm
dealing with a routing table issue, but I'm not familiar with routing
tables or how to configure them. Have any of you experienced traffic not
being routed through the correct NIC on your access proxy? Also, can
someone provide information on what to look for in a routing table that
may be causing problems? I have yet to find any documentation on routing
tables and access proxies.
It makes sense to me that this kind or problem might be more common,
since the recommended configuration of the access proxy basically makes
it a router. Any help is appreciated!
LCS 2005 SP1 Environment:
2 EE Front End Servers, hardware loadbalanced
Backend Server - Active/Passive SQL Cluster
2 SE Directors, hardware loadbalanced
1 Access Proxy
|
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in