Badly stuck - Need help!!!

boseytal

Hey all...

First of all I should start by saying - I am a student on work experience. I know a fair bit about the basics of networking, however I have ran into the following problem...

This morning, I was given an Expressway Service Management Platform (http://www.wancomm.com.au/resources/Expressway%20Datasheet.pdf), from a hotel our company services. The point of this is to get into the config to enable DHCP settings. The problem is - the IP address i was given to enter the product config (10.42.x.x) is wrong, or not working.

The engineer informed me that this IP address worked for him on site, but it obly gave him a limited amount of options (ie. Change Password etc) and no advanced options/TAB....

I am running an IP scanner at the mo, but as you can imagine it is painfully slow. I pinged the IP address given and its returning 100%.


Has anyone any suggestions as to my next step. Or am I making some silly beginners mistake??

Greatly appreciate any suggestions.


Joe.

boseytal

As regards not getting any advanced options in config, the engineer WAS logged in as administrator. I thought that may have been the problem myself.

Cheers.

rmacm

boseytal wrote: »

Hey all...
The point of this is to get into the config to enable DHCP settings. The problem is - the IP address i was given to enter the product config (10.42.x.x) is wrong, or not working.

I am running an IP scanner at the mo, but as you can imagine it is painfully slow. I pinged the IP address given and its returning 100%.

I take it you've got a laptop or something plugged into a port on this? When you say you pinged the address and its returning 100% is that 100% success or failure?

You should keep in mind that if this piece of kit has an IP like 10.42.x.x you'll need to configure your PC with a similar address to communicate with it.

E.g. if the box has an IP of 10.42.1.1 with a subnet mask of 255.255.255.0 you should set the IP address of your PC to something like 10.42.1.x (where x could be 2,3,4 etc.).

Let us know if you get anywhere or are still stuck.

FruitLover

boseytal wrote: »

I am running an IP scanner at the mo

What's this? Do you mean a port scanner? Do you see any ports open? Are you actually getting into any sort of management interface (e.g. telnet, web)? Does the thing have a serial port? If so, any response when connecting to it?

rmacm

FruitLover wrote: »

What's this?

Something like this http://www.angryziber.com/w/About (it's a port scanner too). It can be used on an entire subnet to see what IPs give a response to a ping and determine if there's something using that address.

Not totally reliable obviously e.g. if some devices on a network block ICMP.

TimTim

Get a copy of wireshark and plug a PC/laptop device of choice into the ethernet port of the device and sniff the ethernet traffic. Helped me figure out the IP of a unknown box.

Look for the ARP requests.

FruitLover

No reason an IP scanner should be slow, even on a /16. Nmap can do a ping sweep very quickly (don't think it waits for a response before sending the next ping). You'd want to check your ARP cache rather than relying on ping replies.

If you know the box has a management port on e.g. port 80, you might be quicker just doing a sweep on just that port (e.g. nmap -P0 10.42.0.0/16 -p 80).

boseytal

Correct me if I'm wrong, but if I connect the device to my PC via the ethernet ports, and do and ipconfig /renew & release, it should give me the IP of the device i'm looking at. Which it does. My IP comes in at 10.42.1.17, subnet mast of 255.255.255.0 and default gateway of 10.42.1.1... And when I ping the 10.42.1.1, it return 4 packets @ 0% loss. Problem is when I try and access it thru HTTP, I'm getting nothing.

There is also a serial port on the back of this device, which I have checked also, same story.

Ruaidhri

HI boseytal,

I'm assuming that you're using a URL in the form http://10.x.y.z. I'm just wondering if you were told to connect to a special port on the device, ie: not 80.
In that case your URL would be
http://<device ip>:<special port>/

Or, have your tried HTTPS:
https://<device ip>:<port>/

Regards,

Webmonkey

boseytal wrote: »

Correct me if I'm wrong, but if I connect the device to my PC via the ethernet ports, and do and ipconfig /renew & release, it should give me the IP of the device i'm looking at. Which it does. My IP comes in at 10.42.1.17, subnet mast of 255.255.255.0 and default gateway of 10.42.1.1... And when I ping the 10.42.1.1, it return 4 packets @ 0% loss. Problem is when I try and access it thru HTTP, I'm getting nothing.

There is also a serial port on the back of this device, which I have checked also, same story.

Well in that case it is clear that DHCP is working. You must also have communicated with it to obtain the IP addressing information.

There is no reason to say that ICMP is blocked by the device, hense no return replys from your pings.

Do you have a manual for this - you may have to go through https (SSL) rather than regular http, and further more it could be configured on a different port besides the default 8080.

EDIT: You say same problem with the serial port - how exactly? since this has nothing to do with TCP/IP - are you not getting a prompt on hyperterminal? - You may not have the correct settings to capture the output, perhaps baud/data bits is incorrect or you may be using the wrong COM port.

boseytal

Webmonkey wrote: »

Well in that case it is clear that DHCP is working. You must also have communicated with it to obtain the IP addressing information.

There is no reason to say that ICMP is blocked by the device, hense no return replys from your pings.

Do you have a manual for this - you may have to go through https (SSL) rather than regular http, and further more it could be configured on a different port besides the default 8080.

EDIT: You say same problem with the serial port - how exactly? since this has nothing to do with TCP/IP - are you not getting a prompt on hyperterminal? - You may not have the correct settings to capture the output, perhaps baud/data bits is incorrect or you may be using the wrong COM port.

I haven't actually tried to hook it up via serial port, but someone else has. And apparently there's still no access. You talked about ports there, could this be the problem... I'm after trying thru HTTPs and same story again.

Webmonkey

boseytal wrote: »

I haven't actually tried to hook it up via serial port, but someone else has. And apparently there's still no access. You talked about ports there, could this be the problem... I'm after trying thru HTTPs and same story again.

If you could get the manual for it - it would make life easy as you'll have all the information you need

boseytal

have it: http://10.42.1.1/mgmt

Thanks verymuch for your help.