Re: Serious Missing Bandwidth

LawsonE wrote:
"Curieux" <G-2@xxxxxxx> wrote in message news:uaYNf.494688$qk4.74121@bgtnsc05-
[...]
I came to this group because I believed 'advoccy' carried with it a sense of pride. Earned pride and knowledge? Yeah, I figured I'd find a solution. And I still may! But a wanker like Timberwolf seems to 'advocate' dogma and I'm a dude with in need of a fix.

<snipped the bizarre, yet believable story>

WHY and HOW Word was able to cause another computer on the network to crash is left as an exercise for the reader.

Yeah, but I'm cool on the LAN...(half-a-gig of data flies between boxes).
The G4 only chokes on the I-Net. (Only on DL)

My suggestion to you is to disconnect the PCs and see if you get the expected bandwidth from the Mac.

Was done, 1st off. (Can't talk to Comcast about a prob unless the machine is suckin' directly from the modem...)


Perhaps there is some interactivity between an MS product on the Mac and the PCs causing the problem.

No, the 'interaction' between the Mac & the Winbox's is great!
I've heard plenty of horror stories & it wasn't automatic...but I don't have a clue I'm on 2 OS's (it's a simple WORKGROUP).
I actually do 'more' than I expected.
The access and manipulation of the different files systems (From the other OS) isn't much different than being on the same platforms.

It's only DL bandwith, & only on the Internet which died. (UL is fine).

Another thing to try is create a user account on the Mac that has no access to MS or other 3rd party products and log onto that and see if the problem persists.

Did that too. It's a common cure for some M$ glitches.

1. I *know* how to deal w/this on a Winbox. Check out the M$ Knowledge Base. Loads of fixes from the command prompt.
2. I can't translate the above to the Mac file structue/sys.

TCP/IP..Networking & associated protocols are code based. (The above story of yours may have been odd...but the fix is almost always a *corruption* which can be repaired (not many files are responsible) via the command prompt. (Usually, even the Registry in an M$ box will balk to a change if the file/code is corrupt)

EX: (Problem/Solution from M$)

Problem:
You may experience one or all of the following symptoms:
ï An error occurred while renewing interface 'Internet': An operation was attempted on something that is not a socket.
ï When you issue the ipconfig /renew command, you may receive the following error message: ìAn error occurred while renewing interface local area connection: an operation was attempted on something that is not a socket. Unable to contact driver Error code 2î
ï In the Device Manager, when you click Show Hidden Devices, TCP/IP Protocol Driver is listed as disabled under "Non-Plug and Play drivers", with error code 24.
ï When you create a dial-up connection, you may receive the following error message: Error 720: No PPP Control Protocols Configured
ï When you issue an ipconfig command at a command prompt, you may receive an error message that is similar to one of the following:
The operation failed since no adapter is in the state permissible for this operation
The attempted operation is not supported for the type of object referenced.
ï When you issue the Netsh int ip reset resetlog.txt command at a command prompt, you may receive the following error message:
Initialization function INITHELPERDLL in IPMONTR.DLL failed to start with error code 10107.

===
Solution?

Click Start, and then click Run. In the Open box, type regedit, and then click OK. Locate the following registry subkeys:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock2
Right-click each key, and then click Delete. Click Yes to confirm the deletion of each key. Close Regedit.
Locate the Nettcpip.inf file in %winroot%\inf, and then open the file in Notepad. Locate the [MS-TCPIP.PrimaryInstall] section.
Edit the Characteristics = 0xa0 entry and replace 0xa0 with 0x80. Save the file, and then exit Notepad.
In Control Panel, double-click Network Connections, right-click Local Area Connection, and then select Properties.
On the General tab, click Install, select Protocol, and then click Add.
In the Select Network Protocols window, click Have Disk.
In the Copy manufacturer's files from: text box, type c:\windows\inf, and then click OK.
Select Internet Protocol (TCP/IP), and then click OK.
Note This step will return you to the Local Area Connection Properties screen, but now the Uninstall button is available.
Select Internet Protocol (TCP/IP), click Uninstall, and then click Yes.
Restart your computer
In Control Panel, double-click Network Connections, right-click Local Area Connection, and then select Properties. On the General tab, click Install, select Protocol, and then click Add. In the Select Network Protocols window, click Have Disk.
In the Copy Manufacturer's files from text box, type c:\windows\inf, and then click OK. Select Internet Protocol, and then click OK.

Or?
Start/Run --> cmd.exe
and then, in the command prompt that opened up, type:
netsh.exe winsock reset
and hit Enter. Follow prompts and reboot.
If that didn't work, see if registering the following DLLs helps:
From Start/Run, run the following commands:
regsvr32 %windir%\system32\atl.dll
then
regsvr32 %windir%\system32\hnetcfg.dll
regsvr32 %windir%\system32\netshell.dll
regsvr32 %windir%\system32\netcfgx.dll
regsvr32 %windir%\system32\netman.dll

========

EZ!

Michael
.