Problems with LAN slow to connect on P67A-D3-B3

[F5BJR]

*
sorry but i have tested just at this time ping --> my provider

and ... i have exactly the same values ( some 48ms )

Pierre

[snadge]

did you flush your DNS cache before each test? if not then you would get same result anyway,
Anyway I think Vista and Windows 7 train the DNS settings (under your config) from the router when Vista/Win7 boot up or on first request of DNS, then they save it in the IP Stack for the rest of that windows session... windows XP on the other hand I think requests the router each time for the DNS server's IP Address

either way it still best to do it properly and cut out the 3rd party request

your method:
WINDOWS -> ROUTER -> WINDOWS -> DNS SERVER
windows has to ask the router for DNS IP address, router tells windows its X.X.X.X, windows sends request to X.X.X.X

setting DNS manually:
WINDOWS -> DNS SERVER
windows sends request to X.X.X.X

anyway its not important... i just hope my problem is solved with this fix

[F5BJR]

*
Sorry , i  use not VISA or Windows 7 but Windows XP !!

Pierre

[Dark Mantis]

Basically what you are saying is that you have issued your computer with a fixed IP address rather than letting the router dynamically assign one. I always used to do this anyway as it speeded up the login process.

[snadge]

Basically what you are saying is that you have issued your computer with a fixed IP address rather than letting the router dynamically assign one. I always used to do this anyway as it speeded up the login process.

Yeah, turned on PC this morning and its fine, so its looking good as it would normally be broken again taking approx 64 secs to connect. theres definitley a driver problem or IRQ conflict as Realtek Diagnostic Utility says so as IRQ and FIFO tests fails, but at least it can be fixed until there is a driver update.

[F5BJR]

*
You can find a Realtek LAN drivers collection to this  page

http://www.station-drivers.com/page/realtek_lan.htm

Pierre

[snadge]

thanks Pierre,  im sure that driver version is slightly different, one on gigabyte has newer date but only 2 weeks newer.. im sure the one on that website is higher number

7.046.0621.2011 = date: 21.06.11

mine installed from gigabyte website = 7.46.531.2011
on driver page in device manager it says date: 31.05.11 but on gigabyte website it says date 08.07.11
http://www.gigabyte.com/products/product-page.aspx?pid=3800#dl

hmmm im gunna try the driver from that page as it is obviously a little bit newer. thanks for that Pierre

[snadge]

...well ive installed it and everything is on Automatic (negotiate its own Ip address etc)

if it doesnt mess up by tomorrow morning then its fine... and Gigabyte would need to change the driver on their website with the newer one

[snadge]

didnt work... still same problem after first reboot 4 hours later - im keeping the driver though but going back to manual setup

[Dark Mantis]

I do think that is the most sensible plan. As I said it is something many of us have done in the past anyway just to speed things along.

[snadge]

true, but it doesnt take from the fact there is still a driver conflict issue, I wonder how the other lad is getting on with his

[Brains11]

  Nope no go, this morning back to 64 seconds delay again. Switched to static IP.

[F5BJR]

*
test with a Gigabit HUB :

Computer <--> HUB <--> Router

If you have the same problem send your motherboard for repair / exchange

Pierre

[Dark Mantis]

If you need to return it for repair/replacement as F5BJR suggests then contact your retailer or local Gigabyte centre.

returns@gbt-tech.co.uk     RMA section UK

[snadge]

fixed with new F4 official release BIOS

its not BETA is official F4 thats not on website yet

http://ggts.gigabyte.com.tw/FileList/1108276/p67ad3b3.zip