Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsWindows VistaWindows XPWindows MeWindows 98Windows 95Virtual PCInternet ExplorerOutlook ExpressWindows MediaSecurity
Related Topics
MS Server ProductsMS OfficePC HardwareMore Topics ...

Windows Forum / Windows 98 / Networking / September 2007

Tip: Looking for answers? Try searching our database.

Can ping printers, but not new pc - help!

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
spokes - 19 Sep 2007 10:43 GMT
We've had a small LAN running for quite some time with no problems: two PCs
(98SE + XP Pro), two printers, all connected to a Belkin wireless router . I
recently replaced the XP PC, and now can't get the PCs to talk to each
other. Either can ping the router (everything's RJ45 wired, in passing);
either can ping both of the printers on the network; but neither can ping
the other. If I remove the RJ45 plug from the new XP machine and plug it
into the old XP machine, everything's fine, as before. But the moment I plug
it into the new XP machine, it all goes pear-shaped, as described. As far as
I can see, the settings on the new XP machione are identical to those on the
old one - same workgroup name etc - but '100% data lost' every time.

I should just say I'm far from adept at this kind of thing...I stumble
around and do my best and I've picked up bits & bobs (like how to ping), but
techy stuff goes over my head at a pretty basic level, so please bear that
in mind. Many thanks in anticipation for any suggestions.
MEB - 19 Sep 2007 16:49 GMT
| We've had a small LAN running for quite some time with no problems: two PCs
| (98SE + XP Pro), two printers, all connected to a Belkin wireless router . I
[quoted text clipped - 11 lines]
| techy stuff goes over my head at a pretty basic level, so please bear that
| in mind. Many thanks in anticipation for any suggestions.

First check your firewall settings to make sure your local network [IP
addresses AND *File and Printer Sharing* {simple network}] is ALLOWED. Make
sure you check EVERY firewall. Make sure to check any that may be included
within your AV program [such as worm protection pseudo-firewall/proxy - like
Norton or McAfee].
Disabling your firewall may NOT work during testing/setup. Some firewalls
don't actually remove themselves and continue to block access even when
disabled. SO it is best to make sure the firewall is setup properly FIRST.

Next make absolutely sure the network IP addresses [IP and subnet] match
exactly [example = 192.168.1.* and/or 192.168.0.* subnet 255.255.255.0 -
respectively]. NOTE the third number set [the 0 or 1 octet] MUST be the same
for the particular network being configured.

Make sure all computers are part of the same work group [MSHOME is default
for XP].

Next, generally, it has been found easiest to create the same USER and
password for network access on all computers. IF using differring names they
MUST be allowed permission to the network and resources [in XP and VISTA]
and the EVERYONE/GUEST account must be turned [check this] on in XP {simple
file sharing}.

ALL of the above must be done as Administrator in XP; Win98 does not
require administrator access to change these UNLESS policies have been
applied, or basic network/security settings have been changed.

Here is a link to some basic info and links to other sources:

http://peoplescounsel.orgfree.com/ref/gen/security/NETWORKING.htm

Post back if successful, or if additional help is needed.

Signature

MEB
http://peoplescounsel.orgfree.com
________

spokes - 20 Sep 2007 11:13 GMT
Thanks very much MEB - much appreciated. By chance I'd found the link you
provided - I suspect it was in one of your earlier messages, tho' I can't
swear to it - from which I stumbled on a message that warned that even if
you've turned your firewall off, it may not 'be off enough'. So taking me
lead from that, I completely uninstalled ZoneAlarm and glory be, that seems
to have sorted it.

Oddities remain. His PC can now see mine; mine still can't see his. But to
all intents and purposes, that's all we need. We don't file share much; the
main issue was printer sharing - and that now works fine.

So again, many thanks.

> | We've had a small LAN running for quite some time with no problems: two
> PCs
[quoted text clipped - 59 lines]
>
> Post back if successful, or if additional help is needed.
MEB - 20 Sep 2007 16:20 GMT
| Thanks very much MEB - much appreciated. By chance I'd found the link you
| provided - I suspect it was in one of your earlier messages, tho' I can't
[quoted text clipped - 8 lines]
|
| So again, many thanks.

Thanks for posting back. Glad to hear that your print sharing is now
working.
I will caution though, that if either of you [any computer] contact the
Internet, please make sure you re-install a firewall [which likely will now
detect the network automatically]. I never suggest using Microsoft's
[crippled in XP] firewall though.
In ZoneAlarm, if it is blocking the local network in some form, go into the
advanced settings and ADD your network addressing [generally by a range of
addresses] if it does not automatically detect the settings. Also, in
program/applications allowed, you (sometimes) MAY have to manually add the
printer software into the allowed programs [and this JUST for local servers
{the two check marks for such}]. It seems that sometimes ZA misses the local
network and applications trying to establish connections, whereas, anything
from or to the Internet seems to generally be caught..

As for file sharing: if it does sometime become of interest, run through
those settings and configurations noted.

Good luck.

| > | We've had a small LAN running for quite some time with no problems: two
| > PCs
[quoted text clipped - 59 lines]
| >
| > Post back if successful, or if additional help is needed.

Signature

MEB
http://peoplescounsel.orgfree.com
________

spokes - 24 Sep 2007 12:04 GMT
Thanks again MEB. The Curse of The Windows Network has returned. I decided
to leave it a day or three, relying just on the inbuilt XP firewall until I
was sure everything had bedded in before attempting to reinstal ZoneAlarm,
but even without ZA it's now gone pear-shaped again. This morning after
turning everything on, neither my colleague nor I can print to the HP, and I
can't even ping it now.

It's plugged in to the Belkin router; the light's on (on the router); it's
online (prints configuration pages and the like no problem); but it cannot
be pinged by either computer.

One thing I ought to mention: in the course of my efforts last week I
discovered that my partner's PC had no firewall running. I told him and he
re-enabled the McAfee Firewall on his pc. But this shouldn't affect my
ability to ping the HP, should it?

Losing hair fast. Please help.

> | Thanks very much MEB - much appreciated. By chance I'd found the link
> you
[quoted text clipped - 129 lines]
> | >
> | > Post back if successful, or if additional help is needed.
MEB - 25 Sep 2007 00:35 GMT
| Thanks again MEB. The Curse of The Windows Network has returned. I decided
| to leave it a day or three, relying just on the inbuilt XP firewall until I
[quoted text clipped - 13 lines]
|
| Losing hair fast. Please help.

I'll start with the last question first. If the XP has the software to
configure your router or printer, (and running McAfee) then yes, McAfee's
firewall [and likely which includes AV] could be affecting your network.
McAfee and Norton [among others] have extra aspects, such as worm protection
which MAY interfere with other connections and local settings [computer upon
which they are installed and thereby their connectability in the network].
One must be diligent to set ALL the proper settings in those programs.
Same holds true for the XP firewall.
Any must be configured to properly pass the intended protocols and have the
proper open ports (and application assignments if applicable).

Next, has the Belkin been flashed with the latest BIOS for the router?
Though this is generally associated more with connections in VISTA inclusive
networks, XP is also still receiving updates which may affect both XP
[networking] and the local network [with 9X left waving in the breeze]. A
caution: if a massive change is made to the Belkin BIOS it could potentially
effect 9X's ability to function [small chance]. Also, flashing ANY device
carries potential issues.

As you found the web page and I presume reviewed the material; which style
of network did you choose:

1. Soft set [router assigned networking/IP, which actual means hardware
set]?
If router set, did you make sure all router settings were still
properly set?
Is there another router or network involved?
If more than one router, are the extra set as switches rather than routers?

2. Hard set [manually assigned addressing for all devices and nodes]?

3. Simple networking [file and printer, guest accounts, etc.] or fine
grained {increased security} [specifically assigned user access and
passwords, special assigned networking folders, etc.]. Those types of global
settings would affect all basic networking. Regardless of which, did you
re-check all network settings, addressing, and assignments.

4. Did you check to ensure such factors as an expired IP "lease" is not
interfering/breaking connections by using ipconfig [cmd ipconfig /all from
the run/command box on XP] and winipcfg [from the run box clicking Details]
on the 9X box, and that all network settings are still properly assigned?

5. It would be condusive to know which box and OS you are using and what
firewall and AV, as well as your partner's configuration. Also which
computer controls what.

6. You indicated the printer is connected directly to the router  [network
ready]:
Which computer/node has the configuration software for the printer?
Can this computer access the printer?
Is the printer *always on* or is it intermittently shut down during
non-use?
You also stated there were two printers; does the other function properly?

7. Has this net had any changes made to it during the time period you
indicated, and was the network reset during that time period [complete
network reset] after those changes? {That includes any Microsoft updates}

8. You indicate, that the network HAS been shutdown and restarted [though
not how extensively/completely]:
IF using router soft set [router hardware TCP/IP addressing] did you follow
the proper startup routine.
Presuming this is just a simple single net:
Modem then router > router controlling computer {computer with
router interface installed} > printer controlling computer {which would be
best as the router controller also [makes that the master computer (somewhat
like a master server) far easier to maintain the network]} > other nodes.

9. Are you attempting to use VPN or remote desktop functions?

Supplying this basic information may allow the group to better handle and
proceed through diagnosis of potential issues.

Also, if possible, try connecting the problem printer directly to the
computer with the device configuration software, and check those settings.
Dealing with two printers and several nodes, it would appear a hard set
network would be more stable.

Signature

MEB
http://peoplescounsel.orgfree.com
________

 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.