Problem with windows file sharing(difficult)

UPDATED Problem with windows file sharing(difficult)

So... I am having a problem with Win XP SP2.

I have a computer that suddenly started having a problem with it's file sharing and networking. It may have been related to a virus/trojan. I have been able to partly resolve the issues but have a BIG one remaining...

Networking wasn't working at all on the wireless or wired adaptor so I removed them from device manager and they were picked up on reboot and started working.

When I try to connect from another machine to the problem machine via \\bentley (the machine name) I get a "cannot find" error, even if I use the IP address such as \\172.16.2.26

Locally on the machine...
When I type \\bentley I can see the printers, shares, and scheduled tasks... HOWEVER, when I try to browse the shares I get a "not accessable" error.
If I rather try the IP locally on the machine \\172.16.2.26 I get a "cannot find" error.

If I try to access a machine across the network I get the "cannot find" error regardless of IP or name.

I think that I have tried everything but please make any suggestions that you can in case I have forgotten anything. Windows firewall is disabled.

Thanks

Doug

 

Hello sailsfast Welcome to Wilders: Please try the following:

Connecting to a Shared Printer on Windows XP via Windows Vista





Problem:

Your Windows Vista PC cannot connect and print to a “shared” printer, which is directly attached to a Windows XP PC, via your network.



Solution:

1: Unplug your USB cable from the back of the Windows XP PC and plug the USB cable directly into your Windows Vista PC.
2: The Windows Vista drivers for your printer should be automatically loaded and your printer will be installed on your Windows Vista PC. If this was successful, skip right to step 3.
If step 2 is not successful…
i. Download the Windows Vista printer driver for your printer from the manufacturer’s website.

1. If your printer’s manufacturer has not created a Vista driver yet, retry step 2.

ii. Install the driver on your Windows Vista PC. During installation, you’ll be prompted to connect the printer to your PC. Choose the option to proceed with installation without connecting the printer.

3: After installation is complete, open the Printers icon in the Windows Vista Control Panel.
4: Right-click on your printer that was just installed and choose Properties.
5: Navigate to the Ports tab.
6: Click Add Port, then select Local Port, then click New Port.
7: For the Port Name, enter the exact network path and share name of your printer. (ex. - \\HOMEPC\Printer2)
8: Click OK and make sure that this new port is selected with a check in the checkbox.
9: Click Apply and then OK to close the printer properties.
You should now be able to print from your Windows Vista PC to a shared printer located on your Windows XP PC


Also you can follow the Instructions here if you need more Help:

http://www.microsoft.com/windowsxp/using/networking/expert/russel_hni.mspx

 

I don't have a Vista machine handy but I get the idea...

Trying to connect to a printer on the problem machine from another results in a "Can not connect" error.

If we can figure out why:

1) I can locally browse printers but not files via \\(machine name)

OR

2) I can locally browse via \\(machine name) but not \\(IP address)

We can figure things out... Does anyone know if there is a way to find what services such as "print and file sharing" are binding to what protocals?

 

The folks over at DSLReports have a very good networking forum:

http://www.dslreports.com/forum/sharing

and also a very useful microsoft-specific forum:

http://www.dslreports.com/forum/microsoft

 

Your speaking removing a virus ? I don't know if it is a solution but LSP-fix came to the rescue after damaging the IP stack,just my 2 cents.

 

Thanks... I gave it a try but no problems detected...

BTW: ordinary networking seems to work.. I am connected to it right now using VNC.

 

UPDATE Problem with windows file sharing(difficult)

