I also have a Vonage Linksys router connected to the Dlink router for my Vonage phone service.
remission,
Depending on how the Linksys is configured (which model is it?), it may be one more router than you need. If all the equipment is being serviced from the D-Link router, why not just connect the D-Link directly to the Ethernet cable coming from the cable modem?
I'lI am at work now, I'll have to look at the Vonage Linksys router when I get home.
I do have the Cable modem connected right to the WAN/Internet port on the Dlink router, then it provides internet service to the other 3 ports that are connected to the Linksys router, the PC and the Mac.
I have to have the Linksys router for my Vonage phone service, that is where the phone plugs into.
Depending on how the Linksys is configured (which model is it?), it may be one more router than you need. If all the equipment is being serviced from the D-Link router, why not just connect the D-Link directly to the Ethernet cable coming from the cable modem?
Ah! Is it VOIP? We'll still need to take a look at the Linksys device, since it may be supplying IP addresses to the devices directly connected to it. If so, the network could be partitioned into two parts, one serviced by the DHCP server in the D-Link, and another serviced by the DHCP server in the Linksys.
Yes it is VOIP for my Vonage, the router it uses is a Linksys RT31P2 Broadband Router with 2 phone ports. I have not tried the connection without it hooked into the router because I need my phone service.
There is nothing connected to the Linksys router but my phone. The router is connected to one of the numbers ports on the Wireless router
I am not sure how to look at the DCHP and IP address stuff you said.
I have another question about physical connections. Is the Linksys RT31P2's "Internet" port connected to one of the LAN ports on the DI-514, or is one of the three LAN Ethernet ports on the Linksys connected to one of the D-Link's numbered ports?
The routing situation is a bit unusual. The DHCP server on the D-Link assigns IP addresses in the range 192.168.0.100 through 192.168.0.254, with a subnet mask of 255.255.255.0. Its own IP address on the LAN side is 192.168.0.1. The DHCP server on the Linksys is disabled by default. As a result, I'm not sure what IP address is being assigned to the VOIP service! Since that seems to be working properly, we should be able to ignore that issue for now. Linksys's manual pretty clearly expects the RT31P2's "Internet" port to be directly connected to the cable or DSL modem, though.
You said the MAC works correctly "either way". By "either" what is the "other" way you're referring to? One way is a connection to the D-Link, but I'm not sure what the other one is.
The commonest problem with PCs and the D-Link wireless routers is the fact that the D-Link's "preamble length" defaults to "short". Changing that setting to "long" (on Advanced/Performance in the DI-514) ususally resolves that problem. But yours is different in that both the wireless and wired PCs are having problems staying connected. The timing of the connection loss makes it sound like both the wireless and wired adapters are set to shut down to conserve power. Both those settings should be changed to "always on". The MAC may not have a similar setting, which could explain the differerent behavior.
Is the DI-514 firmware current? According to the D-Link Web site, the current version is 2.04, released on 14 July 2004. If yours isn't current, you should update to the latest version.
Let's use the wired PC for some more troubleshooting. What Operating System and Service Pack is installed on it? What Dell model is it? What model Ethernet adapter is installed in it?
When it's operating properly, you should be able to ping the IP address of the "Default Gateway" as shown in the output of "ipconfig /all". To obtain that output, open a cmd.exe window (Start/Run cmd.exe). In the window that opens, type
ipconfig /all. I expect the "Default Gateway" will be 192.168.0.1, the default LAN address of the DI-514. If that's not the value you see, note the IP address listed as the "Default Gateway". Either way, post all of the output received from "ipconfig /all" into a reply to this message so we can have it as a refererence. If the gateway's IP address is 192.168.0.1, you should be able to "ping" that IP address by typing
ping 192.168.0.1 in a cmd.exe window. Otherwise, "ping" the IP address listed as the "Default Gateway". You should receive three responses and no timeouts. Also try pinging the DSL Reports Web site by typing
ping www.dslreports.com. You should receive three responses and no timeouts.
Now, when you're having trouble with the connections, repeat the two ping experiments and report the results. That will tell us whether the connection between the wired PC and the D-Link is being lost, or whether the problem lies closer to the cable modem.
If you have any questions, or need anything clarified, please post back!
Yes I have the ethernet cable from the Vonage Linksys router connected from it's WAN/Internet port going to one of the Lan ports on the D-LINK Router. Nothing is connected to the Linksys Lan ports.
I can try calling Vonage and having them look and see if the IP addresses are conflicting but would not be able to unplug the router or anything since I will lose my phone connection once internet goes down.
Im not sure how look and see if the Vonage router is being assigned a specific IP address diff from the Dlink, would this not be in the Routers settings on the website?
Yea the Linksys should be directly connected to the modem, except if I am using a situation such as this for wireless, then it should not have to, since it iss till reciving internet through the hub, this is how Vonage told me to set it up, it should get assined the same IP address as the Dlink is and the Comcast is.
The Mac works however I set it up, by itself, or connected right to the modem, connected to the Linksys or to the Dlink, it allways works. It seems to be a Windows problem.
Mac's are pretty straight forward anyways using the internet, plug it in and it works lol
I have turned off the settings on the NIC card and in power management so it doesnt shut down when idle or when power is low.
I have updated all the firmware and drivers on both computers for Nic card, cable modem and all my other hardware.
The PC I have is one I built myself, The Dell is the laptop.
On the PC I am using Windows XP Home, I am not using Service Pack 6, I think it is 5.5 or whichever is the newest one besides 6. I tried 6 and had so many problems I uninstalled it.
The PC that is wired to the router uses a VIA Rhine 2 Fast ethernet adapter.
I also have a ADMTEK AN983 BASED ETHERNET ADAPTER. but i dont use it for my
connection.
The VIA Rhine 2 nic is connected to the MOBO and the other one is a ethernet
card, not sure which one is which.
One the laptop, I am not sure the model of the card, I know it is one that Dell
put in it, I think it is a Broadcom wireless card.
I will try to also PING the IP address when I get home.
I did have one error message that came up the other day, stating that the IP address had a confilic with another IP address on the system, it was a windows message but it went away and I never saw it again. I was thinking MAYBE it was between the routers and wireless router but not sure, Ill have to chedj with Vonage for the IP info also
I'll also disconnect the Vonage and see if it gives me the same problem.
You should be able to connect the Vonage/Linksys directly to the cable modem without losing phone service. You'll need to turn off the cable modem for about five minutes after disconnecting it from the D-Link, so it "forgets" the hardware Ethernet address of the D-Link. After that, turn the cable modem back on and wait for it to establish a connection to the cable system. Then connect the Vonage/Linksys Internet port directly to the cable modem, and turn the Linksys back on. That should allow the phone connection to work. Obviously nothing connected to the D-Link will work at that point (except perhaps locally), since the D-Link will no longer be connected to the Internet.
I'm actually surprised that the MAC works when connected to the Linksys. In the RT31P2's default configuration, the MAC should not be able to receive an IP address from the Linksys, since the Linksys's DHCP server is disabled by default. Note that I'm assuming that all three machines are set up to receive an IP address "automatically" from a DHCP server. Is that a correct assumption? If it isn't, what IP addresses, subnet masks, and default gateways are being manually assigned to each of the three machines? All that information is summarized in the "ipconfig /all" output I described in my last post. It would be helpful if you could post that output from both of the Windows machines. I'm not sure how to obtain it from the MAC. I think the method depends on which MacOS version you're running. It would be useful to have that same information from the MAC, if you can figure out how to get it.
Which Dell model is the laptop? Is it also running XP Home? The most recent Service Pack for XP is Service Pack 2. While it's caused problems for some people, it contains many important security updates, and includes some very significant improvements to XP's wireless capabilities. There were also some significant fixes to XP wireless support introduced after XP Service Pack 1. Here's a
Microsoft article describing that update. It's also available as part of Service Pack 2, but, as the article says, it's also available separately.
The "duplicate IP address" error message could well be significant. That event should have been logged in the "Event Log" of the PC that reported the problem. You can view the Event Log by starting the Event Viewer. That's most easily done by "Start/Run eventvwr.msc". Look in the Application and System event logs for any network or DHCP related errors. If you find that error message, or other network-related "warning" or "error" messages, please report their entire contents. Note that if you double-click on an event, a "properties" window opens showing the error message. If you click on the bottom button on the right side of that window (the one that looks like two pieces of paper), the error message will be transferred to the Windows clipboard. You can then paste the message text into a reply.
It would be very useful to know what the "Internet" IP addresses in both the D-Link and the Linksys/Vonage are. Perhaps Vonage can help you obtain it. The D-Link's built-in Web server can display it. See the "Status/Device Info" display from the D-Link.
My Mistake, I don't think I had the Mac connected to the Linksys router, just the D-link router.
Yes, The IP address is set to Auto Receive from DHCP service on my computers.
I guess I can do the Linksys set up you said and then just plug one of the computers into the LAN port on the Linksys to use the web so they can troouble shoot the D-link if needed.
None of the machine have anything manualy assgned to them, everything is automatic with a dynamic IP address.
The Dell is a 5100 Inspiron also running Windows XP Home. I am pretty sure that I dont have Service pack 6 on it , just 5.x. That pack seems to allways mess up. But maybe Ill reinstall it again, I can allways do the XP rollback if it messes up again. See if maybe that helps with the wireless.
I'll check the IP info and the Error message info when I get home tonight and post it all
I am emailing Dlink tech support also, and I asked them about the access point issue, Not sure if it can be used since they have other routers that are access points as well. This is just a basic wireless router. Hopefully I can get them on the phone and see what they say. But I'll be sure to post the info about IP address later tonight .
Many of the wireless routers can be reconfigured to act as access points, but I didn't see anything in the DI-514 manual that said it was one of them. We'll see what D-Link has to say...
"Two-router" problems can be challenging. This one has an interesting twist, VOIP, that I'm sure we'll be seeing again!
By the way, do incoming calls work OK in that configuration? I'm honestly not sure how they would!
I don't think I had the Mac connected to the Linksys router, just the D-link router.
OK, so the "other" device is probably a direct connection to the cable modem? Yes, I'd expect both of those to work...but with the D-Link and Vonage/Linksys disconnected, of course only the Mac would be able to connect to the Internet.
I just found another section of the Linksys manual (Page 6) that says that the Linksys's DHCP server
is enabled by default. You should be able to confirm that by plugging one of the PCs in to one of the LAN ports on the Linksys, and trying to renew the PC's IP address. The default IP address of the Linksys on the LAN side is 192.168.15.1, with a subnet mask of 255.255.255.0. Its DHCP server will assign fifty IP addresses beginning with 192.168.15.100.
Please note that the most recent Service Pack for XP is Service Pack 2. I'm not sure what service pack information you're seeing that reports a Service Pack 5, but it's not XP. The major caveat on Service Pack 2 is to make sure that the machine it's being installed on is free of all viruses and malware before attempting the update. Since both the wireless laptop and the wired PC are exhibiting similar problems, I don't suggest installing Service Pack 2 on either machine until we figure out what's going on.
The "conventional" setup for a network like yours would be to have the Linksys connected to the cable modem, the DHCP server in the Linksys enabled, and the "other" router reconfigured to act as an access point. That way, anything connected to the "other" router would receive its IP address from the Linksys. As far as I've been able to determine, the DI-514 can't be configured as an access point, so we need to be very certain we know what's wrong before trying to deal with the issue of how the DI-514 works.
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Ping statistics for 192.168.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
C:\Documents and Settings\mike>
Also, i was reading my VONAGE book and it says the DHCP on the LAN end, is enabled by default,
and If I use another hardware with it I must disable one of them or I'll have IP ADDY conflicts, so maybe I have to disable the DHCP server in one of them, but which one? but you said in your last message it is disabled by default..
Also in the Vonage book, it says the Routers default IP address is the 192.168.1.15 , the same as the gateway above. But when I type that in explorer to try to access the Admin screen to config the Linksys router it wont go and times out.
When I type in /192.168.0.1 to access the D-LINK ROUTER it lets me go there though.
Here is the info from the screen when I access the DLINK ROUTER, It looks to me like the DHCP server is enabled here also.
IP Address
192.168.0.1
Subnet Mask
255.255.255.0
DHCP Server
Enabled
WAN
MAC Address
00-50-2C-02-9B-04
Connection
DHCP Client Connect
IP Address
69.143.39.116
Subnet Mask
255.255.248.0
Default Gateway
69.143.32.1
DNS
68.42.244.5 68.42.244.6
OK, I can now access the linksys ruter!!!! And DHCP IS ENABLED on there also
Optional Settings
(required by some ISPs) Host Name:
Domain Name:
MTU: Enable Disable Size:
Network Setup
Router IP Local IP Address: . . .
Subnet Mask:
Network Address
Server Settings (DHCP) Local DHCP Server: EnableDisable
Start IP Address: 192.168.15.
Number of Address:
DHCP Address Range: 192.168.15.100 to 192.168.15.149
Client Lease Time: minutes (0 means one day)
DNS 1: . . .
DNS 2: . . .
DNS 3: . . .
WINS: . . .
So.. now i just need to know what to do next, I assume I need to choose which one to use as the DHCP server and what else??
Well, that set of results tells the story clearly, doesn't it? When the PC is first booted, it obtains its IP address from the DI-524, as expected. But, some time after that, it receives an IP address from the LINKSYS instead! We know that because the DHCP server in the Linksys issues IP addresses beginning with 192.168.
15.100, and the D-Link's range begins with 192.168.
1.100.
That suggests that the PC is renewing its IP address in an unexpected way. There may be more to it than this, but the next step is to go into the Linksys and disable its DHCP server. There's nothing that should be receiving an IP address from the Linksys as things stand now. And the reason things work "for a while" is that the IP address received by the PC is coming from one device (the D-Link), and then it later receives one from the Linksys.
While you're turning off the DHCP server in the Linksys, could you look at the "Router Status" tab and report the Internet IP Address, Subnet Mask, and Default Gateway it's using? That tab is described on Page 43 of the manual - in the PDF file, it's Page 51.
Regarding whether the DHCP server in the Linksys is enabled by default or not, I'd earlier found a note that said it wasn't. But after going through most of the manual, it was clear that it is enabled by default...and indeed it is!
(edit) The "more to it" issue that I mentioned above is the possibility that the Linksys is sending out routing information on its LAN port, and that information is confusing either the D-Link or the PC or both of them. While everything's working, can you collect the output of
netstat -r from a cmd.exe window, save it, and repeat that step if problems again develop? That will display the PC's routing table.
Ok, I disabled the DHCP on the Vonage Linksys router, but now when it is connected I cannot log into the router when I type in the 192.168.15.1 . it just times out, i have to totaly unplug evrything and plug it directly into the linksys without the DLINK. Then the phone stops working without multiple restarts.
I did the netstat -r, here is the stats of that, Ill see if the disabling of the DHCP worked later when it is idle.
I am moving into a townhouse soon, so I think im not going to use the vonage, it is cheaper by a lot, but not worth the constant hassle. I guess it would be good with just a basic setup, but anything else is a hassle heh
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
jwatt
4.4K Posts
0
May 10th, 2005 19:00
remission,
Depending on how the Linksys is configured (which model is it?), it may be one more router than you need. If all the equipment is being serviced from the D-Link router, why not just connect the D-Link directly to the Ethernet cable coming from the cable modem?
Jim
remission
24 Posts
0
May 10th, 2005 19:00
jwatt
4.4K Posts
0
May 10th, 2005 23:00
Ah! Is it VOIP? We'll still need to take a look at the Linksys device, since it may be supplying IP addresses to the devices directly connected to it. If so, the network could be partitioned into two parts, one serviced by the DHCP server in the D-Link, and another serviced by the DHCP server in the Linksys.
Jim
remission
24 Posts
0
May 11th, 2005 01:00
There is nothing connected to the Linksys router but my phone. The router is connected to one of the numbers ports on the Wireless router
I am not sure how to look at the DCHP and IP address stuff you said.
jwatt
4.4K Posts
0
May 11th, 2005 05:00
I have another question about physical connections. Is the Linksys RT31P2's "Internet" port connected to one of the LAN ports on the DI-514, or is one of the three LAN Ethernet ports on the Linksys connected to one of the D-Link's numbered ports?
The routing situation is a bit unusual. The DHCP server on the D-Link assigns IP addresses in the range 192.168.0.100 through 192.168.0.254, with a subnet mask of 255.255.255.0. Its own IP address on the LAN side is 192.168.0.1. The DHCP server on the Linksys is disabled by default. As a result, I'm not sure what IP address is being assigned to the VOIP service! Since that seems to be working properly, we should be able to ignore that issue for now. Linksys's manual pretty clearly expects the RT31P2's "Internet" port to be directly connected to the cable or DSL modem, though.
You said the MAC works correctly "either way". By "either" what is the "other" way you're referring to? One way is a connection to the D-Link, but I'm not sure what the other one is.
The commonest problem with PCs and the D-Link wireless routers is the fact that the D-Link's "preamble length" defaults to "short". Changing that setting to "long" (on Advanced/Performance in the DI-514) ususally resolves that problem. But yours is different in that both the wireless and wired PCs are having problems staying connected. The timing of the connection loss makes it sound like both the wireless and wired adapters are set to shut down to conserve power. Both those settings should be changed to "always on". The MAC may not have a similar setting, which could explain the differerent behavior.
Is the DI-514 firmware current? According to the D-Link Web site, the current version is 2.04, released on 14 July 2004. If yours isn't current, you should update to the latest version.
Let's use the wired PC for some more troubleshooting. What Operating System and Service Pack is installed on it? What Dell model is it? What model Ethernet adapter is installed in it?
When it's operating properly, you should be able to ping the IP address of the "Default Gateway" as shown in the output of "ipconfig /all". To obtain that output, open a cmd.exe window (Start/Run cmd.exe). In the window that opens, type ipconfig /all. I expect the "Default Gateway" will be 192.168.0.1, the default LAN address of the DI-514. If that's not the value you see, note the IP address listed as the "Default Gateway". Either way, post all of the output received from "ipconfig /all" into a reply to this message so we can have it as a refererence. If the gateway's IP address is 192.168.0.1, you should be able to "ping" that IP address by typing ping 192.168.0.1 in a cmd.exe window. Otherwise, "ping" the IP address listed as the "Default Gateway". You should receive three responses and no timeouts. Also try pinging the DSL Reports Web site by typing ping www.dslreports.com. You should receive three responses and no timeouts.
Now, when you're having trouble with the connections, repeat the two ping experiments and report the results. That will tell us whether the connection between the wired PC and the D-Link is being lost, or whether the problem lies closer to the cable modem.
If you have any questions, or need anything clarified, please post back!
Jim
Message Edited by jimw on 05-10-2005 11:19 PM
remission
24 Posts
0
May 11th, 2005 15:00
I can try calling Vonage and having them look and see if the IP addresses are conflicting but would not be able to unplug the router or anything since I will lose my phone connection once internet goes down.
The Mac works however I set it up, by itself, or connected right to the modem, connected to the Linksys or to the Dlink, it allways works. It seems to be a Windows problem.
Mac's are pretty straight forward anyways using the internet, plug it in and it works lol
I have updated all the firmware and drivers on both computers for Nic card, cable modem and all my other hardware.
connection.
card, not sure which one is which.
One the laptop, I am not sure the model of the card, I know it is one that Dell
put in it, I think it is a Broadcom wireless card.
jwatt
4.4K Posts
0
May 11th, 2005 16:00
You should be able to connect the Vonage/Linksys directly to the cable modem without losing phone service. You'll need to turn off the cable modem for about five minutes after disconnecting it from the D-Link, so it "forgets" the hardware Ethernet address of the D-Link. After that, turn the cable modem back on and wait for it to establish a connection to the cable system. Then connect the Vonage/Linksys Internet port directly to the cable modem, and turn the Linksys back on. That should allow the phone connection to work. Obviously nothing connected to the D-Link will work at that point (except perhaps locally), since the D-Link will no longer be connected to the Internet.
I'm actually surprised that the MAC works when connected to the Linksys. In the RT31P2's default configuration, the MAC should not be able to receive an IP address from the Linksys, since the Linksys's DHCP server is disabled by default. Note that I'm assuming that all three machines are set up to receive an IP address "automatically" from a DHCP server. Is that a correct assumption? If it isn't, what IP addresses, subnet masks, and default gateways are being manually assigned to each of the three machines? All that information is summarized in the "ipconfig /all" output I described in my last post. It would be helpful if you could post that output from both of the Windows machines. I'm not sure how to obtain it from the MAC. I think the method depends on which MacOS version you're running. It would be useful to have that same information from the MAC, if you can figure out how to get it.
Which Dell model is the laptop? Is it also running XP Home? The most recent Service Pack for XP is Service Pack 2. While it's caused problems for some people, it contains many important security updates, and includes some very significant improvements to XP's wireless capabilities. There were also some significant fixes to XP wireless support introduced after XP Service Pack 1. Here's a Microsoft article describing that update. It's also available as part of Service Pack 2, but, as the article says, it's also available separately.
The "duplicate IP address" error message could well be significant. That event should have been logged in the "Event Log" of the PC that reported the problem. You can view the Event Log by starting the Event Viewer. That's most easily done by "Start/Run eventvwr.msc". Look in the Application and System event logs for any network or DHCP related errors. If you find that error message, or other network-related "warning" or "error" messages, please report their entire contents. Note that if you double-click on an event, a "properties" window opens showing the error message. If you click on the bottom button on the right side of that window (the one that looks like two pieces of paper), the error message will be transferred to the Windows clipboard. You can then paste the message text into a reply.
It would be very useful to know what the "Internet" IP addresses in both the D-Link and the Linksys/Vonage are. Perhaps Vonage can help you obtain it. The D-Link's built-in Web server can display it. See the "Status/Device Info" display from the D-Link.
Jim
remission
24 Posts
0
May 11th, 2005 16:00
Yes, The IP address is set to Auto Receive from DHCP service on my computers.
I'll check the IP info and the Error message info when I get home tonight and post it all
Thanks
remission
24 Posts
0
May 11th, 2005 17:00
jwatt
4.4K Posts
0
May 11th, 2005 17:00
Many of the wireless routers can be reconfigured to act as access points, but I didn't see anything in the DI-514 manual that said it was one of them. We'll see what D-Link has to say...
"Two-router" problems can be challenging. This one has an interesting twist, VOIP, that I'm sure we'll be seeing again!
By the way, do incoming calls work OK in that configuration? I'm honestly not sure how they would!
Jim
jwatt
4.4K Posts
0
May 11th, 2005 17:00
I don't think I had the Mac connected to the Linksys router, just the D-link router.
OK, so the "other" device is probably a direct connection to the cable modem? Yes, I'd expect both of those to work...but with the D-Link and Vonage/Linksys disconnected, of course only the Mac would be able to connect to the Internet.
I just found another section of the Linksys manual (Page 6) that says that the Linksys's DHCP server is enabled by default. You should be able to confirm that by plugging one of the PCs in to one of the LAN ports on the Linksys, and trying to renew the PC's IP address. The default IP address of the Linksys on the LAN side is 192.168.15.1, with a subnet mask of 255.255.255.0. Its DHCP server will assign fifty IP addresses beginning with 192.168.15.100.
Please note that the most recent Service Pack for XP is Service Pack 2. I'm not sure what service pack information you're seeing that reports a Service Pack 5, but it's not XP. The major caveat on Service Pack 2 is to make sure that the machine it's being installed on is free of all viruses and malware before attempting the update. Since both the wireless laptop and the wired PC are exhibiting similar problems, I don't suggest installing Service Pack 2 on either machine until we figure out what's going on.
The "conventional" setup for a network like yours would be to have the Linksys connected to the cable modem, the DHCP server in the Linksys enabled, and the "other" router reconfigured to act as an access point. That way, anything connected to the "other" router would receive its IP address from the Linksys. As far as I've been able to determine, the DI-514 can't be configured as an access point, so we need to be very certain we know what's wrong before trying to deal with the issue of how the DI-514 works.
Jim
remission
24 Posts
0
May 13th, 2005 22:00
The default gateway received 0 packets back, but the IP address and DHCP Server received all the packets I sent .
Here is the info from the IP /ALL
Windows IP Configuration
Host Name . . . . . . . . . . . . : mike-ufy48bzfsp
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Local Area Connection:
Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : VIA Rhine II Fast Ethernet Adapter
Physical Address. . . . . . . . . : 00-50-2C-02-9B-04
Ethernet adapter Local Area Connection 2:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : ADMtek AN983 based ethernet adapter
Physical Address. . . . . . . . . : 00-50-BF-97-42-A8
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.15.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.15.1
DHCP Server . . . . . . . . . . . : 192.168.15.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
Lease Obtained. . . . . . . . . . : Friday, May 13, 2005 7:01:58 PM
Lease Expires . . . . . . . . . . : Saturday, May 14, 2005 7:01:58 PM
C:\Documents and Settings\mike>
AND HERE is the same info AFTER I restart my computer and get my internet working, you can see that the info has changed.
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\mike>IPCONFIG /ALL
Windows IP Configuration
Host Name . . . . . . . . . . . . : mike-ufy48bzfsp
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Local Area Connection:
Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : VIA Rhine II Fast Ethernet Adapter
Physical Address. . . . . . . . . : 00-50-2C-02-9B-04
Ethernet adapter Local Area Connection 2:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : ADMtek AN983 based ethernet adapter
Physical Address. . . . . . . . . : 00-50-BF-97-42-A8
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.102
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
Lease Obtained. . . . . . . . . . : Friday, May 13, 2005 7:14:13 PM
Lease Expires . . . . . . . . . . : Friday, May 20, 2005 7:14:13 PM
C:\Documents and Settings\mike>PING 192.168.0.1
Pinging 192.168.0.1 with 32 bytes of data:
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Ping statistics for 192.168.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
C:\Documents and Settings\mike>
Also, i was reading my VONAGE book and it says the DHCP on the LAN end, is enabled by default,
and If I use another hardware with it I must disable one of them or I'll have IP ADDY conflicts, so maybe I have to disable the DHCP server in one of them, but which one? but you said in your last message it is disabled by default..
Also in the Vonage book, it says the Routers default IP address is the 192.168.1.15 , the same as the gateway above. But when I type that in explorer to try to access the Admin screen to config the Linksys router it wont go and times out.
When I type in /192.168.0.1 to access the D-LINK ROUTER it lets me go there though.
Here is the info from the screen when I access the DLINK ROUTER, It looks to me like the DHCP server is enabled here also.
IP Address
192.168.0.1
Subnet Mask
255.255.255.0
DHCP Server
Enabled
WAN
MAC Address
00-50-2C-02-9B-04
Connection
DHCP Client Connect
IP Address
69.143.39.116
Subnet Mask
255.255.248.0
Default Gateway
69.143.32.1
DNS
68.42.244.5 68.42.244.6
OK, I can now access the linksys ruter!!!! And DHCP IS ENABLED on there also
here is the LINKSYS info
Firmware Version: 1.28.00
Setup
Broadband Router with 2 Phone Ports RT31P2
Setup Security Voice Applications
& Gaming Administration
Status
Basic Setup
DDNS
MAC Address Clone
Advanced Routing
Internet Setup
Internet Connection Type
Optional Settings
(required by some ISPs) Host Name:
Domain Name:
MTU: Enable Disable Size:
Network Setup
Router IP Local IP Address: . . .
Subnet Mask:
Network Address
Server Settings (DHCP) Local DHCP Server: EnableDisable
Start IP Address: 192.168.15.
Number of Address:
DHCP Address Range: 192.168.15.100 to 192.168.15.149
Client Lease Time: minutes (0 means one day)
DNS 1: . . .
DNS 2: . . .
DNS 3: . . .
WINS: . . .
So.. now i just need to know what to do next, I assume I need to choose which one to use as the DHCP server and what else??
thanks :)
remission
24 Posts
0
May 13th, 2005 22:00
IP ADDRESS 192.168.15.1
SUBNET MASK 255.255.255.0
Local DHCP SERVER : ENABLED
start ip address : 192.168.15.100
# of address = 50
DHCP Address Range: 192.168.15.100 to 192.168.15.149
MTU is DISABLED
It is set to OBTAIN IP ADDRESS AUTOMATICLY
jwatt
4.4K Posts
0
May 14th, 2005 00:00
Well, that set of results tells the story clearly, doesn't it? When the PC is first booted, it obtains its IP address from the DI-524, as expected. But, some time after that, it receives an IP address from the LINKSYS instead! We know that because the DHCP server in the Linksys issues IP addresses beginning with 192.168. 15.100, and the D-Link's range begins with 192.168. 1.100.
That suggests that the PC is renewing its IP address in an unexpected way. There may be more to it than this, but the next step is to go into the Linksys and disable its DHCP server. There's nothing that should be receiving an IP address from the Linksys as things stand now. And the reason things work "for a while" is that the IP address received by the PC is coming from one device (the D-Link), and then it later receives one from the Linksys.
While you're turning off the DHCP server in the Linksys, could you look at the "Router Status" tab and report the Internet IP Address, Subnet Mask, and Default Gateway it's using? That tab is described on Page 43 of the manual - in the PDF file, it's Page 51.
Regarding whether the DHCP server in the Linksys is enabled by default or not, I'd earlier found a note that said it wasn't. But after going through most of the manual, it was clear that it is enabled by default...and indeed it is!
(edit) The "more to it" issue that I mentioned above is the possibility that the Linksys is sending out routing information on its LAN port, and that information is confusing either the D-Link or the PC or both of them. While everything's working, can you collect the output of netstat -r from a cmd.exe window, save it, and repeat that step if problems again develop? That will display the PC's routing table.
Jim
Message Edited by jimw on 05-13-2005 07:04 PM
remission
24 Posts
0
May 14th, 2005 02:00
I did the netstat -r, here is the stats of that, Ill see if the disabling of the DHCP worked later when it is idle.
I am moving into a townhouse soon, so I think im not going to use the vonage, it is cheaper by a lot, but not worth the constant hassle. I guess it would be good with just a basic setup, but anything else is a hassle heh
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\mike> netstat -r
Route Table
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 50 2c 02 9b 04 ...... VIA PCI 10/100Mb Fast Ethernet Adapter - Packet
Scheduler Miniport
0x3 ...00 50 bf 97 42 a8 ...... ADMtek AN983 based ethernet adapter - Packet Sch
eduler Miniport
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.0.1 192.168.0.102 20
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.0.0 255.255.255.0 192.168.0.102 192.168.0.102 20
192.168.0.102 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.0.255 255.255.255.255 192.168.0.102 192.168.0.102 20
224.0.0.0 240.0.0.0 192.168.0.102 192.168.0.102 20
255.255.255.255 255.255.255.255 192.168.0.102 192.168.0.102 1
255.255.255.255 255.255.255.255 192.168.0.102 2 1
Default Gateway: 192.168.0.1
===========================================================================
Persistent Routes:
None
C:\Documents and Settings\mike>