DHCP 2

Well.... after much help from "mame" and others, I thought
I had my problem fixed, but the reason I thought that is
because it works for a while and then it doesn't work. In
fact it worked for a whole day. Anyhow I'm satisified that
I've tried all cable hookup scenario's so today while it was
giving us a problem I collected some info that you guys had
asked for last time before I thought it was fixed again.
So I redirected all the Ipconfig's and Ping's to a txt file and
brought the results home on a floppy. And here it is,
(please excuse the upper case I use it all the time at work)
----FIRST DURING PROBLEM I IPCONFIG'D EACH,
PROBLEM NODE (HOSS) DURING PROBLEM
(HE CAN'T SEE US)
Windows 98 IP Configuration
0 Ethernet adapter :
IP Address. . . . . . . . . : 192.168.1.104
Subnet Mask . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . : 192.168.1.1
-----------------
MY NODE DURING PROBLEM (I CAN SEE HIM )
Windows IP Configuration
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 192.168.1.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
------------------
THEN I PINGED HIM DURING TIME HE CAN'T SEE OUT
BUT I CAN SEE HIM
-----------
Pinging HOSS [192.168.1.104] with 32 bytes of data:
Reply from 192.168.1.104: bytes=32 time<1ms TTL=128
Reply from 192.168.1.104: bytes=32 time<1ms TTL=128
Reply from 192.168.1.104: bytes=32 time<1ms TTL=128
Reply from 192.168.1.104: bytes=32 time<1ms TTL=128
Ping statistics for 192.168.1.104:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
-------------
THEN I WENT TO HIS NODE AND PINGED ME
---------
Pinging DAVE [192.168.1.100] with 32 bytes of data:
Reply from 192.168.1.100: bytes=32 time=1ms TTL=128
Reply from 192.168.1.100: bytes=32 time<10ms TTL=128
Reply from 192.168.1.100: bytes=32 time<10ms TTL=128
Reply from 192.168.1.100: bytes=32 time<10ms TTL=128
Ping statistics for 192.168.1.100:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms
-------------------
BEING SOMEWHAT AMAZED THAT THE PINGED EVIDENTLY WENT
THROUGH I IMMEDIATELY OPENED HIS WINDOWS EXPLORER FILE
HANDLER AND TRIED TO SEE THE NETWORK BUT GOT A MSG,
"NETWORK UNAVAILBLE"
----------
I THEN PINGED THE PRINT SERVER NODE
-----
Pinging VEFX1 [192.168.1.101] with 32 bytes of data:
Reply from 192.168.1.101: bytes=32 time<1ms TTL=128
Reply from 192.168.1.101: bytes=32 time<1ms TTL=128
Reply from 192.168.1.101: bytes=32 time<1ms TTL=128
Reply from 192.168.1.101: bytes=32 time<1ms TTL=128
Ping statistics for 192.168.1.101:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
----
Which went thru showing it's IP addrs of 101
But HOSS still cannot print to the plot server?

Well then it's definitely software related.

What OS Are you using?

When the problem happens try to browse the other nodes by ip address.
Instead of by name us its ipaddress. But this may not help if Hoss
can't ping the Plot server. Try and see if he can ping the router.
192.168.1.1


instead of Plot use //192.168.1.xxx/ The problem with this is that
with DHCP your plotter, depending on boot order may have a different
address. On my home network 4 desktops, 2 print servers, 2 laptops, 2
wirless bridges. I assign them ip address. That way when windows
screws up I can still get there.

If you're using win 98 I had a problem browsing the network and then
would loff off and log back on and everything would work.

**** With XP make sure none of your nodes are setup in bridge mode.
This may happen even if you only have one ethernet port but the
computer has a modem attached also. The bridge thing is kinda hard to
get out of. It will only show for a while then disappear unless you
have two connections going all the time. This may be a problem on the
computer HOSS.

I only have Win 98 at the house and only limited time with xp.
Someone else will probably have to chime in.


On Thu, 26 Aug 2004 19:43:37 -0400, "D" <NoMail@NoSpam> wrote: