Printer and File Sharing

[Martin]

I am having problems sharing a printer and files. I have 2 machines using ME and one using XP connected with a hub. The two running ME can see each other and use the printer fine but the XP one can only see the other pc, not the gateway and cant find the printer, and the gateway cant see the XP pc, why is this?

[Greenstead]

Can you clarify your configuration a little more. It will help to understand what is happening.
e.g.
Is it like this?
ISP dial-up line -> Gateway PC modem with ICS ...Gateway PC NIC -> HUB.
HUB -> ME PC #2 and XP PC.
Which hub ports are you using ?
(I hope you do not have a cable modem connected to the hub).

Is it XP home or Pro ?

In the meantime check:
- ICS does not report any errors.
- All PCs have the same workgroup.
- All PCs have a unique computer name.
- ALL PCs have network shares defined.
- ALL NICS are set to get an IP address and DNS addresses automatically.
- MS Client and file & printer sharing are checked on each NIC.
- All firewalls (diable XP's ICF permanently) are disabled until you get all connections working .

If you still have problems after these checks post again with:

- Confirm the checks above and errors you see.
- Use Winipcfg on the ME PCs and report the IP and subnet and gateway addresses.
- Use Ipconfig /all on XP and do likewise.
(If you use ipconfig /all > file.txt you can cut and paste the info).

[Martin]

I have a cable modem attacjed to the gateway which is connected to the hub and uses Sygates Home Network Program...Gateway PC NIC -> HUB.
HUB -> ME PC #2 and XP PC.
Which hub ports are you using ? P1, P2, P3

XP home

In the meantime check:
- All PCs have the same workgroup. They do
- All PCs have a unique computer name. They do
- ALL PCs have network shares defined. How do find this out?
- ALL NICS are set to get an IP address and DNS addresses automatically. They are
- MS Client and file & printer sharing are checked on each NIC. They are

Gateway-

Windows IP Configuration
Host Name . . . . . . . . . : RDOMIN
DNS Servers . . . . . . . . : 62.31.64.116
62.31.64.115
Node Type . . . . . . . . . :
Hybrid NetBIOS Scope ID. . . . . . :
IP Routing Enabled. . . . . : Yes
WINS Proxy Enabled. . . . . : No
NetBIOS Resolution Uses DNS : No0

Ethernet adapter :
Description . . . . . . . . : ICSHARE Adapter.
Physical Address. . . . . . : 00-E0-7D-92-58-EA
DHCP Enabled. . . . . . . . : No
IP Address. . . . . . . . . : 192.168.0.1
Subnet Mask . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . :
Primary WINS Server . . . . :
Secondary WINS Server . . . :
Lease Obtained. . . . . . . :
Lease Expires . . . . . . . :

Ethernet adapter :
Description . . . . . . . . : NDIS 5.0 driver
Physical Address. . . . . . : 00-E0-7D-92-58-EE
DHCP Enabled. . . . . . . . : Yes
IP Address. . . . . . . . . : 80.195.**.**
Subnet Mask . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . : 80.195.67.1
DHCP Server . . . . . . . . : 62.31.64.116
Primary WINS Server . . . . :
Secondary WINS Server . . . :
Lease Obtained. . . . . . . : 10 20 02 16:30:11
Lease Expires . . . . . . . : 10 21 02 14:27:532 Ethernet adapter :
Description . . . . . . . . : PPP Adapter.
Physical Address. . . . . . : 44-45-53-54-00-01
DHCP Enabled. . . . . . . . : Yes
IP Address. . . . . . . . . : 0.0.0.0
Subnet Mask . . . . . . . . : 0.0.0.0
Default Gateway . . . . . . :
DHCP Server . . . . . . . . : 255.255.255.255
Primary WINS Server . . . . :
Secondary WINS Server . . . :
Lease Obtained. . . . . . . :
Lease Expires . . . . . . . :

3 Ethernet adapter :
Description . . . . . . . . : PPP Adapter.
Physical Address. . . . . . : 44-45-53-54-00-00
DHCP Enabled. . . . . . . . : Yes
IP Address. . . . . . . . . : 0.0.0.0
Subnet Mask . . . . . . . . : 0.0.0.0
Default Gateway . . . . . . :
DHCP Server . . . . . . . . : 255.255.255.255
Primary WINS Server . . . . :
Secondary WINS Server . . . :
Lease Obtained. . . . . . . :
Lease Expires . . . . . . . :

4 Ethernet adapter :
Description . . . . . . . . : AOL Dial-Up Adapter
Physical Address. . . . . . : 44-45-53-54-61-70
DHCP Enabled. . . . . . . . : Yes
IP Address. . . . . . . . . : 0.0.0.0
Subnet Mask . . . . . . . . : 0.0.0.0
Default Gateway . . . . . . :
DHCP Server . . . . . . . . : 255.255.255.255
Primary WINS Server . . . . :
Secondary WINS Server . . . :
Lease Obtained. . . . . . . :
Lease Expires . . . . . . . :

5 Ethernet adapter :
Description . . . . . . . . : AOL Adapter
Physical Address. . . . . . : 44-45-53-54-61-6F
DHCP Enabled. . . . . . . . : Yes
IP Address. . . . . . . . . : 0.0.0.0
Subnet Mask . . . . . . . . : 0.0.0.0
Default Gateway . . . . . . :
DHCP Server . . . . . . . . : 255.255.255.255
Primary WINS Server . . . . :
Secondary WINS Server . . . :
Lease Obtained. . . . . . . :
Lease Expires . . . . . . . :

PC1 (ME)

Windows IP Configuration
Host Name . . . . . . . . . : RDOMIN
DNS Servers . . . . . . . . : 192.168.0.1
Node Type . . . . . . . . . :
Broadcast NetBIOS Scope ID. . . . . . :
IP Routing Enabled. . . . . : No
WINS Proxy Enabled. . . . . : No
NetBIOS Resolution Uses DNS : Yes
Ethernet adapter :
Description . . . . . . . . : NDIS 5.0 driver
Physical Address. . . . . . : 00-E0-7D-91-E9-C9
DHCP Enabled. . . . . . . . : Yes
IP Address. . . . . . . . . : 192.168.0.2
Subnet Mask . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . : 192.168.0.1
Primary WINS Server . . . . :
Secondary WINS Server . . . :
Lease Obtained. . . . . . . : 10 20 02 19:48:22
Lease Expires . . . . . . . :


PC2 (XP)

Windows IP Configuration

Host Name . . . . . . . . . . . . : martin
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection 2:


Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/100 S Desktop Adapter
Physical Address. . . . . . . . . : 00-02-B3-8C-6B-2B
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.3
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
NetBIOS over Tcpip. . . . . . . . : Disabled
Lease Obtained. . . . . . . . . . : 20 October 2002 18:17:37
Lease Expires . . . . . . . . . . : 19 January 2038 04:14:07

[Greenstead]

Ok thanks - good feedback.

Its clearer now.

The configuration looks mostly good but some strange things:

On PC1
- The gateway PC and PC1 seem to have the same host name (Host Name . . . . . . . . . : RDOMIN).
They should be different names. I'm surprised the two ME PCs can see each other. Change the computer name on PC1.

On the XP PC.
- The node type should be = broadcast.
(Node Type . . . . . . . . . . . . : Unknown)
May not be a problem...forget for now - we can fix later if needed.
- Netbios over TCP/IP should be enabled.
(NetBIOS over Tcpip. . . . . . . . : Disabled)
Go to Network connections -> Highlight Local Area Connection 2 -> right click -> properties -> highlight TCP/IP -> properties -> advanced -> WINS -> check enable Netbios over TCP/IP -> click OK till all is closed out.

Network shares:
On each PC under c: you should made a folder called shared and modify its properties to make it network shared. I can only tell you how to that on XP since I don't have ME. Highlight the shared folder and right click -> properties -> sharing tab -> check box for 'share this folder on the network'.

If you make those changes then reboot all PCs starting with the gateway first and XP last.

Are you trying to use any other protocols (e.g. IPX/SPX or Netbeui) - you should not need them.

See what you get now.

[Martin]

Firstly, thanks for the continued help.

PC1 is not called RDomin, it has a seperate name!

I did as you said and now:

The XP PC can see PC1 under Workgroup Computers but cant see the "Shared" folder, and cant see the gateway at all.

The Gateway can see PC1 and its "Shared" folder through "Entire Network" but not PC2

PC1 locks up when I try to view "Entire Network" and so I dont know what it can see!

This probably doesnt help I know!

[Greenstead]

Hmm... not too much progress then.

First I should say I don't know this Sygate software though I have heard of it. Why do you use it instead of ICS ? Not that I am a fan of ICS as such.

Also I should say the best configuration for what you are trying to do would be a combined NAT cable router and 4 port switch which has the advantages of a NAT firewall, no need to leave the gateway PC on, and a simple setup. Just a thought for you for the future.

Still, there's no reason why your currnet config should not work.

Back to the current problem :
I still want to question the host name for PC1. Your earlier post showed it had the same host name as the gateway PC
---
Gateway-
Windows IP Configuration
Host Name . . . . . . . . . : RDOMIN

PC1 (ME)
Windows IP Configuration
Host Name . . . . . . . . . : RDOMIN
---
Is that right or ?? Why do you think the Gateway PC and PC1 have different names ?
If the PCs do not have unique names it will cause the problems you have described.

A test you can try:
From each PC:
Ping the IP address of the other two PCs - that will work I expect.
Ping the PCname of the other two PCs - that might not work.

The results might indicate where the problems lie.

[Martin]

In the Identification tab on PC1, the Computers name is not RDOMIN but the Host info was right.

Ping- XP- Gateway- IP- Request timed out
Name- Ping request could not find host RDomin. Please check the name and try again.

XP- PC1- IP- Request timed out
Name- Request timed out


Gateway-XP- IP- Request timed out
Name- Unable to find host *pcname*

Gateway-PC1-IP- Request timed out
Name- Unable to find host *pcname*

PC1-Gateway-IP- Request timed out
Name- OK

PC1-XP- IP- Request timed out
Name- Request timed out

[Greenstead]

Even more confusing.

Nearly everything timed out.
Particularly confusing is that the pings by IP to the gateway time out which does not make sense since we know PC1 and the XP PC are getting their IP addresses from the Gateway PC.

You are pinging 192.168.0.1 as the Gateway ?


For interest from Microsoft windows help and support center.
host name:
The DNS name of a device on a network. These names are used to locate computers on the network. For most Windows computers, the host name and the computer name are the same.

What is the pcname of PC1 ?

bedtime here - I'll check back in during Monday.

[Martin]

PC1 is called "Kristin", its my sister's

[Martin]

ok change to those pings after disabling firewalls:

those that have changed

PC2-PC1- Name and IP OK

PC1-PC2- Name and Ip OK
PC1-Gateway- IP- Times out
Name- OK

The gateway to the rest dont work neither does PC2-gateway

[Martin]

Also., upon removal of the firewalls:

PC2 and the gateway can see the shared folders of PC1
PC2 can see the gateway but isnt allowed access to the folders
The gateway can see PC1 and shared folders but not PC2 at all
PC1 can see all computers and can access all files.

[Greenstead]

Thats useful info. Also some conflicting info e.g. PC1 cannot ping the gateway IP but can ping its name - can you check that again.

Some ideas and guesswork (its what I'm reduced to now):

What I know: XP is very open to file sharing. It doesn't care who accesses it. You just need an IP connection and name resolution and you will see its shares. The only things I know could stop access to XP is a firewall on the PC you access from.

Guesswork : I have seen it said some windows systems (I dunno ME) need you to use the same ID and password on the computer you access from. I don't expect it would be acceptable to have the same ID and password on each PC but it would be interesting to try it and know if this makes it work. i.e. PC2 to the Gateway.

Another question (I asked it before):
Are you trying to use any other protocols (e.g. IPX/SPX or Netbeui) ? You only need TCP/IP.

After the checks you have made I am running short on new ideas. Things look correctly setup but I see all still does not work. If we are still stuck I am left with suspecting the Sygate software may be interferring somehow. So my next suggestions would be more fundemental changes.

[Martin]

The ping info is correct BUT when I ping 192.168.0.1 it doesnt work but when I ping the name it says that the IP of the gateway is 192.168.0.2 but ipconfig on PC1 shows that 192.168.0.2 is the IP of PC1! Pinging 192.168.0.2 from PC1 then works.

How do I change the ID and password?

Netbui is installed on PC1 and the gateway but how can i remove that if it is being used over tcp/ip?

I am using Sygate because using ICS meant I couldnt play a game over the internet and Sygate fixed this.

Doesnt it appear that PC1 and the gateway talk to each othe fine as do PC1 and PC2, its just the gateway and PC2 which dont talk, and so I cant see the printer or files? All computers use Sygate.

[Greenstead]

Yes I agree Sygate is widely used and normally works OK. I also see why you want to use it.

That ping to the gateway is very strange. Pinging 192.168.0.2 on PC1 works because it is just pinging itself.

Changing the ID & password I mean to make a user account on PC2 which has the same name and password as the one you logon to the Gateway with.

And thinking about logons - you are logging on to the Gateway ?not just firing up windows. Ditto the XP PC.

On protocols:
- You have only Netbios over TCP/IP I think ?
- On the gateway. Can you check you also have Netbios over TCP/IP. You can run it alongside Netbeui.
- Ditto for PC1.

Alternatively you can disable Netbios over TCP/IP and run Netbeui on all PCs. (It is not in XP by default and has to be loaded from the XP CD).

Whatever you need the same protocol on each PC, you can have two or three protocols, but all PCs must all have at least one protocol in common.

It might be a protocol problem - maybe.

[Martin]

When I start up PC1 and the Gateway, they both have Windows Netorking Log On screens which didnt have the same username but now do, likewise password. On the XP one, I log in under My User Account with a different password, I wasnt aware that they were linked?

As for netbios over tcpip, it is enabled on all but each PC has tcpp installed.

On the gateway and PC1 the netbios over tcpip is greyed out but ticked so I couldnt change it anyway, on the XP one I had enabled it myself.

[Greenstead]

OK - I think you answered my latest ideas.

Lets step back and see what we know (tell me if any I have wrong).:
- One ME PC (Gateway) with Sygate and an NIC to cable modem and an NIC to the hub. (This is not correct is it?)
- One ME PC (PC1) with an NIC to the hub.
- One XP PC (PC2) with an NIC to the hub.
- All PCs have TCP/IP installed.
- All PCs have Netbios over TCP/IP enabled.
- All PCs have the same workgroup.
- All PCs have a unique computer name.
- ALL PCs have network shares defined.
- ALL NICS are set to get an IP address and DNS addresses automatically.
- MS Client and file & printer sharing are checked on each NIC.
- All firewalls are disabled.

All the things we have checked would normally result in a working LAN. There must be some other factor causing the problem. It can only be Sygate.

I took at look at Sygate's website.
- Have you raised your question in the forums there ?
- Have you tried this ?
http://forums.sygatetech.com/showthread.php?threadid=96

Also - you don't have ICS installed do you - I think you already indicated not?

[Martin]

Everything you said is correct. The gateway has one NIC connected to the modem and one connected to the hub.

How do I check that all PCs have network shares defined?

One thing, on the XP, it is set to obtain IP address and DNS server automatically but I have an alternate configuration that uses IP 192.168.0.3, subnet mask 255.255.255.0 and gateway 192.168.0.1, I did this to get the game working, now that I remember this wasnt set up before when it worked, so I will revert back, check game then check network and get back to you.

ICS is installed on gateway and PC1 but disabled on the gateway.

I will do as it says in the Sygate thread as well and get back to you.

[Greenstead]

OK see you back here when you have done your changes.

The Sygate website says Sygate is incompatible with ICS. I suggest you delete ICS on all PCs.

On network shares, since PC1 sees files on the other PCs then the shares must be set up OK.

I think you should post your problem in the Sygate forums. There is an excellent moderator there who seems to solve all the problems. He asks people to post their Sygate logs and he can analyse them and advise a solution. I see he has Sygate upgrades he offers if needed.

I see there are hundreds of problems posted at the Sygate site, some similar to yours. This product certainly have a wide impact on the network. I feel convinced your problem is most likely a Sygate based problem. If you still have problems please try Sygate forums next.

If you still find problems I think my only other suggestion for you is to delete Sygate and try ICS or a hardware router as an internet gateway PC.

[Martin]

Removing the alternate configuration means I cant see any PCs so that mustnt have been causing the problem.

[Martin]

Right, I'll try that then, thanks very much for your help, time and patience :)

[Martin]

All I had to do was uninstall ICS! Its all working now :)