We have these 2 pbx boxes with hard-coded class C ip addresses, but we don't now what the are. What's the easiest way to find out? Im trying to use a network scanner but I'm unsuccessful so far. Im placing a pc on the same hub those pbx boxes are plug into. I assigned a ip address of 192.168.0.1 255.255.255.0 on the pc. With the ip scanner application i begin the scan at 192.168.0.1 to 192.168.254.0 still no luck, please help, thank you.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Finding ip address
- Thread starter 12122053
- Start date
- Thread starter
- #3
If you use the same hardware setup (using the hub and the computer) and if you use a packet sniffer that is able to see ALL traffic (for example Microsoft's Network Monitor provided with SMS or any other network sniffer), you should be able to *see* packets send by one of the routers. In these packets the IP-adres should be specified. It is important that you use a packet sniffer that is capable to use promicious mode, otherwise you won't see packets from 'other' networks.
Another option might be simple if these boxes also provide DHCP leases. If they are:
Setup the workstation to simply receive an ip address from an DHCP server.
Another option might be simple if these boxes also provide DHCP leases. If they are:
Setup the workstation to simply receive an ip address from an DHCP server.
Guest_imported
New member
- Jan 1, 1970
- 0
Here’s a free sniffer, probably the best public domain sniffer available,
Dave
Dave
Guest_imported
New member
- Jan 1, 1970
- 0
Help!!!
I am desperately trying to find the answer to one question. I would really appreciate if you could help me.
What is the difference between loopback test and pinging your own IP address in terms of what the host does? And where does the packet goes in the TCP IP stack? In both cases it should not leave the host’s network interface card. Isn’it? When you ping your IP address, does IP use loopback drivers to reroute outgoing packets back to the source computer? (like in the loopback test) What is the difference?
Where does IP resolves the destination IP address of the packet to the destination MAC address when a packet is sent by a host to itself? I know IP addresses are mapped to MAC addresses in every computer but how does IP get to know the MAC address?
This is my interpretation (probably wrong!):
Once the packet goes down to the Data Link layer, TCP IP finds corresponding MAC address for that IP address as the network interface card has been mapped to that IP address. At this point the packet is passed back up the stack again for processing at the same host.
So only at the Data Link layer, where MAC addresses are recognized by TCP IP, the host identifies that the packet is addresses to itself.
Can you help at all? Thank you so much for your time.
I am desperately trying to find the answer to one question. I would really appreciate if you could help me.
What is the difference between loopback test and pinging your own IP address in terms of what the host does? And where does the packet goes in the TCP IP stack? In both cases it should not leave the host’s network interface card. Isn’it? When you ping your IP address, does IP use loopback drivers to reroute outgoing packets back to the source computer? (like in the loopback test) What is the difference?
Where does IP resolves the destination IP address of the packet to the destination MAC address when a packet is sent by a host to itself? I know IP addresses are mapped to MAC addresses in every computer but how does IP get to know the MAC address?
This is my interpretation (probably wrong!):
Once the packet goes down to the Data Link layer, TCP IP finds corresponding MAC address for that IP address as the network interface card has been mapped to that IP address. At this point the packet is passed back up the stack again for processing at the same host.
So only at the Data Link layer, where MAC addresses are recognized by TCP IP, the host identifies that the packet is addresses to itself.
Can you help at all? Thank you so much for your time.
- Status
Similar threads
- Locked
- Question
- Locked
- Question