<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Are both machines on the same subnet? If not are their default
routes correct and default gateways know how to get to each subnet?
This sounds like behavior I've seen before when default gateway
route was incorrect and trying to communicate with server not on the
same subnet.<br>
<br>
<div class="moz-cite-prefix">On 7/9/2015 9:17 AM, Lightner, Jeff
wrote:<br>
</div>
<blockquote
cite="mid:DM2PR07MB1514764522C7DA73BEBE93DBC1900@DM2PR07MB1514.namprd07.prod.outlook.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<meta name="Generator" content="Microsoft Word 14 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
span.EmailStyle17
        {mso-style-type:personal-compose;
        font-family:"Calibri","sans-serif";
        color:windowtext;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-family:"Calibri","sans-serif";}
@page WordSection1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
        {page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal">We have a server that appears to be unable
to connect to various IPs (mostly printers) in our WAN at
times.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The odd thing is that the interface is not
down on either the server or the printer. The server can
reach multiple other IPs when this occurs but for some reason
can’t reach a few. Similarly when this occurs we can reach
these other IPs from other servers in the same VLAN.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">There are no errors shown in statistics on
the interface (eth0) on the server nor on the port it attached
to on the switch. There are no errors shown in
/var/log/messages or dmesg.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The IPs are not always the same ones. In
fact yesterday when we saw the issue on IPs I tested the IPs
that it couldn’t reach the day before that I’d resolved and
they were still working.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">We’ve tried:<o:p></o:p></p>
<p class="MsoNormal">Killing the lp process that is hung at the
start of this issue on server side.<o:p></o:p></p>
<p class="MsoNormal">Clearing arp on the server.<o:p></o:p></p>
<p class="MsoNormal">Clearing arp on the switch.<o:p></o:p></p>
<p class="MsoNormal">Bouncing cups (note issue is NOT just cups
– when this occurs we can not ping the affected IPs nor can we
telnet in on port 9100 as we would normally be able to do).<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The only thing that seems to resolve the
issue (and does each time) is having the interface bounce on
the server.<o:p></o:p></p>
<p class="MsoNormal">We’’ve done that by:<o:p></o:p></p>
<p class="MsoNormal">Rebooting the server<o:p></o:p></p>
<p class="MsoNormal">Ifup/ifdown on the server interface<o:p></o:p></p>
<p class="MsoNormal">Removing and reseating the cable.<o:p></o:p></p>
<p class="MsoNormal">Resetting the switch port.<o:p></o:p></p>
<p class="MsoNormal">In each of those we see the port go down
then come back up and after that the previously unreachable
IPs are again reachable.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I’m suspecting a bad interface port on
either the server or the switch but in the absence of actual
errors can’t prove one way or the other.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">This is different than any other network
issue I’ve seen. I’m wondering if anyone has run into this
and can shed any light on it?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p style="font-size:10pt; line-height:10pt; font-family:
'Arial','times roman',serif;">
CONFIDENTIALITY NOTICE: This e-mail may contain privileged or
confidential information and is for the sole use of the intended
recipient(s). If you are not the intended recipient, any
disclosure, copying, distribution, or use of the contents of
this information is prohibited and may be unlawful. If you have
received this electronic transmission in error, please reply
immediately to the sender that you have received the message in
error, and delete it. Thank you
</p>
<span style="padding-top:10px; font-weight:color:#CC0000;
font-size:10pt; font-family: 'Arial',Arial,sans-serif; ">
</span><br>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Ale mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Ale@ale.org">Ale@ale.org</a>
<a class="moz-txt-link-freetext" href="http://mail.ale.org/mailman/listinfo/ale">http://mail.ale.org/mailman/listinfo/ale</a>
See JOBS, ANNOUNCE and SCHOOLS lists at
<a class="moz-txt-link-freetext" href="http://mail.ale.org/mailman/listinfo">http://mail.ale.org/mailman/listinfo</a>
</pre>
</blockquote>
<br>
</body>
</html>