MachinimatorMLG
New Member
- Joined
- Jun 11, 2010
- Messages
- 52
DHCP is disabled on the router. We can't use DHCP. Period.Try letting the DHCP server automatically assign your computer the IP address. It could be for whatever reason the router isn't accepting your entered values.
Okay, I'll check the computer I'm posting from right now. How do I do so on WindowsXP?They don't have to be running Windows 7 - you just need to be able to compare the IP configuration settings on this pc with those of another which is successfully connecting to see if there is any differences which would help explain the problem.
It's never worked on anything other than set to Public. I tried to set it to the other options when I initially configured the system but the configuration wouldn't even finish. I don't remember the exact details, but I do remember that the setup wouldn't even accept any choice but Public.If you network is being shown as a public network (bench), then it is handled differently than a Home network. Look at the Windows Firewall to see the difference. I would suggest you open the Network and Sharing Center, click on the link to set your network as a Home network. A Public Network is like Starbucks and is normally more restricted.
Obviously.If you are assigning your own IP addresses, does that include the DNS addresses also.
It concerns me that you cannot set your network to Home. Public networks are usually computers connected directly to the internet. I have seen that type of problem if the IP addresses being used were not part of the home network. You are sure the router address is x.x.1.1?It's never worked on anything other than set to Public. I tried to set it to the other options when I initially configured the system but the configuration wouldn't even finish. I don't remember the exact details, but I do remember that the setup wouldn't even accept any choice but Public.
As I stated several posts ago, I already tried that. I can access the router (by putting the IP adress in as a URL) from every computer except the one I'm having the problem with. That was one of the first things I checked. So, no, it's NOT. THE. ROUTER.You state your Network and Sharing center has a red x after the park bench (see attachment). The only way I can duplicate this is by disconnecting my cable modem from the router. So it would seem you are getting to the router, but not beyond it. There are ways you can check this, like pinging the router or putting its IP address in a browser as a URL.
How could that even be possible, though? Wouldn't that sort of thing have caused all sorts of other problems a long time ago? And how would that in any way explain everything working perfectly up until after a Windows Update Reboot?My only other possible thoughts would be a hardware compatibility issue, or as Saltgrass has suggested, a network setup problem.
There are Unix boxes on the router. We CAN'T enable DHCP. Ever. Period.I know you said you can't, but if the router at all supports the option, enable the DHCP server,
No kidding. Can we get back on track, though? We've already ruled out this problem not being local to the Win7 system.Saltgrass, patcooke and myself have no doubt seen similar problems before, but never a similar one that has taken this long to solve.
Windows IP Configuration
Host Name . . . . . . . . . . . . : Sylvanas
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Local Area Connection:
Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : Broadcom NetXtreme 57xx Gigabit Controller
Physical Address. . . . . . . . . : 00-23-AE-2F-3E-9D
Ethernet adapter Wireless Network Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Dell Wireless 1397 WLAN Mini-Card
Physical Address. . . . . . . . . : 00-24-2C-7B-AA-01
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.83
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 68.87.76.178
68.87.66.196
netsh winsock reset
netsh int ip reset c:\resetlog.txt
Investigate router or broadband modem issues
If you're connected to a hotspot or domain network, contact the network administrator.
Otherwise:
1. Unplug or turn off the device.
2. After all the lights on the device are off, wait at least 10 seconds.
3. Turn the device on or plug it back into the power outlet.
To restart the router or modem that has a built-in-battery, press and quickly release the Reset button.
Windows Network Diagnostics
Issues found
"Local Area Connection" doesn't have a valid IP configuration . . . . . . Not fixed
. . Reset the "Local Area Connection" adapter . . . . . . Completed
. . Investigate router or broadband modem issues . . . . . . Completed
Detection details
Details about network adapter diagnosis:
Network adapter Local Area Connection driver information:
. . Description . . . . . . : NVIDIA nForce Networking Controller
. . Manufacturer . . . . . . : NVIDIA
. . Provider . . . . . . . : Microsoft
. . Version . . . . . . : 1.0.1.211
. . Inf File Name . . . . . . . : C:\Windows\INF\netnvm64.inf
. . Inf File Date . . . . . . . : Monday, July 13, 2009 8:37:30 PM
. . Section Name . . . . . . . : NVENET51.NDI
. . Hardware ID . . . . . . . : pci\ven_10de&dev_0269
. . Instance Status Flags . . . . . . . : 0x180200a
. . Device Manager Status Code . . . . . . : 0
. . IfType . . . . . . : 6
. . Physical Media Type . . . . . . : 14
Collection information
Computer Name: ALGALON
Windows Version: 6.1
Architecture: amd64
Time: Monday, November 15, 2010 2:18:38 AM
An error occurred while renewing interface Local Area Connection : unable to contact your DHCP server. Request has timed out.
An error occurred while releasing interface Loopback Pseudo-Interface 1 : The system cannot find the file specified.