41 replies to this topic

[L A M A]

Hi 

 

XP: NAS negotiation delays explorer shell and takes 2 minutes to connect

 

I used, XP Lite, nLite, disabled plenty of services, tweaked, etc etc SO, can anyone tell me how to stablize negotiation assuming that I screwed up somewhere and brought Bill Gate's wrath upon me???

 

Win7 works great... could it be SMB version? Any way to upgrage or use third party SMB? something that exist on WinPE?

[sbaeder]

What NAS are you using, and can you give more information - like does it work OK with a full XP?  i.e. more to go on that just my cut down version doesn't seem to work right...

[L A M A]

Iomega 4TB ix2, My XP is actually full,... only feature related components were removed. Unused Services were removed by XPLite (which can be reinstalled provided that such service can fix the delaying negotiations.

 

It goes like this, when XP is up and when I plug in NAS ethernet cable directly, negotiation takes 2 minutes! (on w7 its fast though, 30sec).

 

 

When I connect NAS to router (which is connected to XP), it only takes 10 seconds. 

 

 

Following are the only 'netwok' related services enabled on this XP (for the sake of performance):

DHCP Client (the main thing)

DCOM Server Process Launcher

Server (needed by bluetooth)

Workstation (needed by bluetooth)

Network Connections (to enable/disable)

Remote Procedure Call 

Remote Access Connection Manager (needed by bluetooth)

Telephony (needed by bluetooth)

Terminal Services

Wireless Zero Configuration (wifi)

 

When NAS is connected to my samsungTV directly, it also takes 2 minutes there but when I use homeplug, it takes 15-20 seconds.

 

Ethernet is Intel82579LM with many advance settings in device manager, can anthing get tweaked in there? you can use google image and type above model + advance device manager settings to know...

 

If I plug the Ethernet cable and PowerON system which starts Grub4dos > FiraDisk XP on RAM, I see start menu but My Computer takes 2 minutes to show. Process Explorer shows userinit not started svchost.exe frozen and after 2 minuted suddently everything starts up. (I remember such experience years back when i disabled Terminal Services, logon delayed...)

 

 

So what critical services could be disabled? because honestly, I don't know...

[Wonko the Sane]

Well, as always, you completely FAIL to describe (let alone EXACTLY) your setup.

I don't think anyone here has ESP capabilities.

 

Wonko

[L A M A]

If you mean XP setup, then following is done with nLite:

 

 

 

[Main]

Env = 1.4.9.1 - 2.0.50727.42.Microsoft Windows NT 5.1.2600 Service Pack 2
Target = Windows XP Professional SP2 - 5.1.2600.2180 - English (United States)

[Tasks]
Remove Components
Unattended Setup
Integrate Drivers
Tweaks
Create a Bootable ISO
Options

[Components]
;# Applications #
Accessibility Options
Briefcase
ClipBook Viewer
Defragmenter
Games
Internet Games
NT Backup
Screensavers
;# Drivers #
Display Adapters
Display Adapters (old)
IBM ThinkPad
Modems
;# Multimedia #
Images and Backgrounds
Luna desktop theme
Media Center
Mouse Cursors
Movie Maker
Music Samples
Old CDPlayer and Sound Recorder
Windows Media Player
Windows Media Player 6.4
Windows Sounds
;# Network #
MSN Explorer
Windows Messenger
;# Operating System Options #
.NET Framework
Desktop Cleanup Wizard
Disk Cleanup
Document Templates
DR Watson
File and Settings Wizard
Help and Support
IExpress Wizard
MS Agent
Out of Box Experience (OOBE)
Search Assistant
Security Center
Shell Media Handler
Tour
User account pictures
Zip Folders
;# Services #
Automatic Updates
Background Intelligent Transfer Service (BITS)
Distributed Link Tracking Client
Error Reporting
System Restore Service
Task Scheduler
TCP/IP NetBIOS Helper
Windows Firewall/Internet Connection Sharing (ICS)
Windows Time
;# Directories #
DOCS
SUPPORT
VALUEADD
;# Compatibility #

[KeepFiles]
msconfig.exe

[RemoveFiles]
clock.avi
yahoo.bmp
swtchbrd.bmp

[Options]
BlackSetupBack
DisableFreereq
DisableMinMem
ProfilesDir = "%SystemDrive%\Documents and Settings"
TargetPath = "WINDOWS"
temp_dir = %SystemDrive%\WINDOWS\Temp
AdvTweaks
CDPromptRemove

[Patches]
TcpIp = 1000
UsbPoll = 1000
DoUxTheme
DoSFC

[Services2]

[Tweaks]
Boot and Shutdown-Auto-End tasks immediately
Boot and Shutdown-Auto-Kill hung applications immediately
Boot and Shutdown-Auto-Kill hung services immediately
Boot and Shutdown-Disable automatic restart on System Failure
Boot and Shutdown-Disable logging on System Failure
Boot and Shutdown-Disable saving Last Good state at boot
My Computer-Add Device Manager to Context Menu
My Computer-Add Event Viewer to Context Menu
My Computer-Add Registry Editor to Context Menu
My Computer-Add Services to Context Menu
My Computer-Add Software to Context Menu
Performance-Disable Last accessed Timestamp on files
Performance-Disable Optimize harddisk when idle
Performance-Disable paging of kernel and core-os
Performance-Disable Tracking of Broken Shortcut Links
Performance-Disable Warn on low disk space
Performance-Disable WBEM logging
Performance-Do not cache thumbnails
Performance-Enable USB Idle Endpoint support
Performance-Minimal Power Management
Performance-Processor scheduling-Background services
Performance-Run 16-bit Windows applications in a separate process
Privacy-Disable Driver Update Internet prompt
Privacy-Disable Tracking of most used programs
Privacy-Remove Alexa
Security-Always show Updates under Software
Security-Disable Web Open With prompt
Security-Re-Enable user:pass URLs

[Unattended]
NoPassExpSpec
ComputerType = Automatic
HibernationNo
AutoLogon = Adm
Resolution = 1920x1080
BitsPerPel = 32 bit (True Color)
MaximumDataStorePercentOfDisk = 12
RestorePointLife = 30
DesktopTheme = ConcaveC|Normal|Normal
IISInstall = 2
AutoUDay = 5
AutoUHour = 15
ProgFilesPath = "\Program Files"
CustomNetwork

[DesktopThemes]
C:\WINDOWS\Resources\Themes\Concave Compound\ConcaveC.msstyles

[NetAdapter1]
connname = ""
macaddress = ""
ipaddress = "192.168.0.1"
subnetmask = "255.255.255.0"
defaultgateway = ""
dnsserver1 = ""
dnsserver2 = ""
winsserver = ""
netbiossetting = "0"
ipxnetworknumber = "00000000"
ipxnetworkframetype = "0xFF"

[GuiRunOnce]

[Drivers]
I:\x86_winxp\driver - storage\alcor\sp56689\program_files\AlcorMicro\x32\SZCCID.INF,0
I:\x86_winxp\driver - storage\intel\sp57837\Drivers\x32\iaAHCI.inf,iaAHCI_5
I:\x86_winxp\driver - storage\intel\sp57837\Drivers\x32\iaAHCI.inf,iaAHCI_5_1
I:\x86_winxp\driver - storage\intel\sp57837\Drivers\x32\iaAHCI.inf,iaAHCI_5_1_1
I:\x86_winxp\driver - storage\intel\sp57837\Drivers\x32\iaAHCI.inf,iaAHCI_7_1
I:\x86_winxp\driver - storage\intel\sp57837\Drivers\x32\iaAHCI.inf,iaAHCI_7
I:\x86_winxp\driver - storage\intel\sp57837\Drivers\x32\iaAHCI.inf,iaAHCI_DesktopWorkstationServer
I:\x86_winxp\driver - storage\intel\sp57837\Drivers\x32\iaAHCI.inf,iaStor_DesktopWorkstationServer
I:\x86_winxp\driver - storage\intel\sp57837\Drivers\x32\iaAHCI.inf,iaAHCI_10DDO
I:\x86_winxp\driver - storage\intel\sp57837\Drivers\x32\iaAHCI.inf,iaAHCI_10R
I:\x86_winxp\driver - storage\intel\sp57837\Drivers\x32\iaAHCI.inf,iaAHCI_7MMDH
I:\x86_winxp\driver - storage\intel\sp57837\Drivers\x32\iaAHCI.inf,iaStor_7MDH
I:\x86_winxp\driver - storage\intel\sp57837\Drivers\x32\iaAHCI.inf,iaAHCI_7RDH
I:\x86_winxp\driver - storage\intel\sp57837\Drivers\x32\iaAHCI.inf,iaStor_7RDH
I:\x86_winxp\driver - storage\intel\sp57837\Drivers\x32\iaAHCI.inf,iaAHCI_9MEM
I:\x86_winxp\driver - storage\intel\sp57837\Drivers\x32\iaAHCI.inf,iaAHCI_Mobile
I:\x86_winxp\driver - storage\intel\sp57837\Drivers\x32\iaAHCI.inf,iaStor_Mobile
I:\x86_winxp\driver - storage\jmicron\sp57014\Driver1\Driver\XP_Vista\x32\johcih.inf,0
I:\x86_winxp\driver - storage\jmicron\sp57014\Driver2\Driver\x32\jmcr_hp.inf,0
I:\x86_winxp\driver - storage\jmicron\sp57014\Driver3\Driver\x32\jraid_hp.inf,0
I:\x86_winxp\driver - network\atheros\sp57138\XP\ndis5x\netathw.inf,0
I:\x86_winxp\driver - network\atheros\sp57473\XP\ndis5x\netathw.inf,0
I:\x86_winxp\driver - network\atheros\sp57473\XP\ndis5x64\netathwx.inf,0
I:\x86_winxp\driver - network\broadcom\sp57088\WinXP\bcmwl5.inf,0
I:\x86_winxp\driver - network\broadcom\sp57144\Win32\drivers\bcbthid32.inf,0
I:\x86_winxp\driver - network\intel\sp57086\Flat\XP32\E1C5132.inf,0
I:\x86_winxp\driver - network\intel\sp57482\XP\x32\Drivers\NETwLx32.INF,0
I:\x86_winxp\driver - network\realtek\sp57089\WINXP\PCI\Netrtlx.inf,0
I:\x86_winxp\driver - network\realtek\sp57089\WINXP\PCIE\Nethpe.inf,0
I:\x86_winxp\driver - input devices\hp\sp57329\Drivers\HKSButton\hphkbuttn.inf,0
I:\x86_winxp\driver - input devices\hp\sp57329\Drivers\KbdFilter\HpqKbFiltr.inf,0
I:\x86_winxp\driver - input devices\synaptics\sp58647\WinWDF\x86\SmbDrv.inf,0
I:\x86_winxp\driver - input devices\validity\sp57124\Validity Sensors\Shared\Drivers\VFS_451_DRV\vfs451.inf,0
I:\x86_winxp\driver - input devices\validity\sp57124\Validity Sensors\Shared\Drivers\VFS_471_DRV\vfs471.inf,0
I:\x86_winxp\driver - input devices\validity\sp57124\Validity Sensors\Shared\Drivers\VFS_491_DRV\vfs491.inf,0
I:\x86_winxp\driver - graphics\intel\sp57617\Graphics\Kit45578.inf,0
I:\x86_winxp\driver - graphics\intel\sp57617\ibxHDMI\IntcDAud.inf,0
I:\x86_winxp\driver - graphics\nvidia\sp57908\Display.Driver\NVBL.INF,0
I:\x86_winxp\driver - graphics\nvidia\sp57908\HDAudio\nvhda.inf,0
I:\x86_winxp\driver - chipset\infineon\sp46541\TPM Driver\ifxtpm.inf,0
I:\x86_winxp\driver - chipset\intel\sp57122\All\2008s4el.inf,0
I:\x86_winxp\driver - chipset\intel\sp57380\Drivers\MEI\HECI.inf,0
I:\x86_winxp\driver - chipset\intel\sp57380\Drivers\SOL\mesrl.inf,0
I:\x86_winxp\driver - chipset\intel\sp57380\NAC_PP\IntelAMTPP.inf,0
I:\x86_winxp\driver - audio\idt\sp57475\WDM\WinXP\STHDA.INF,0
I:\x86_winxp\Others\AtherosWlan\netathw.inf,0
I:\x86_winxp\Others\commonfiles\hdaudbus.inf,0
I:\x86_winxp\Others\FiraDisk\firadisk.inf,firadiskx86
I:\x86_winxp\Others\Ralink 802.11n Wireless LAN Card\oem14.inf,0
I:\x86_winxp\Others\RealTek Card Reader\DriverBin_32bit\RtsUStor.inf,0
I:\x86_winxp\Others\RealtekHDA\HDA.inf,0
I:\x86_winxp\Others\Renesas Electronics USB 3.0 Host Controller\oem10.inf,0
I:\x86_winxp\Others\Renesas Electronics USB 3.0 Root Hub\oem11.inf,0
I:\x86_winxp\Others\VIAusb3\XP\x86\ViaHub3.inf,0

[Hotfixes]

 

I'm afraid I can't give you removal details of XPLite app (deleted xplite.log from %windir%). I can give AIDA64 log (while striking out personal details) if it helps...

 

 

About the issue, I would like to add that LAN status in notification are shows "Limited or No connectivity" when connected directly to NAS.
 

[Wonko the Sane]

No, actually I was thinking more at a general description of the setup, you mention grub4dos, firadisk, and everything and the kitchen sink. 

 

Ethernet is Intel82579LM with many advance settings in device manager, can anthing get tweaked in there? you can use google image and type above model + advance device manager settings to know...

 

If I plug the Ethernet cable and PowerON system which starts Grub4dos > FiraDisk XP on RAM, I see start menu but My Computer takes 2 minutes to show. Process Explorer shows userinit not started svchost.exe frozen and after 2 minuted suddently everything starts up. (I remember such experience years back when i disabled Terminal Services, logon delayed...)

 

 

So what critical services could be disabled? because honestly, I don't know...

 

It sounds a lot like NOT an issue with services, but more along TCP/IP issues of some kind (or plug n' play, or something like that, something more connected to "devices" than to "services" ) .

 

Why don' t you trace a windows boot WITHOUT the NAS connected and one WITH the NAS connected?

i.e. Process Monitor "Boot time logging of all operations":

http://technet.micro...s/bb896645.aspx

 

Wonko

[L A M A]

I Logged boot with procmon.exe 2.3, first withNAS.pml and second withoutNAS.pml

(latest version crashes xp with bsod hard error@img_xp_update process) also same bsod after using latest procexp.exe ???

As usual, withNAS start menu's My computer froze

As usual, withoutNAS there was no delay seeing My computer from start menu.

 

 

Logs are huge but how do i compare the one with NAS and without? there is no option to compare. There is a column with time, but I see no time "jump" of 1+ minute by any process where freeze occurs. Doesn't make sense to me now

[Wonko the Sane]

Save as .csv and use a text comparing tool (or a spreadsheet, or both).

 

On a not-so-side note, is the delay when booting on when logging on?

http://blogs.technet...13/3305263.aspx

 

Or even later?

 

Wonko

[L A M A]

If you mean delay while process monitor is logging on then, yes and no.

if you mean delay after user logging in windows then again, yes and no

 

yes with NAS.

no without NAS.

 

file is huge, 90+mb .csv! don't know which text comparing app will read this huge file... trying winMerge

 

 

 

[Wonko the Sane]

No.

I mean, is the lag BEFORE you provide user name and password (logon) or after it and before you get to the desktop?

If you have automatic logon, set it to manual and find out in which part from physically switching on to appearing of desktop is the delay occurring.

 

Wonko

[L A M A]

I removed auto login and added "procexp.exe" as runOnce app. There was no delay showing classic login window and after I pressed enter, procexp.exe also started but svchost.exe didn't start all services (see below) till 1+ minute which is the issue.

 

 

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce]
"procexp.exe"="C:\\windows\\system32\\procexp.exe"

 

I can run procMon.exe the same way (if something can be done)...

 

Here is what happens when I remove NAS ethernet cable, procexp.exe starts and svchost.exe shows no delay in starting services:

 

If it helps, here is my services.msc (on MMC 3.0)

 

 

 

It sounds a lot like NOT an issue with services, but more along TCP/IP issues of some kind (or plug n' play, or something like that, something more connected to "devices" than to "services" ) .

 

Could it be the DLNA from NAS? Should i do the following?:

Start > Control Panel > Add or Remove Programs > Add / Remove Windows component > Networking Services > enable uPnP service? (it require COM+ something) which is removed with XPLite app.

[Wonko the Sane]

So, the issue is not really in "booting" but it logging on, right?

Then the logs won't be that big.

 

Instead of posting senselessly big images (that cannot be anyway read easily) post the §@ç#ing LOGS (one with the NAS connected and one without it)

 

As a side note, forget about the services.msc, and get a "real" tool such as serviwin:

http://www.nirsoft.n...s/serviwin.html

or pserv:

http://p-nand-q.com/.../pserv_cpl.html

 

Yes, Upnp is a possibility.

 

 

Wonko

[L A M A]

Instead of posting senselessly big images (that cannot be anyway read easily) post the §@ç#ing LOGS (one with the NAS connected and one without it)

 

 

Yes, Upnp is a possibility.

 

 

Wonko

 

Enabled Upnp but no success, still delays...

 

Grab the .csv logs from this rar file

 

 

 

 

...§@ç#ing LOGS

 

[Wonko the Sane]

Good.
Now, try again, this time select Colums in a more appropriate way.
You want NOT "time of day", but INSTEAD: 

• sequence
• relative time
• duration

this way we may start to have an "easy" common reference.
The two "worst things" happen:

 

44,60155550 3,86624090 2359,83782860 5:23:59.8378286 AM lsass.exe 900 Thread Exit SUCCESS Thread ID: 1012, User Time: 0.0000000, Kernel Time: 0.0000000
44,06512880 102,24638290 2458,21797060 5:24:58.2179706 AM svchost.exe 1252 UDP Send 0.0.0.0:bootpc -> 255.255.255.255:bootps SUCCESS Length: 300

 

The second "makes sense" somehow as it it connected to "network", the first one needs to be checked an understood in detail (as it is "strange").

 

Wonko

[L A M A]

All right, I've uploaded *.PML (with NAS attached) this time, should be easy to open from procmon.exe 

edit: here another *.PML without NAS, just in case you ask me

 

 

aside from this delay, do you see any other problem that could also get solved? so much happens in a second,..

 

 

 

 

 

edit: did you get anthing Wonko? 

[L A M A]

So,... what do i do next? 

[Wonko the Sane]

I don' t know.

 

The files you posted lately seem like taken from two different systems!

 

Are you sure that you logged the SAME system, in EXACTLY the SAME manner, once with the NAS attached and one without it?

Or one was with network attached and one without?

Or there is something in the trace settings that is different?

 

Normally two traces begin in the same manner and at a certain point diverge, yours BEGIN differently...

 

Wonko

[L A M A]

I don' t know.

 

The files you posted lately seem like taken from two different systems!

 

Are you sure that you logged the SAME system, in EXACTLY the SAME manner, once with the NAS attached and one without it?

Or one was with network attached and one without?

Or there is something in the trace settings that is different?

 

Normally two traces begin in the same manner and at a certain point diverge, yours BEGIN differently...

 

Wonko

I did that runOnce setting, saved my xp.vhd with image_xp_update.exe which means, everytime i reboot, procmon.exe starts up first.

 

 

First, I attached NAS, started system and saved log

Second, I restarted without NAS and saved log again

 

The only difference you're suppose to see is different time and time length of log. Don't know how system looks different to you  I can still restart and save log if you prefer.

 

edit: The core issue here is "negotiation", at any time i put ethernet cable, it takes 2+ minutes so, how about I restart system, wait till all services are loaded, clear procmon screen THEN, attach ethernet cable and save log? shouldn't this catch the problem in a different way?

[L A M A]

Wonko, this time,

01. I started system (runOnce:procmon.exe) without NAS (waited for all processes to become idle)

02. i then excluded most of the loopy processes except (services.exe, svchost.exe and system)

03. Cleared the screen

04. Connected ethernet cable and waited 1+ minute (till UDP recieved ip address).

05. Created log

 

 

here is a slimmed down log 1.5MB (165KB RAR). Maybe it should narrow down finding solution?

 

 

Whatever is happening here, is probably also freezing "My Computer". Is there a way to delay network proccesses for few seconds (gpedit.msc or tweak? which could at least give enough priority to other start up system processes?)

 

 

Any KB-update patch to fix this? i couldn't find 

 

edit: TCP/IP Net Bios helper service missing (not even on XPLite, probably nLited out). How to install this service from original xp ISO? It surely created trouble for me in Win7 (couldn't access my NAS without enabling it)

[Wonko the Sane]

I will try again. We still somehow fail to communicate.

 

How is setup your network?

Are you attaching/detaching the ethernet cable from the back of the PC in your attempts?

Is the NAS the ONLY device connected to the PC (directly with a cross over cable or through a network hub)?

 

The idea of the little sign looking like a hook at the end of a sentence means that it is a question, that you should please answer to directly.

 

I have not yet clear if the delay is at boot time or at logon, and if what you actually connect/disconnect is ONLY the NAS or the whole network connection.

 

Your note about "TCP/IP Net Bios helper service missing" makes no sense to me, unfortunately, if it is needed to access the NAS, then you need it, if you can access the NAS in XP without it, then it is not needed.

 

Wonko

[L A M A]

I will try again. We still somehow fail to communicate.

 

How is setup your network?

Are you attaching/detaching the ethernet cable from the back of the PC in your attempts?

Is the NAS the ONLY device connected to the PC (directly with a cross over cable or through a network hub)?

 

The idea of the little sign looking like a hook at the end of a sentence means that it is a question, that you should please answer to directly.

 

I have not yet clear if the delay is at boot time or at logon, and if what you actually connect/disconnect is ONLY the NAS or the whole network connection.

 

Your note about "TCP/IP Net Bios helper service missing" makes no sense to me, unfortunately, if it is needed to access the NAS, then you need it, if you can access the NAS in XP without it, then it is not needed.

 

Wonko

Are you attaching/detaching the ethernet cable from the back of the PC? YES

 

Is the NAS the ONLY device connected to the PC? YES, Directly

 

the delay is at boot time or at logon? I see BLACK BOOT and LOGON window without delays. It only slows down after LOGON where services get started

 

ONLY the NAS or the whole network connection? Only NAS

 

if you can access the NAS in XP without it, then it is not needed. It can access without but in negotiations delays, it was one guess 

================================

Seems like my last *.pml file was of no use either

[Wonko the Sane]

Seems like my last *.pml file was of no use either 

I don't know, I haven't had a look at it yet.

I need to understand what happens first.

 

Another test before going on.

Forget about the NAS, check if the same delay happens when some other devices are connected to the network and to the PC.

 

I am trying to understand, and failed till now (and you did not make any particular effort to describe clearly your setup) if the issue is related to having the PC connected to "network" (this is what I think) or to the NAS.

 

So, I will try again, a NAS makes sense on a network.

Do you have a network?

Network means at least TWO PC's connected through ethernet and a hub (or switch) to which you additionally attach other devices, such as a modem/router for internet access and (example) a NAS.

 

Repeat:

Hub (or switch) with at least three devices attached to it: two PC's and one NAS make a "network"

 

In the above there are THREE different conditions:

1. PC connected to the network
2. PC disconnected from the network (ethernet cable pulled off the back of the PC)
3. NAS disconnected from the network (ethernet cable pulled off the back of the NAS or switched off)

A further condition is the IP address of the PC, is it a "static" IP or is it gathered by another device on the network?

 

Wonko

[L A M A]

I'm out of home country and there are 4 devices with me

01. NAS

02. Laptop

03. A WIRED Router with 4 Ethernet ports+adsl port (without wifi which i don't use at all because its 100Mbps and without Internet)

04. Mobile (which becomes  "Portable WiFi hotspot" for Internet)

05. Powerline HomePlug 500Mbps x2 (for NAS when i'm in different room)

 

So, I'm not connected to any computer network or Wired router (even though i have). My mobile's so called "Portable WiFi hotspot" is only connected to Internet after I manually enable "Wireless Network Connection" from Network connections. Since this XP-OS is based on grub4dos\firadisk\RamDisk, upon every restart, "Wireless Network Connection" remains disabled.

 

 

Ultimately, I repeat, I only have one laptop which uses (mobile's WiFi for internet) and (Ethernet for NAS). 

 

Router can act as ethernet switch but currently pointless. Connection to WIRED router in my test was very fast, no delays at all but I really don't want to use it often (speed sucks).

[Wonko the Sane]

I'm out of home country and there are 4 devices with me

01. NAS

02. Laptop

03. A WIRED Router with 4 Ethernet ports+adsl port (without wifi which i don't use at all because its 100Mbps and without Internet)

04. Mobile (which becomes  "Portable WiFi hotspot" for Internet)

05. Powerline HomePlug 500Mbps x2 (for NAS when i'm in different room)

 

So, I'm not connected to any computer network or Wired router (even though i have). My mobile's so called "Portable WiFi hotspot" is only connected to Internet after I manually enable "Wireless Network Connection" from Network connections. Since this XP-OS is based on grub4dos\firadisk\RamDisk, upon every restart, "Wireless Network Connection" remains disabled.

 

 

Ultimately, I repeat, I only have one laptop which uses (mobile's WiFi for internet) and (Ethernet for NAS). 

 

Router can act as ethernet switch but currently pointless. Connection to WIRED router in my test was very fast, no delays at all but I really don't want to use it often (speed sucks).

Yes, that's all good  but the issue remains .

 

Is the delay related specifically to connecting it with the NAS OR you would have the same delay every time you connect to "a" network?

 

I hope you can see the difference, is the issue with the NAS as "itself" or is it with NAS as "any network device", or (you did not provide this info) with NAS as "any network device with DHCP server"?

 

The two logs are  probably not easily comparable because they refer to a "non-networked" PC vs. a "networked" PC (though networked only with the NAS).

 

What would be useful would be a couple of logs "non-networked" PC vs. "networked" PC (but with another device, NOT the NAS), the latter is IMHO the missing one, that would allow to compare two networked PC's (one with the NAS and one with another device).

And additionally (seen from the point of view of the NAS) the moment you connect/logon the PC you are actually "creating" the network for the first time (if you prefer there is NO "network" existing untill BOTH the PC and NAS are on and connected), we don't know if this changes anything when compared to simply add one, the other or both the devices to an already existing network.

 

Wonko

[L A M A]

Hmm, I can keep answering but, maybe this time with question

 

 

Is the delay related specifically to connecting it with the NAS OR you would have the same delay every time you connect to "a" network?

I connect to NAS (WD or Iomega), there is a delay but when i connect to [router+adsl] which IMO is a network, it does not delay. What does this answer you?

 

I hope you can see the difference, is the issue with the NAS as "itself" or is it with NAS as "any network device", or (you did not provide this info) with NAS as "any network device with DHCP server"?

Modem+router has it's own DHCP server but it does not delay on Windows. When NAS is connected to Modem+router, it does not delay there either as NAS immedietly gets an ip address from DHCP of Modem+router (meaning issue cannot be with NAS as itself, any network device or any network device with DHCP server, can it be?). To further confirm, I will test with portable Win8...

 

 

 

The two logs are  probably not easily comparable because they refer to a "non-networked" PC vs. a "networked" PC (though networked only with the NAS).

 

What would be useful would be a couple of logs "non-networked" PC vs. "networked" PC (but with another device, NOT the NAS), the latter is IMHO the missing one, that would allow to compare two networked PC's (one with the NAS and one with another device).And additionally (seen from the point of view of the NAS) the moment you connect/logon the PC you are actually "creating" the network for the first time (if you prefer there is NO "network" existing untill BOTH the PC and NAS are on and connected), we don't know if this changes anything when compared to simply add one, the other or both the devices to an already existing network.

So, you like me to connect to modem+router with laptop and give you procmon.exe log? This can become "networked PC through: networked only with the NAS" vs. "networked-PC through: networked only with the Modem+router".

 

Secondly, do you want me to save xp with img_xp_update.exe after the network is "created" for the first time? and see the result after a restart where it simply adds NAS or modem+router device or both to an already existing network?