Welcome to the Cox Community
Our community is a collaborative place to learn about Cox products and services. Jump into the conversation today!
Messages
Selected Messages
Our community is a collaborative place to learn about Cox products and services. Jump into the conversation today!
MikeyChris
+4 more
New Contributor II
•
59 Messages
Closed
Hello,
I have a Cox-supplied Cisco DPC3825 gateway (modem/router/switch). On the wired network there are two desktop computers (one running XP/SP3, the other Win 7 Pro 64 Bit), on the wireless there is a laptop (Win 7 32 bit), two scanner/printers, two iPhone and a Kindle tablet. Everything is working as far as the network (both wired and wireless). All devices can see and access files with each other (XP machine included). However, the XP machine cannot get to the internet. I can even log in to the gateway successfully with the XP machine.
This XP desktop stopped working years ago, and I just got it back online (there was no need before, now there is a need). I can't honestly say if it EVER worked on the Cox system. However, this has me confused. How can the XP machine see all the network devices, exchange files with them (as appropriate with the shares involved) but NOT see the internet? Since the gateway contains all the "magic", and the switch part obviously works, what am I missing?
Thanx for the help.
Discussions
•
Updated
3.6K
9
0
0
They don’t care
Discussions
1
0
Internet outage 24 hrs
Discussions
1
0
Wifi 7
Discussions
1
0
Can't login to new Panoramic Wifi Gateway
Discussions
2
0
Internet outage 24 hrs
Discussions
1
0
Wifi 7
Discussions
1
0
Frequent Outages
Discussions
2
Outages
Discussions
2
Accepted Solution
AllenP
+4 more
Valued Contributor
•
You have to connect the gateway for it to do it's "magic". Back in the XP days it wasn't as simple as plug and surf. Sounds like tcp/ip isn't configured correctly on the XP machine. It is possible you are sharing files with other devices on the network using netbios and not over tcp/ip. Check you tcp/ip setup:
- From Control Panel click Network Connections
- Right click on the local area connection and select Properties
- Make sure Internet Protocol (TCP/IP) is checked and click Properties
- On the general tab select Obtain an IP address automatically and Obtain DNS Server address automatically
Use OK to close all windows. If you made changes above, reboot to be sure the XP machine obtains an IP address via DHCP.
One other thing, make sure no firewall is running on the XP machine which may block internet access. Please let us know if this helps.
0
0
Tecknowhelp
Valued Contributor II
•
My guess is DNS. Can you ping out from the XP machine? Try both IP (8.8.8.8) and domain (cox.net). Start > Run > CMD > Ping cox.net. To copy the text, right click on top of CMD window and go to Edit > Select all and press enter. Then paste the result here. Edit anything you are not comfortable sharing.
0
0
AllenP
+4 more
Valued Contributor
•
Teck, reason I think tcp/ip is because MikeyChris posted "I can even log in to the gateway successfully with the XP machine." If he is trying to log in using the gateway's IP, he isn't using DNS at all.
0
0
DerrickW
Valued Contributor
•
It could be something simple like the settings on the XP machine. Have you tried to ping the default gateway? If you connect that XP machine directly to the cable modem are you able to get online? It sounds like the issue is specific to the machine so you will want to make sure your network settings are correct.
0
0
AllenP
+4 more
Valued Contributor
•
DerrickW, it's insulting to your customer when they take the time to post details, in this case, how to check a network config in XP, then you chime in with "want to make sure your network settings are correct." What was the purpose of that post? Did it add anything to the discussion?
0
0
MikeyChris
+4 more
New Contributor II
•
Allen - Thanx for the reply. Although your solution didn't actually fix the issue, it got me on the right path. The short answer is the gateway I.P. address was wrong! When we dropped DSL and switched to Cox (quite a while ago) the gateway address changed from 192.168.1.1 to 192.168.0.1 and somehow I missed that (years ago). When I entered ipconfig (CMD prompt) it was obvious the gateway and DHCP addresses were one number (1 -0) off.
Now, if I could just speed up the browser! Using either Chrome or IE is painful... (Win 7 and Win 8 machines OK).
Mike
0
0
MikeyChris
+4 more
New Contributor II
•
"My guess is DNS"
How can DNS affect a computer that can't see the internet? Thanx for the reply, but not getting the point. I guess I didn't post in original message that I had tried pinging, and only success was pinging the gateway itself.
0
0
MikeyChris
+4 more
New Contributor II
•
"Teck, reason I think tcp/ip is because MikeyChris posted "I can even log in to the gateway successfully with the XP machine." If he is trying to log in using the gateway's IP, he isn't using DNS at all."
That's what I thought too.
0
0
MikeyChris
+4 more
New Contributor II
•
"t could be something simple like the settings on the XP machine. Have you tried to ping the default gateway? If you connect that XP machine directly to the cable modem are you able to get online? It sounds like the issue is specific to the machine so you will want to make sure your network settings are correct."
Original post mentions I could login to gateway. You were correct, XP TCP/IP setting were off (Gateway address).
0
0