Setting up 2 PC's to share drive

  • Thread starter Thread starter byrocat
  • Start date Start date
Pity you rabbited on about laplink.

Even a laplink cable alone costs more than a crossover lan cable.

More than a crossover and two nics too.

if you buy a blue or yellow , yes .
 
Rod Speed said:
Nope, you can use the dhcp default.

This is typical Rod Speed troll bullshit. He just loves to pontificate
on matters he has no experience or knowledge of. If you pay any
attention to this village idiot, then you are one of his sock puppets.

If you connect two Windows workstations using a crossover cable you
must set up TCP/IP with static IP addresses. The reason is because
there is no DHCP server in Windows workstations.

To make sure I asked the Microsoft networking forum. Here's the
dialog:

+++
I want to connect two Win2K machines together using a crossover cable.
Must I set up networking using a static IP address or does Win2K Pro
SP4 have built in DHCP?

Windows 2000 Pro does not have a DHCP server, you'll need to use
static addressing to be sure it will work correctly.
+++

Where's the DHCP server, Rod boy?


--

Map of the Vast Right Wing Conspiracy
http://home.houston.rr.com/rkba/vrwc.html

"Whatever crushes individuality is despotism."
--John Stuart Mill, "On Liberty"
 
Once again, Boob demonstrates he is a ****ing moron and idiot troll.

The option assigns valid addresses without DHCP. You simply are too stupid to verify
this. It is documented under "To configure TCP/IP for automatic addressing".

Bob said:
This is typical Rod Speed troll bullshit. He just loves to pontificate
on matters he has no experience or knowledge of. If you pay any
attention to this village idiot, then you are one of his sock puppets.

If you connect two Windows workstations using a crossover cable you
must set up TCP/IP with static IP addresses. The reason is because
there is no DHCP server in Windows workstations.

To make sure I asked the Microsoft networking forum. Here's the
dialog:
[drivel snipped]
 
This is typical Rod Speed troll bullshit. He just loves to
pontificate on matters he has no experience or knowledge of.

I've been doing this stuff LONG before you ever did, you
pathetic excuse for a pig ignorant bullshit artist AND use
the latest OSs too, unlike some pathetically senile silly
old fart that has never had a ****ing clue on the basics.
If you connect two Windows workstations using a crossover
cable you must set up TCP/IP with static IP addresses.
Wrong.

The reason is because there is no DHCP server in Windows workstations.

Thanks for that completely superfluous proof
that you've never ever had a ****ing clue.

That works fine even right back to Win98.
To make sure I asked the Microsoft networking forum. Here's the dialog:

Irrelevant. I'VE DONE WHAT YOU CLAIM ISNT
POSSIBLE, YOU STUPID PIG IGNORANT CLOWN.

And the config the OP asked about, with a router,
HAS A DHCP SERVER IN THE ROUTER ANYWAY.
Windows 2000 Pro does not have a DHCP server, you'll need
to use static addressing to be sure it will work correctly.
+++
Where's the DHCP server, Rod boy?

In 2K, you stupid pig ignorant pathetically senile silly old fart.

AND THE OP ISNT RUNNING 2K ANYWAY.
 
Bob said:
This is typical Rod Speed troll bullshit. He just loves to pontificate
on matters he has no experience or knowledge of. If you pay any
attention to this village idiot, then you are one of his sock puppets.

If you connect two Windows workstations using a crossover cable you
must set up TCP/IP with static IP addresses. The reason is because
there is no DHCP server in Windows workstations.

To make sure I asked the Microsoft networking forum. Here's the
dialog:

+++


Windows 2000 Pro does not have a DHCP server, you'll need to use
static addressing to be sure it will work correctly.
+++

Where's the DHCP server, Rod boy?

In 2K, you stupid pig ignorant pathetically senile silly old fart.
http://www.clubs.mq.edu.au/mits/Downloads/TCP-IP for Windows 2000.pdf
bottom of page 8.

Read it and weep, again.

And the OP isnt even running 2K anyway, stupid pig ignorant pathetically senile
silly old fart.
 
Thanks for that completely superfluous proof
that you've never ever had a ****ing clue.
That works fine even right back to Win98.

For the Gentle Reader who would benefit from discovering that this
village idiot Rodboy is a ****wit troll who doesn't know what he is
talking about, be informed that the original discussion I posted
involved Win2K, not Win98. Anyone who would refer to Win98 in today's
computing environment is indeed a complete idiot.
Irrelevant. I'VE DONE WHAT YOU CLAIM ISNT
POSSIBLE, YOU STUPID PIG IGNORANT CLOWN.
And the config the OP asked about, with a router,
HAS A DHCP SERVER IN THE ROUTER ANYWAY.

As the Gentle Reader will notice above, the discussion was concerned
with connecting two machines with a crossover cable. There was no
router involved.

