|
Posted by yanks2112 on July 30, 2008, 10:32 am
If you were Registered and logged in, you could reply and use other advanced thread options
> yanks2112 wrote:
> >> yanks2112 wrote:
> >>> Hi Artie
> >>> Thanks for the quick reply.
> >>> Yes we can get to it from behind the firewall
> >>> We dont have any inspection rules for ssh (this works for other ssh
> >>> servers behind the firewall)
> >>> The OS is Suse linux (not sure what version, I'll chekc that out) the
> >> So you have other SSH servers that work behind the firewall? If so, I
> >> would start by double checking to make sure that the NAT translation a=
nd
> >> ACL's are constructed the same. If they are, I would suggest debugging
> >> the errors from the SUSE box, tail -f /var/log/messages and you should
> >> see some output of the error from there.
>
> > Thanks. I checked the NAT and ACLs and they look ok. The ssh logs
> > show:
>
> > 11:39:24 10.10.10.10. sshd[6904]: Did not receive identification
> > string from ::ffff:192.168.100.100
>
> > Thanks again for your help
>
> Well if you are getting that on the SUSE box, you are connecting fine.
> =A0From googling the error, that has something to do with authentication.
>
> Are you using the same version of SSH across your network including your
> clients?- Hide quoted text -
>
> - Show quoted text -
Hi Artie
It turned out to be a Websense server that was in the middle. The
server was exluded from filtering, yet Websesne still blocked it.
Rebooting the websense server fixed it. Thanks a lot for your help
| 
Yahoo! 
Google 
Windows Live 
del.icio.us 
digg 
Netscape 
XML site map