| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 81557 | 2007-07-31 08:58:00 | Vista Networking problem | Painty (3964) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 574514 | 2007-07-31 08:58:00 | I have a Vista Ultimate machine I built for a mate. Its all squeaky clean and legit, fully patched etc etc. My home network is 192.168.1.1 etc, I'm running a dynalink rta220 with dhcp and Im using a 3m office connect as a wireless access point. THis all functions fine and I have never had a problem with it. The machine has been successfully resighted to another mates place who also runs a 192 network. But at the mates place his network is using a Telecom dlink freebie thing on 10.1.1.1 etc. His two laptops on XP can connect fine. And his Cambridge Audio CD player just plugs in and works ok As soon as I plug the vista machine in, it gets an IP but it can only see machines on his network, it can't get outside. nslookup can't get out, so the dns relay isnt working for it. I did specify gateway can ping 10.1.1.1 cant ping anything past 10.1.1.1 turned nasty vista firewall off and still no joy. any thoughts or suggestions gratefully accepted as this is causing extreme hair loose |
Painty (3964) | ||
| 574515 | 2007-07-31 09:04:00 | Check the network names are all the same. XP uses XPHome by default and Vista uses Workgroup. | Bantu (52) | ||
| 574516 | 2007-07-31 11:03:00 | Sounds weird. Are you pinging an external ip no. or a URL? Using an ip eliminates a dns issue. What error is the external ping returning? Double check the gateway address of 10.1.1.1 | linw (53) | ||
| 574517 | 2007-07-31 21:38:00 | yes did enter IP of an external website (tra) with no joy and the gateway is definitely 10.1.1.1 (because I can browse to the web config page for it) Bantu: at my home I have my own workgroup name that is non standard and I could still see the Vista box and get through my gateway. Is it anything to do with the Telecom setup (everywhere else i have tried it has been on SLingshot, Quicksilver and even got a mate to take it to another persons place who has a 10.1.1.1 setup in case there was something bizarre there. |
Painty (3964) | ||
| 574518 | 2007-07-31 21:42:00 | open a command window and type ipconfig /all and post the results here | Rob99 (151) | ||
| 574519 | 2007-07-31 23:34:00 | Well I found this gem: blogs.zdnet.com ... I called a technical contact at D-Link, who confirmed that the router is indeed part of the problem. According to this source, a known bug in recent builds of Windows Vista affects a slew of recent-vintage routers. The culprit is the built-in firewall software on the DI-724U router, which features Stateful Packet Inspection (SPI). This is not the only router in the SOHO market that features SPI - Netgear’s WGR614 and Linksys’ WRT54GS are among dozens of products that offer similar capabilities. Trouble is, the new and improved TCP/IP stack in Windows Vista falls apart when it encounters an SPI-enabled router. So I think given my experiences so far that I am going to investigate the dlink on his network further. |
Painty (3964) | ||
| 574520 | 2007-08-01 02:11:00 | Well I found this gem: . zdnet . com/Bott/index . php?p=10" target="_blank">blogs . zdnet . com So I think given my experiences so far that I am going to investigate the dlink on his network further . Uninstall IPv6 on the NIC . I too have read about numerous issues with the new TCP layer . The best solution thus far is to uninstall the extra protocal as its not needed yet anyway . . . |
SolMiester (139) | ||
| 574521 | 2007-08-01 10:28:00 | Interesting . I have my IPV6 disabled but for no special reason other than it is not necessary! My router isn't affected, though - must be too old (502T) . Painty, interested to know if disabling IPV6 works for your situation . |
linw (53) | ||
| 1 | |||||