There is an exporter available for Rhino 4.0 for SketchUp.http://en.wiki.mcneel.com/default.aspx/ ... House.html
The importer installs by default, but you need this package for export. It may fail with very large models. And it will not solve the problem with textures in exported files.
With regard to textures...this is where Rhino falls down, and I've spoken with the McNeel people about it and the local rep explained that they are working on it.
Surfaces and meshes that have been textured with bitmaps in Rhino itself will not hold their textures or their mapping on export to anything. The experienced Rhino users I know well (if they are using the Rhino Renderer or a similar plugin) often texture objects "by layer", not "by object", and then export their models as DWG or DXF to mesh modelers (and this includes SketchUp). The ACAD formats, unlike 3DS, will lose their materials but they will hold layer status and layer color. In the non-Rhino modeler they "select by layer" and apply new textures and texture mapping using that organizational strategy.
Because of this problem, it most often makes sense to import SketchUp meshes into Rhino for rendering, as opposed to the other way around. The mapping tools, lighting tools, and the Rhino Renderer are quite basic but reliable, as long as you use them to produce output from Rhino. You can also (at least for now) download free betas of several renderers for Rhino, including Brazil and FlamingoNXT.