Here we see Rodboy trying again to weasel out of his glaring and most
profound idiotic comment about DHCP. First he tries to bullshit us
into believing the discussion somehow involved a now-defunct Win98
system, and then knowing that was pure crap he is now trying to slip a
router into the picture when it is so very obvious that there is no
router involved in a simple crossover connection.

What this troll does is to crap all over someone else's post by
spewing his bullshit wherever he things the Gentle Reader won't catch
on. For example, when I mentioned that the Win2K crossover system we
were discussing would require static IP addresses (because Win2K does
not provice DHCP services, which almost everyone knows except Troll
Rodboy), he dumps his load of bullcrap expecting his pontifical tone
to support his idiocy.

But it won't work Trollboy because those of us who do know about
Windows and PCs know for certain that you are a notorious fraud. The
only people who support you are your sock puppets and they are just as
moronic as you.

So, Gentle Reader, I will warn you one last time - because I do not
intend to read this cretin's posts again. Be warned that this Troll
Rodboy is a notorious bullshit artist who likes to get off dropping
his bullcrap into posts in a pontifical manner that is enough to tell
you he is full of it.
In 2K, you stupid pig ignorant pathetically senile silly old fart.

From a Microsoft networking forum:
"Windows 2000 Pro does not have a DHCP server, you'll need to use
static addressing to be sure it will work correctly."
AND THE OP ISNT RUNNING 2K ANYWAY.

My discussion centered around running Win2K.

Idiot.


--

Map of the Vast Right Wing Conspiracy
http://home.houston.rr.com/rkba/vrwc.html

"Whatever crushes individuality is despotism."
--John Stuart Mill, "On Liberty"
 
In 2K, you stupid pig ignorant pathetically senile silly old fart.
http://www.clubs.mq.edu.au/mits/Downloads/TCP-IP for Windows 2000.pdf
bottom of page 8.

LOL. That assumes there is a DHCP server on the network. Connecting 2
Windows workstations with a crossover cable does not provide a DHCP
service. Idiot.

If the best you can come up with is an outdated dated high school
primer from May 2001, you are truly pathetic.
Read it and weep, again.

How pathetic does it get for you. Astute readers are not going to buy
your inane bullshit. The Gentle Reader has been adequately warned.
Only your sock puppets will support your moronic behavior. Idiot.
And the OP isnt even running 2K anyway, stupid pig ignorant pathetically senile
silly old fart.

My discussion was centered on Win2K as an example. Idiot.

Anyway, idiot, your reference above was about Win2K networking.

--

Map of the Vast Right Wing Conspiracy
http://home.houston.rr.com/rkba/vrwc.html

"Whatever crushes individuality is despotism."
--John Stuart Mill, "On Liberty"
 
If you connect two Windows workstations using a crossover cable you
must set up TCP/IP with static IP addresses. The reason is because
there is no DHCP server in Windows workstations.

While true in Win2K Pro, WinXP has TCP/IP Autoconfiguration
enabled by default. No need for static IP addresses in WinXP, that
is less work for setup. Machines will get 169.254.x.y IPs automatically.
 
For the Gentle Reader who would benefit from discovering
that this village idiot Rodboy is a ****wit troll who doesn't
know what he is talking about,

Even a pathetically senile silly old fart should be able to bullshit its
way out of its predicament better than that pathetic effort, redneck.
be informed that the original discussion
I posted involved Win2K, not Win98.

Irrelevant to that stupid pig ignorant claim you clearly
made about about WINDOWS WORKSTATIONS.
Anyone who would refer to Win98 in today's
computing environment is indeed a complete idiot.

Irrelevant to that stupid pig ignorant claim you clearly
made about about WINDOWS WORKSTATIONS.
As the Gentle Reader will notice above, the discussion
was concerned with connecting two machines with a
crossover cable. There was no router involved.

Pity there was in the original post that had many including
me point out that just a crossover would be enough.

If however one of the PCs ALREADY had a router for net
access, and many do, the dhcp server would be in that, ****wit.
Here we see Rodboy trying again to weasel out of his
glaring and most profound idiotic comment about DHCP.

Have fun explaining how come you can indeed use Win98
with a crossover and have the IPs automatically assigned.
First he tries to bullshit us into believing the discussion
somehow involved a now-defunct Win98 system,

Everyone can see you are lying on that. YOU were the one that
clearly rabbited on about WINDOWS WORKSTATIONS above.
and then knowing that was pure crap he is now trying to slip
a router into the picture when it is so very obvious that there
is no router involved in a simple crossover connection.

Caught lying, yet again.

Reams of puerile shit any 2 year old could leave for dead flushed where it
belongs.
My discussion centered around running Win2K.

Pity you dont even know that the OP is running 2K, ****wit.

****wit.
 
Bob said:
Another sock puppet rears its moronic head.

Odd how your response is rather more Ron/Rod like than his.
So who is the actual sock puppet here, Bob.
 
Back
Top