The 'traceroute' (unix) or 'tracert' (windows) command is very usefull
for diagnosing network problems. One example usage is (windows)
c:> tracert -d 64.233.187.104
This is one of the google servers/load balancers.
Each IP address you see is the next router/NAT device toward the destination
The switch will not show up. The '-d' keeps it from trying to resolve the
IPs into hostnames.
So if the PC is connected like this
Internet <-> MMDS Modem <-> VoipRouter <-> Xincom router <-> switch <-> PC
With the other wan disconnected and you see (Your IP addreses will be different)
C:> tracert 64.233.187.104
C:\Documents and Settings\Administrator>tra
Tracing route to www.l.google.com [64.233.187.99]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.102.1
2 25 ms 25 ms 25 ms 10.1.1.1
3 24 ms 24 ms 24 ms 172.16.32.32
4 69 ms 68 ms 68 ms 192.168.1.37
5 69 ms 68 ms 68 ms 23.10.45.22
6 72 ms 73 ms 72 ms 64.55.101.7
and on until it reaches the destination.
The first is the Xincom, number 2 will be the VOIP router,,
3 will probably be past the MMDS modem, at the first ISP router.
If traceroute works, but you can resolve hostnames, your problem is DNS.
Which is used to resolve hostnames into IP addresses. If this is the case
please post.
BTW: I hadn't seen the Xincom product, it looks useful, I too have 2 ISP's
but am currently using a Linux router to fill the role of the Xincom.
Main Topics
Browse All Topics
by: apparition0Posted on 2005-07-17 at 23:57:04ID: 14464080
What is the problem?
Assuming
Internet <-> MMDS Modem <-> VoipRouter <-> Xincom router
Is not working.
Can a normal computer or laptop use the MMDS modem directly?
Test by powering up MMDS, let it stablise for 1-2 minutes, then
connect a laptop or computer, and rebooting it. Can the computer
connect to the internet, or surf the web?
If that works, powering the MMDS on first and letting it stabalize for 1-2 minutes.
then plug in and power on the VOIP router, let it stablaize for 1-2 minutes.
Now can you make or receive calls on the VOIP router?
If that works, now plug in the Xincom, power it up, and let it stabalize for 1-2 minutes.
Test the Xincom, by connecting and having it test from menu's or plug in a computer
or laptop directly into its internal 4 port switch, (with the primary wan disconnected)
and see if the computer or laptop can reach the internet.
If that works, plug in the 24 port switch, to the Xincom, then plug the computer into the
switch. retest.
The '1-2 minutes to stablize is to let the machine powerup, boot, and negotiate
an IP address from the upstream device. Most devices can be told to do this
without powering off, but it is easier to do by power-cycling.
If you don't want to reboot the computer or laptop for each test, you can have it
request a new address for each test by going to the command line and typing
C:> ipconfig /release
C:> ipconfig /renew
This assumes
1. The machine is setup to use DHCP
2. It only has one (default) ethernet card/port.
Each network segment probably has a different NAT address. Only when the computer is
plugged directly into the MMDS modem, will you see your real address.
Also check when you plug in the ethernet cables, the lights for that port come on,
on both end devices. If they don't you may need a special 'crossover' ethernet cable.