Jump to content

Dns Issue On Client Pc On An Ics Network


hardnrg

Recommended Posts

ok, this started happening today, all has been working fine since august using the follow setup:

 

 

 

 

AXP rig:

ICS enabled, Firewall disabled

nForce 100baseTX NIC connected to Ethernet (internet)

D-Link giga NIC connected to giga switch

 

Windows IP Configuration

	Host Name . . . . . . . . . . . . : XP2500
	Primary Dns Suffix  . . . . . . . : 
	Node Type . . . . . . . . . . . . : Unknown
	IP Routing Enabled. . . . . . . . : Yes
	WINS Proxy Enabled. . . . . . . . : No
	DNS Suffix Search List. . . . . . : jmu.ac.uk

Ethernet adapter Halls LAN:

	Connection-specific DNS Suffix  . : jmu.ac.uk
	Description . . . . . . . . . . . : NVIDIA nForce MCP Networking Adapter
	Physical Address. . . . . . . . . : 00-0C-76-8E-47-BF
	Dhcp Enabled. . . . . . . . . . . : Yes
	Autoconfiguration Enabled . . . . : Yes
	IP Address. . . . . . . . . . . . : 150.204.72.5
	Subnet Mask . . . . . . . . . . . : 255.255.252.0
	Default Gateway . . . . . . . . . : 150.204.75.254
	DHCP Server . . . . . . . . . . . : 150.204.39.3
	DNS Servers . . . . . . . . . . . : 150.204.37.1
										150.204.40.1
										150.204.39.1
										150.204.39.2
										150.204.40.2
										150.204.40.3
										150.204.16.13
	Lease Obtained. . . . . . . . . . : Friday 22 December 2006 5:36:18 am
	Lease Expires . . . . . . . . . . : Friday 05 January 2007 5:36:18 am

Ethernet adapter Steve LAN:

	Connection-specific DNS Suffix  . : 
	Description . . . . . . . . . . . : D-Link DGE-528T Gigabit Ethernet Adapter
	Physical Address. . . . . . . . . : 00-13-46-2D-7A-82
	Dhcp Enabled. . . . . . . . . . . : No
	IP Address. . . . . . . . . . . . : 192.168.0.1
	Subnet Mask . . . . . . . . . . . : 255.255.255.0
	Default Gateway . . . . . . . . . :

 

3500 rig:

Firewall disabled

nForce giga NIC connected to giga switch

 

170 rig

Firewall disabled

Marvell Yukon giga LAN connected to giga switch

 

Windows IP Configuration

	Host Name . . . . . . . . . . . . : steve-main
	Primary Dns Suffix  . . . . . . . : 
	Node Type . . . . . . . . . . . . : Mixed
	IP Routing Enabled. . . . . . . . : No
	WINS Proxy Enabled. . . . . . . . : No
	DNS Suffix Search List. . . . . . : mshome.net

Ethernet adapter Local Area Connection:

	Media State . . . . . . . . . . . : Media disconnected
	Description . . . . . . . . . . . : NVIDIA nForce Networking Controller
	Physical Address. . . . . . . . . : 00-01-29-D1-44-AB

Ethernet adapter Local Area Connection 2:

	Connection-specific DNS Suffix  . : mshome.net
	Description . . . . . . . . . . . : Marvell Yukon 88E8001/8003/8010 PCI Gigabit Ethernet Controller
	Physical Address. . . . . . . . . : 00-01-29-D1-44-66
	Dhcp Enabled. . . . . . . . . . . : Yes
	Autoconfiguration Enabled . . . . : Yes
	IP Address. . . . . . . . . . . . : 192.168.0.115
	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 22 December 2006 6:46:49 am
	Lease Expires . . . . . . . . . . : Friday 29 December 2006 6:46:49 am

Ethernet adapter Local Area Connection 4:

	Media State . . . . . . . . . . . : Media disconnected
	Description . . . . . . . . . . . : Bluetooth PAN Network Adapter
	Physical Address. . . . . . . . . : 00-11-F6-05-3A-27

 

 

 

