Re: Problem with Windows 98SE computer networking with XP computer



On Thu, 05 Jun 2008 17:11:52 GMT, "Ray" <rgk456_NOSPAM_@xxxxxxxxxxx>
wrote:

I'm new to networking and would appreciate any help I can get on this
problem. I have tried may suggested solutions but nothing has helped so
far.

I have a home network with one XP Pro SP2 (NTFS) computer (called
Blackbox)
and one older Win 98SE (FAT32) computer (called Dell) connected through a
router/DSL modem (ActionTec GT704WG gateway) for a wired network.

"ipconfig /all" for the XP computer is:
Windows IP configuration
Host name: blackbox
Primary Dns Suffix:
Node Type: Unknown
IP Routing Enabled: No
WINS Proxy Enabled: No
DNS Suffix Search List: domain_not_st.invalid
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix: domain_not_set.invalid
Description: Attansic L1 Gigabit Ethernet 1000Base-T Adapter
Physical Address: 00-18-F3-5F-C7-14
Dhcp Enabled: Yes
Autoconfiguration Enabled: Yes
IP Address: 192.168.1.64
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.1.1
DHCP Server: 192.168.1.1
DNS Servers: 192.168.1.1
68.238.64.12
Lease Obtained: Wednesday, June 04, 2008 9:23
Lease Expires: Thursday, June 05, 2008 9:23

"ipconfig /all" for the 98SE computer is:
Windows IP configuration:
Host name: Dell.domain_not_set.invalid (I don't understand - the
computer
is called "Dell")
DNS servers: 192.168.1.1
68.238.64.12
Mode Type: Broadcast
NetBIOS scope ID:
IP Routing enabled: No
WINS Proxy enabled: No
NetBIOS Resolution Uses DNS: No
Ethernet Adapter:
Description: U.S. Robotics 10/100 PCI NIC TX
Physical address: 00-14-C1-40-B7-D9
DHCP enabled: Yes
IP Address: 192.168.1.66
Subnet Mask: 255.255.255.0
Default gateway: 192.168.1.1
PHCP Server: 192.168.1.1
Primary WINS Server:
Secondary WINS Server:
Lease Obtained: 06 04 08 10:28:21 AM
Lease Expires: 06 05 08 10:28:21 AM

Both computers have firewall and anti-virus software. The 98SE computer
used Kerio while the XP uses Comodo. Both firewalls and both anti-virus
softwares are disabled. The XP computer can only "see" the 98SE computer
with the Kerio firewall disabled (it does not seem to work with a trusted
IP
address group of 192.164.1.1 - 192.168.1.255).

Both computers are able to use the internet without trouble.
Both computers can ping the localhost by name and IP address, ping each
other and ping a remote address (e.g., google.com) by name or IP address.
Both computers have several shared folders.
Both computers show the home and individual shared folders in their
"Network
Places/Neighborhood" locations.

The XP computer can map the shared folders of the 98SE computer and
browse/read/write to them.
The 98SE computer can NOT view/map/read/write to the shared folders on the
XP. Clicking on a shared folder for the XP machine results in an error
message. The message reads: ""\\Blackbox\<shared folder name> is not
accessible. Not enough memory is available. Quit some programs."
"Blackbox" is the name of the XP computer.

Please help! Using a "one-way" network is not enough. I would appreciate
any/all help/solutions I can get.

The problem could be that an antivirus program has changed an obscure
setting on the XP computer. This Microsoft Knowledge Base article has
a likely solution:

Antivirus Software May Cause Event ID 2011
http://support.microsoft.com/?scid=kb;en-us;177078

Thanks very much for the response. I had already seen this KB article and
it seems to not apply to my XP machine. It refers to NAV which I never had
on my machine (not in a million years :)) or IBM AV (also never had) and
there is no "IRPStackSize" entry. It does note how to add a value for
IRPStackSize if it is missing but I thought that still applied to those
with NAV. Am I wrong? Should I apply this entry with a value of 15? I
read at http://www.crn.com/white-box/59200376 that this entry was not ever
"required" by NAV but was added by its installation, quoting: "6. Older
versions of Norton Anti-Virus set a value for IRPStacksize in the registry
that is too low for XP. In fact, XP doesn't even need this registry key. If
you have it in your registry, thankSymantec (NSDQ: SYMC) and then delete it.
If you determine that the XP registry has this unneeded entry, check this
registry location:...". Is this incorrect?

Any other suggestions?

You're welcome. I'd try the procedure in the KB article. If it
solves the problem, great. If it doesn't, you can undo what you
change. A value of 15 often works.
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com
.



Relevant Pages

  • Re: the effects on running dcpromo to fix anAD issue.
    ... This belongs to the multihomed server. ... AD registers certain records in DNS in the form of SRV records that signify AD's resource and service locations. ... When there are multiple NICs, ... there are some registry changes to eliminate the registration of the external NIC. ...
    (microsoft.public.windows.server.active_directory)
  • Re: RRAS - required as Internet Gateway
    ... My server is not a DC just a standalone server... ... Multihomed DCs, DNS, RRAS servers. ... When there are multiple NICs, ... there are some registry changes to eliminate the ...
    (microsoft.public.windows.server.active_directory)
  • Re: RPC is unavailable when try to transfer FSMO Roles
    ... prevent the public interface addresses from being registered in DNS. ... In the DNS management console, in the properties of the DNS server, ... Registry value: DnsAvoidRegisterRecords ... To stop registration of both NICs, add or alter this reg ...
    (microsoft.public.windows.server.active_directory)
  • Re: Is it safe to use a DHCP to assign the IP addresses to the servers
    ... Being a VPN Server and even simply running RRAS makes it multi-homed. ... Domain Controllers with the PDF Role are automatically Domain Master Browser. ... Multihomed DCs, DNS, RRAS servers. ... there are some registry changes to eliminate the registration of the external NIC. ...
    (microsoft.public.windows.server.networking)
  • Re: Multihomed DCs
    ... mean that the multihomed server is the member server. ... W2K3, with dual NICs that responds to domain traffic Vlan, ... It is hugely problematic due to the multiple interefaces and DNS ... there are some registry changes to eliminate the ...
    (microsoft.public.windows.server.networking)