Problems connecting to the UTD via ethernet please help

D

Dan The Man

Well-Known Member
Joined
Apr 24, 2006
Messages
120
Reaction score
0
Hi all,

i did run a search to see if this has come up before - if i missed the thread then i apologise

My problem:

Up until last night i've been able to connect to the UTD through my on board lan port without any worries....

then from about 11pm and beyond ill switch the utd on it will create a local connection between the utd and my pc, but when i try and connect iburst it just freezes on the connecting through wan mini port window. then get error saying unable to reach remote computer bla bla ( its never done that before)

so i figured great my on board lan is messed up, so i whip out a network card plug & install. but when i connect the utd to the new network card it doesnt created a local connection at all :mad: so quite obviously i wont be able to connect iburst through it.

i know i can just use the usb, but i prefer the ethernet way and really would like to resolve this

any idea why my on board has frozen or why the utd and network card aren't talking to each other ??

any advice will be much appreciated

thanks Dan :)
 
a buddy of mine had the same problem after his windows update patched his XP and then it froze trying to connect to iBurst....:confused: he reloaded XP after he got annoyed trying to sort it out, anyway.........Did windows update patch anything on your win XP recently?

that's all I can think of....sorry
 
i had just finished downloading patches for xp from windows update!

so is my only option a full reinstall ?

there must be some other way
 
Dan The Man said:
i had just finished downloading patches for xp from windows update!

so is my only option a full reinstall ?

there must be some other way
Click to expand...

:confused: DAMN! Co-incedence or Microsoft cons-piracy :D

I wonder......lemme go disable my Auto Updates :D
 
Simple Twist Of Fate said:
netsh int ip reset c:\resetlog.txt

run that from
start
run

resets your Tcp stack to original
Click to expand...

Phew thanks boet, makin a note if I ever need this :D
 
Wow, thats pretty dangerous to the avreage Iburst user that knows nothing about your fix.

So howcome this doesnt effect more people?
 
oh my word!!

ok so its happened again :(

and i did the fix again......only difference is...it does not work anymore!!
$@#$%#%#$!!!!!!!!!

aaaaaahhh !! this is so frustrating - any idea what else it could be twist ?
 
heres whats in the resetlog if this will help you figure it out :



deleted SYSTEM\CurrentControlSet\Services\Netbt\Parameters\EnableLmhosts
reset SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{C9157F26-7450-4A69-85E9-090A56E553F4}\AddressType
old REG_DWORD = 1

added SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{C9157F26-7450-4A69-85E9-090A56E553F4}\DisableDynamicUpdate
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{C9157F26-7450-4A69-85E9-090A56E553F4}\IpAutoconfigurationAddress
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{C9157F26-7450-4A69-85E9-090A56E553F4}\IpAutoconfigurationMask
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{C9157F26-7450-4A69-85E9-090A56E553F4}\IpAutoconfigurationSeed
reset SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{C9157F26-7450-4A69-85E9-090A56E553F4}\RawIpAllowedProtocols
old REG_MULTI_SZ =
0

reset SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{C9157F26-7450-4A69-85E9-090A56E553F4}\TcpAllowedPorts
old REG_MULTI_SZ =
0

reset SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{C9157F26-7450-4A69-85E9-090A56E553F4}\UdpAllowedPorts
old REG_MULTI_SZ =
0

deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\DontAddDefaultGatewayDefault
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\EnableIcmpRedirect
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\EnableSecurityFilters
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\SearchList
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\UseDomainNameDevolution
reset Linkage\UpperBind for {1A3E09BE-1E45-494B-9174-D7385B45BBF5}\NVNET_DEV0057\4&31DE8C1B&0&01. bad value was:
REG_MULTI_SZ =
PSched

reset Linkage\UpperBind for PCI\VEN_10EC&DEV_8139&SUBSYS_813910EC&REV_10\4&13699180&0&3848. bad value was:
REG_MULTI_SZ =
PSched

reset Linkage\UpperBind for USB\VID_0482&PID_0204\02701Q191791687500. bad value was:
REG_MULTI_SZ =
PSched

reset Linkage\UpperBind for ROOT\MS_NDISWANIP\0000. bad value was:
REG_MULTI_SZ =
PSched

<completed>

reset SYSTEM\CurrentControlSet\Services\Netbt\Parameters\Interfaces\Tcpip_{4C87B181-1A07-4628-8C16-E89EC80F4B32}\NameServerList
old REG_MULTI_SZ =
<empty>

added SYSTEM\CurrentControlSet\Services\Netbt\Parameters\Interfaces\Tcpip_{4C87B181-1A07-4628-8C16-E89EC80F4B32}\NetbiosOptions
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{4C87B181-1A07-4628-8C16-E89EC80F4B32}\NameServer
reset SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{794DE427-E586-40B3-8189-37AC0F11D6A5}\AddressType
old REG_DWORD = 1

deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{794DE427-E586-40B3-8189-37AC0F11D6A5}\IpAutoconfigurationAddress
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{794DE427-E586-40B3-8189-37AC0F11D6A5}\IpAutoconfigurationMask
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{794DE427-E586-40B3-8189-37AC0F11D6A5}\IpAutoconfigurationSeed
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{AA52F243-8C9B-4292-B416-29B2142CA2FB}\IpAutoconfigurationAddress
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{AA52F243-8C9B-4292-B416-29B2142CA2FB}\IpAutoconfigurationMask
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{AA52F243-8C9B-4292-B416-29B2142CA2FB}\IpAutoconfigurationSeed
reset SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{F979CC5D-B896-413A-8028-97652894A0D3}\AddressType
old REG_DWORD = 1

deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{F979CC5D-B896-413A-8028-97652894A0D3}\IpAutoconfigurationAddress
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{F979CC5D-B896-413A-8028-97652894A0D3}\IpAutoconfigurationMask
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{F979CC5D-B896-413A-8028-97652894A0D3}\IpAutoconfigurationSeed
<completed>
 
Hmmm I've also had problems like this with my modem... and what's worse was it use to freeze my entire pc and crash my system folder and boot record :(

best solution either get a replacement for your modem or get a router
 
well, i reinstalled windows, didnt help...

so i figured.... i'll try my friends UTD, same problem...... very strange indeed
tried firmware updates, latest driver updates for on board lan etc... nothing :(

last option is to get a router......but will it work ?
 
Firmware update?
Plug the USB in and see what firmware is on the UTD.
Maybe update it.
 
Any resolution to this problem, as I seem to be experiencing the same thing?
 
Why on earth are you ppl connecting to iBurst modem directly with your PC. Using a router solves all these problems indefnitely and you don't need to patch your windows or worry about Windoze causing the problem
 
Trying to connect it via my Linksys WAG354G router, but not geting any love. Will try again tonight. I had it working when I still had my ADSL.
 
JTech said:
Why on earth are you ppl connecting to iBurst modem directly with your PC. Using a router solves all these problems indefnitely and you don't need to patch your windows or worry about Windoze causing the problem
Click to expand...


possibly because there is no need for the additional cost if you are not going to network?
 
Additional cost? I think the benefits outweight the additional cost.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X