Prev: Run out of IP addresses
Next: Networking Laptop and desktop
From: KORISNIK on 11 May 2008 20:05
those 2 pcs isolated from LAN and connected with crossover
cable,firewalls down, manually assigned 192.168.1.100,101 and nt pc
account has some restrictions (however it operated internet ok while
it was connected in LAN) Now xp can see nt in workgroup but cant be
neither accesed,nor ftp-ed by nt (although it is seen in the same
workgroup)
Is perhaps dhcp on xp interfearing -should it be disabled at boot via
msconfig or is it smth else?
From: Chuck [MVP] on 11 May 2008 23:31
On Sun, 11 May 2008 17:05:08 -0700 (PDT), KORISNIK <tehit1(a)gmail.com> wrote:

>those 2 pcs isolated from LAN and connected with crossover
>cable,firewalls down, manually assigned 192.168.1.100,101 and nt pc
>account has some restrictions (however it operated internet ok while
>it was connected in LAN) Now xp can see nt in workgroup but cant be
>neither accesed,nor ftp-ed by nt (although it is seen in the same
>workgroup)
>Is perhaps dhcp on xp interfearing -should it be disabled at boot via
>msconfig or is it smth else?

I'd look for a personal firewall or other security component, interfering with
SMBs, first.
<http://networking.nitecruzr.net/2005/05/your-personal-firewall-can-either-help.html>
http://networking.nitecruzr.net/2005/05/your-personal-firewall-can-either-help.html

Then, I'd look at logs from "browstat status", "ipconfig /all", "net config
server", and "net config workstation", from each computer, and diagnose the
problem. Read this article, and linked articles, and follow instructions
precisely (download browstat!):
<http://networking.nitecruzr.net/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp>
http://networking.nitecruzr.net/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp

--
Cheers,
Chuck, MS-MVP 2005-2007 [Windows - Networking]
http://networking.nitecruzr.net/
 | 
Pages: 1
Prev: Run out of IP addresses
Next: Networking Laptop and desktop