right... recently i disconnected my 170 from the network and when i reconnected it i couldn't remember which RJ-45 socket was the Marvell-Yukon one (as opposed to the nForce one) and connected it to the nForce one by mistake... today i swapped it back to the Marvell Yukon one... so that's a recent change

 

on the client pc (main rig: 170) a lot of pages are just failing to load in browsers, IM clients not connecting, email servers not working... and if i try something like: ping www.fart.com (an address i have not accessed on the client) then i get "Ping request could not find host www.fart.com. Please check the host and try again". I could repeat this indefinitely with the same result...

 

NOW, if i ping www.fart.com from the host pc (axp rig) then it works first time, no problems at all... then if i REPEAT the ping request on the client pc, it NOW works!!! what the hell is going on? i've tried manually setting the DNS and Gateway ip addresses to 192.168.0.1 on the client pc, i've tried adjust the MTU setting of the Marvell Yukon NIC down to 1472 and then 1444 (from finding the lowest unfragmented packet size using ping -f -l <packetsize> 150.204.75.254 and then first time i found it to be 1472, so set that using regedit on the currentcontrolset / tcpip / params... and then rebooted and retried and then somehow fragmentation size went down to 1444 so set to 1444 and rebooted and went down to 1415... so i thought that was a waste of time!!!!!

 

this is so annoying... especially since it's worked fine without issue for so long and now all of a sudden it just doesn't seem to be working right

 

if i try to access a page in the browser of the client pc it fails, or maybe 1 in 40 times it will load, but then on the host pc it works first time, try back on the client pc and it works first time NOW, but not before... what is going on here? i can't work it out :(

 

i would GUESS it's a dns issue... but i don't know enough about networking to find out why the name resolving isn't working...

 

oh yeah, if i put the ip addresses in the browser of the client pc's, the pages will load... that's why i think it's a dns issue

 

edit:

 

also, i've tried ipconfig /release and ipconfig /renew on both the host and client pc's... and ipconfig /flushdns... resetting windows firewall settings to default and then disabling it again... rebooting all pc's after each change...

Edited by hardnrg

Share this post


Link to post
Share on other sites

on client pc:

 

tried winsock fix

tried commandline -> netsh interface ip reset

tried winsock fix again

tried different NIC

there is only one wall jack

 

my network setup goes:

 

wall jack >--100--> AXP (nForce), ICS, AXP (D-Link PCI giga) >--1000--> gigaswitch >--1000--> 170 (marvell yukon giga OR nforce giga)

..................................................................... .......................................................>--1000--> 3500+ (nforce giga)

 

the thing that's really stumping me is that the client pc's have ip addresses, the gateway and dns are correctly assigned as the host pc (192.168.0.1), internal network file sharing works perfectly, IP addresses work fine in browser, XFire works fine on client pc... browsing a site on client pc after opening it on host pc works...

 

it's like the whole network CAN work, it's just the client pc's aren't able to resolve a (new) domain name to an ip address... i might try the winsock fix on the host pc now and see what happens

Edited by hardnrg

Share this post


Link to post
Share on other sites

mmm, i think i'll uninstall the nic's, try and clear all the ics stuff and start again on the host pc lol

 

man... i uninstalled the NIC's from the hardware device list and then uninstalled anything to do with networking from Add/Remove Windows software... and still no joy... it's exactly the same no matter what i do...

 

i think i'm just going to buy a router from work and use that instead of a pc with ICS...

 

Wall (100M) --> Router (100M switch) --> Switch (1000M) --> 3x PC w/ giga NICs

Edited by hardnrg

Share this post


Link to post
Share on other sites

  • 3 weeks later...

I had this EXACT same problem at home, with an ISDN connection.

 

I found the ONLY way to get around the problem was disable DHCP.

 

Set the IPs all manualy.

 

I also set the DNS severs on the Clients to the ones provided by the ISP, NOT the IP of the Host.

 

Try setting the DNS sever address on your client to those

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...