Error Code 1231 Unconnective Network Problem
Hi,I have a problem that I'm quite sure is Vista-Asscociated.I recently switched from directly being plugged into my modem, to a router-system at home for my computer.However, the problem is that I get the "Unidentified Network" in the Networks section, and I can't ping my own IP or Default gate way, as it gives me a "PING: transmit failed, error code 1231." message.Currently, all my settings in the IPv4 protocol are set to auto, and setting them manually makes no difference, except that it gives me error 1232 instead of 1231...I've tried pretty much everything I could,includinghttp://blogs.technet.com/steve_lamb/archive/2007/05/01/windows-vista-won-t-connect-to-the-network-how-to-fix-the-problem-by-making-vista-less-aggressive-on-the-network.aspxandhttp://support.microsoft.com/default.aspx/kb/928233/en-usI'm currently using Realtek RTL8168/8110 Family PCI Gigabit Ethernet NIC running Vista Ultimate.I have 4 other computers at home, all capable of connecting to the network, and going on the internet and everything.Vista obviously cannot repair the problem itself.Any help would be greately appreciated. Thanks.
June 28th, 2007 2:44am
It's probably also worth mentioning that Vista does connect to the network, calling it the 'Network #', and during that second or two, I can get all the numbers in ipconfig, but very soon after, Vista changes the 'Network #' to 'Unidentified Network', and all the numbers in ipconfig are lost.
July 1st, 2007 10:09pm
Have you tried de-selecting TCP IP V6 from TCP/IP setting under the lan adapter as I've seen it cause probs before. It seems to favour V6 over V4 for some reason which I believe is causing the problem so if you only have V4 protocol available it will most likely fix your troubles. P.S. I'm not sure if it is just my own router but I also find that I sometimes need to perform 'ipconfig /renew' in prompt window to discover the correct DNS. I fix many computers each day, it's my job... so If this doesn't fix your prob then I'd really like to know cos it hasn't failed me yet
July 12th, 2007 7:25am
Thanks for the help, but it's a little late lol.Just to help you, and anyone else having this problem: Yes, I have tried doing that, as well as a whole bunch of other stuff.I have fixed the problem.At first, the problem was originally solved by upgrading the router firmware of the Xincom Twin Wan XC-DPG502 to Ver 2.2, released February 2007 (I believe), updated from V. 2.1O released back in May 2005.However, that only solved the problem until next restart, at which point I went back into the router settings, and for Vista, you need to make sure the "LAN Any IP" is disabled (not checked). That should solve the router problem with Vista.-Gloomfrost
July 12th, 2007 4:23pm
>and for Vista, you need to make sure the "LAN Any IP" is disabled (not checked). Mhmmm, would you be so kind and say where can I find it? TIA! Gints
August 3rd, 2008 8:01am
Lol wow you're SO lucky I was subscribed to this thread still Uhm, I have a Xincom XC-DPG502router, and for me, it was in your local gateway (for me it's 192.168.1.1), could be 192.168.2.1, and then it was in "Basic Configuration" and in "LAN & DHCP", and then in"Optional Settings" in there, and it's right beside "DHCP Server" which was enabled, and still is. (I'm still on my Vista Ultimate)I'm going away forthe nextweek incase you reply, but good luck!~Gloom
August 3rd, 2008 11:55am
Hello, I had the same issue on a Vista Business 64 machine. Turns out in my case the problem was with Comodo Firewall. Once I uninstalled it, everything worked fine again. Best of luck.
April 30th, 2009 9:40pm
This has already been mentioned, but it did work for me. First, I disabled ipv6. I then ran the netsh command to reset my IP stuff. Just a warning though, I think this will only apply to this problem if you are using static IPs. Here is the netsh comman: netsh interface ip set address name="Local Area Connection" static xxx.xxx.xxx xxx.xxx.xxx xxx.xxx.xxx ip address subnet mask gateway
June 15th, 2009 10:32am
HiI had the same problem that you have mentioned. It occured to me, when i was trying to connect to an Unsecured WLAN. I was connected and was getting an Auto Config IP address. All I did was, tried renewing the ip with "ipconfig /renew". And that worked out for me. I hope you should have tried this. If not, Please try it.
September 20th, 2009 3:16pm
About 6 weeks ago, I started to get intermittent failure of my ethernet on my Vista (Business, running for about 1yr)PC. The other desktop and laptop, both running XP didn't seem to have any problems. At first a restart seemed to cure the problem and it was only once every three days or so, annoying but not disastorous. It gradually got more frequent until the Vista PC would not connect at all and would not even ping the router. I trawled the forums, did resets on the comms, reloaded drivers, installed a new NIC (wired) All to no avail. I did a restore to a couple of weeks back with no difference, then in desparation ran full diagnostics - those failed with a disc access error about half way through, but on a reboot suddenly it worked again; the other XP PCs had been working quite happily all this time. This lasted for a week and then the system went completly dead and none of the otherPCs had a connection.I ended up with a 1231 error and then this thread.Having tried all the suggestions with no effect, Ieventually a bought a new router. This last weekend I ditched eveything and reloaded Vista from scratch. Having mostly got back to where I was with updates etc. the system is still functional with the original integrated NIC. I do now however have IP6 turned off. I haven't been back to try the old router yet - too much catching up to do - but I have this feeling that there is something in Vista which went astray. No way to prove it, but my own experience and the comments on the forums suggest to me a strong bias to that conculsion. I would be interested to know if anyone else has taken the drastic step of a reinstallation and found the problem fixed.One definite problem these days is that if you don't have an internet connection it is very difficult to implement a solution. If I'd have had only had one computer, I would definitely be up the proverbial creek. It would also suggest that it is not sensible to have all one OS. In addition if the basic operating system does not even have a pdf reader on board, it can also be difficult to look at installation instructions!
November 17th, 2009 12:55pm
I’m beginning to despise computers more and more, especially when people think (and maybe do understand it) that they can help discover a solution, but they confuse their explanations which are so arcane that they’re very difficult to understand. Sometimes, then they also use abbreviations as if they’re text-messaging and trying to save space. Maybe they’re trying to impress somebody or themselves. Anyway, your explanation was well written and closely describes my recent experiences and, frankly, I’m bewildered at how I found it at all. I’ve googled everywhere over the past two weeks and have been unsuccessful. I "upgraded" a pair of P3s with an aim at connecting faster with the Internet and my home network. Everything worked great for a few months when connections gradually began to deteriorate until there was nothing. I tried all the things you mention, also unsuccessfully, and have resorted to returning one of my new PCs for repair. Its integrated NIC worked erratically until it finally didn’t work at all. I tried pinging it and received an error code, 1231, which led me to your discussion. (By the way, my other PC which is nearly identical to the malfunctioning one works just fine, but I’m waiting for that to change!) I set up an old P3 (with XP) as a replacement so that I could print stuff on my network, and noticed that it works fine, albeit slow, using all the same cables, connections, routers, and so forth. I’m not a techy and have very limited knowledge, but I wanted to thank you for your effort you made to try and help others who might have experienced the same problem. Eventually, I hope to figure out what happened and my next target for scrutiny is IP6 and the stability/continuity of Vista in general. But I feel that I’m looking for a needle in the proverbial haystack. Thanks again.
January 10th, 2010 5:17pm
I thought I would share the result of my experience with this same issue. Nothing posted in this forum was anywhere close to how I fixed my issue. Our problem was actually hardware. A while back, we had a lightning storm. Since then (as I never thought that would be the issue) this computer has failed to connect. All other 30+ computers on our domain had no problem at all. Eventually, I went to the utility closet and switched this computer's Cat5 line to another port on the 24 port switch, and Bam, it worked. This is after having the exact same issue with the error code 1231 and 1232 when trying to ping the firewall router. The computer was acting like it was connecting just fine, but in the end, failed to communicate with the firewall and server, otherwise any and every network resource. Hope this helps someone else figure out that it's a hardware issue. -Jerry
September 15th, 2010 9:50am
I'd suggest just double checking your IP settings. When I ran into this error, I had a machine that had the correct IP and Subnet Mask, and DNS settings, but no default gateway configured. Correcting the default gateway resolved it.DG
January 4th, 2011 6:13pm
Error code 1231: Solving the problem with network settings: Try to remove the "unnecessary protocols" in the network settings and remove the tick from those "unnecessary protocols", that are not removed, such as: IP 6.http://www.anodonta.com.ua
February 1st, 2011 5:49am
This happened to our Vista PC yesterday when I added a blackberry to our Wireless Network. Because we have a Linux box that needs a static IP address (I need to ssh from a windows box using putty etc) I decided to bind all the other devices to keep things tidy. It seems that the Blackberry trashed the configuration somewhere and the PC that got pushed off the network was our (only) Vista machine. No idea why but there you go. Anyway, I reset everything on the router and rebooted it and problem solved - everything is getting a dynamic IPv4 address from the DHCP server on the router and I've re-bound the Linux box to the IP address it had before. We've a Draytek Vigor 2820, this is a bit above most peoples spec. We got it because our ISP was fast but a bit unstable - but my wife likes her email address! - so we went for dual ISPs and this was the cheapest router that need a good job of running both in parallel + I'm a Linux novice so having a more configurable router meant I didn't have to figure out how to do it in Linux which would have caused too many grey hairs. Anyway, if you don't have this router don't worry, just reset everything and reboot (and assign the passwords etc - a bit of work but it should clear everything up). For those SMEs with 'big' routers, check your IP routing tables and see if you CAN'T see the Vista box. Hope this helps, I'm sure this isn't the only reason for that kind of failure.
June 16th, 2011 3:57pm
Thank you for the thought. Had been working fine all morning but had a storm come through last night. Must of damaged something that decided to quit all of a sudden. Switched it to a different port and away it went. Top-down, bottom-up, seems I always start at the wrong end ... lol.
July 28th, 2011 5:04pm
I ran into this problem while working on a MOAC lab for my server 2008 class. We had two servers each with two NICs. Server1 had static IPs of 192.168.10.1 and 192.168.11.1. Server2 had static IPs of 192.168.11.2 and 192.168.12.2. When I would ping 192.168.12.2 from Server1 or 192.168.10.1 from Server2 I would get the error code. To solve the problem I enabled the Routing and Remote Access role on the servers and configured them for the LAN. Problem solved for me.
February 17th, 2012 10:31am