Via netstat I confirmed that microsoft-ds and netbios does not seem to be working on the "broken" machine... Now what do I do? :?(

(note) the working machine's IP is 172.16.2.20 the broken 172.16.2.27 and I have noted the open (vnc) connection. During an active connection attempt...

Working machine to broken machine via IP address

Proto Local Address Foreign Address State
TCP Mastif:1096 localhost:1097 ESTABLISHED
TCP Mastif:1097 localhost:1096 ESTABLISHED
TCP Mastif:1107 localhost:1108 ESTABLISHED
TCP Mastif:1108 localhost:1107 ESTABLISHED
TCP Mastif:http 172.16.2.27:2211 (vnc) ESTABLISHED
TCP Mastif:2531 172.16.2.27:5900 (vnc) ESTABLISHED
TCP Mastif:2796 172.16.2.27:microsoft-ds SYN_SENT
TCP Mastif:2797 172.16.2.27:netbios-ssn SYN_SENT

The reverse... Broken machine to working machine via IP address

Proto Local Address Foreign Address State
TCP Bentley:1670 localhost:1671 ESTABLISHED
TCP Bentley:1671 localhost:1670 ESTABLISHED
TCP Bentley:1672 localhost:1673 ESTABLISHED
TCP Bentley:1673 localhost:1672 ESTABLISHED
TCP Bentley:2211 172.16.2.20:http (vnc) ESTABLISHED
TCP Bentley:5900 172.16.2.20:2531 (vnc) ESTABLISHED

Working machnine

Proto Local Address Foreign Address State
TCP Mastif:http Mastif:0 LISTENING
TCP Mastif:epmap Mastif:0 LISTENING
TCP Mastif:https Mastif:0 LISTENING
TCP Mastif:microsoft-ds Mastif:0 LISTENING
TCP Mastif:1025 Mastif:0 LISTENING
TCP Mastif:3389 Mastif:0 LISTENING
TCP Mastif:5800 Mastif:0 LISTENING
TCP Mastif:5900 Mastif:0 LISTENING
TCP Mastif:1034 Mastif:0 LISTENING
TCP Mastif:1096 localhost:1097 ESTABLISHED
TCP Mastif:1097 localhost:1096 ESTABLISHED
TCP Mastif:1107 localhost:1108 ESTABLISHED
TCP Mastif:1108 localhost:1107 ESTABLISHED
TCP Mastif:10110 Mastif:0 LISTENING
TCP Mastif:epmap Mastif:3318 TIME_WAIT
TCP Mastif:epmap Mastif:3319 TIME_WAIT
TCP Mastif:epmap Mastif:3326 TIME_WAIT
TCP Mastif:epmap Mastif:3327 TIME_WAIT
TCP Mastif:netbios-ssn Mastif:0 LISTENING
TCP Mastif:2531 172.16.2.27:5900 (vnc) ESTABLISHED
TCP Mastif:3306 Mastif:microsoft-ds TIME_WAIT
TCP Mastif:3307
Mastif:epmap TIME_WAIT
TCP Mastif:3317 Mastif:microsoft-ds TIME_WAIT
TCP Mastif:3366 172.16.2.27:microsoft-ds SYN_SENT
TCP Mastif:3367 172.16.2.27:netbios-ssn SYN_SENT
UDP Mastif:snmp *:*
UDP Mastif:microsoft-ds *:*
UDP Mastif:isakmp *:*
UDP Mastif:syslog *:*
UDP Mastif:1026 *:*
UDP Mastif:1244 *:*
UDP Mastif:1245 *:*
UDP Mastif:1257 *:*
UDP Mastif:3456 *:*
UDP Mastif:4500 *:*
UDP Mastif:ntp *:*
UDP Mastif:1900 *:*
UDP Mastif:ntp *:*
UDP Mastif:netbios-ns *:*
UDP Mastif:netbios-dgm *:*
UDP Mastif:1900 *:*

Broken Machine

Proto Local Address Foreign Address State
TCP Bentley:epmap Bentley:0 LISTENING
TCP Bentley:5900 Bentley:0 LISTENING
TCP Bentley:1032 Bentley:0 LISTENING
TCP Bentley:1670 localhost:1671 ESTABLISHED
TCP Bentley:1671 localhost:1670 ESTABLISHED
TCP Bentley:1672 localhost:1673 ESTABLISHED
TCP Bentley:1673 localhost:1672 ESTABLISHED
TCP Bentley:5900 172.16.2.20:2531 ESTABLISHED
UDP Bentley:isakmp *:*
UDP Bentley:1034 *:*
UDP Bentley:1052 *:*
UDP Bentley:1363 *:*
UDP Bentley:1585 *:*
UDP Bentley:4500 *:*
UDP Bentley:ntp *:*
UDP Bentley:1900 *:*
UDP Bentley:ntp *:*
UDP Bentley:1900 *:*
UDP Bentley:ntp *:*
UDP Bentley:1900 *:*