Default root password
I am lookinf to find/change the default root password on the k2100.
I wish to allow remote ssh access/monitoring.
Is this possible?
I wish to allow remote ssh access/monitoring.
Is this possible?
0 Comments
[ + ] Show comments
Answers (5)
Please log in to answer
Posted by:
airwolf
13 years ago
Well, the KBOX devices are just that: devices. They don't want everyone running around with root access breaking stuff. It would add a whole new subset of potential support issues if they opened up root access.
Posted by:
airwolf
13 years ago
Dell KACE support can SSH to it via tether - but that's only for remote support. We don't have access to using something like that - nor would we have proper credentials available for any local accounts. To my knowledge, you're not going to get any type of remote connectivity to the K2100 aside from the web console, file shares, and read-only ODBC.
Posted by:
trevzilla
10 years ago
Only problem is Kace support has been less than helpful and keep kicking it back to us and blaming our network. If we could look at a few things in the shell it would be a lot easier. Getting to the point where I just want to return the k1100, it's no use to us with half our hosts not connecting.
Comments:
-
Has your case been escalated to Tier 3? What is it you'd like to look at on the backend? We'd be more than happy to run network troubleshooting commands for you. Unfortunately, there is no supported method for a customer to gain root access. However, there are some commands you can run by logging in as the 'netdiag' user at the console. - airwolf 10 years ago
-
Nope, I'm dealing with a contact we were given right now and just asked to have someone tether on to look around. We used netdiag but we need to tracert and look at the routing table in the shell to be sure it's doing what we want it to (ie in the shell I can see what interface the route is using as we are concerned that it's trying to route some traffic out the wrong interface). It's very weird, we have one vlan that works perfect, our office vlan, but the production network with our servers doesn't connect.
I even have a virtualized test server that is connected to a trunk so I can pick which vlan I want it to use. As soon as I put it on the office vlan it could connect through the web browser instantly. I put it back to production and it hangs. The routing table statements are correct in the web interface, we have no internal firewall blocking anything. The fact that the k1 is a black box makes it very difficult since we can't look at traffic on both ends. I'm going to set up a mirrored switchport and run it to a server so we can at least look at wireshark.
All I can say is when I contacted support in the past they were pretty rude and just said it's your network, you fix the problem. Not helpful at all and I expected better support for a licensed appliance. - trevzilla 10 years ago-
Only Tier 3 support engineers can use a tether. You're in good hands. We can certainly give you the routing table info. If you are still hitting road blocks, feel free to request/insist the case be escalated to management and/or myself (Andy Flesner - Tier 3). I'm out for the holidays until Jan 2nd, but I can certainly take the case when I get back if you're willing to wait. Otherwise any other Tier 3 should be able to assist you in the mean time. - airwolf 10 years ago
-
alright airwolf, thanks for the feedback. - trevzilla 10 years ago
-
Have you tried replicating (port monitoring/mirroring) the port to a laptop with Wireshark so you can inspect the packets? You could issue a ping out from the Kace and see if your Wireshark catches it. - ammaross 10 years ago
-
Was about to set it up but then we figured out that there is something wrong with the routing table. When I set the appliance network settings gateway to our internal gateway which handles routing to all our internal vlans it connected to all our clients. But now the k1000 and k2000 can't get out to the internet.
So basically our routing table entries are supposed to handle sending traffic to our internal gateway when communicating with our internal network while the appliance goes out to the internet through our external gateway for everything else. The web gui entries are correct and identical to the same routes we put on each server.
If I could look at the shell and issue a route command I could get more detailed information not to mention a traceroute. I may still set up a mirror as "support" still hasn't got back to my ticket yet. And of course the usual nonsense of documenting their 10 or 15 steps which I've done before already before they'll even help me; and by help I mean being terse with me and telling me it's a networking problem and dumping it back in my lap without lifting a finger. If you're going to prevent sys admins from looking under the hood of the appliance then support should be faster and more responsive.
I'll post again when I set up a mirror just to see where our traffic is going. We suspect it's being sent out the wrong interface which would be easy enough to see if I could print out routing info in the shell. We could also fix it by specifying which interface we wanted the route to be assigned to. - trevzilla 10 years ago-
If you reference me in the ticket and tell them I've asked to take over the ticket, then I can assist you with troubleshooting tomorrow. Or you can post the ticket ID here and I'll take the case over myself. - airwolf 10 years ago
Posted by:
obakk
13 years ago
well thats just silly!
Comments:
-
If vendor support was rude to me, I'd be pulling the drives, plugging them into a generic Linux box, fooling about with mdraid until the filesystems checked OK, chrooting to them and running passwd for root. And if that broke anything I'd write a few thousand blocks of random gibberish to them, put them back in the appliance and return it under warranty. But that's just me. I'm not suggesting for a second that you do that. Oh dear no. - flabdablet 10 years ago
-
Your warranty would be void. Most likely in this case you'd just rebuild from ISO anyway, but our license prohibits your suggested course of action. - airwolf 10 years ago
-
It's obviously the kind of thing that *would* void the warranty on any device sold by a vendor who would employ rude support people, which is exactly why I didn't suggest it for a second. - flabdablet 10 years ago
-
I just wanted to make it clear that this behavior will void the warranty. - airwolf 10 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.